abbyswag/qwen-code
1
0
Fork 0
mirror of https://github.com/QwenLM/qwen-code.git synced 2025-12-19 09:33:53 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
e20171e7ddb7c4d0935dcb578b8395dc560005ec
qwen-code/docs/troubleshooting.md
starsandskies ddb32a3614 Edit pass of docs/troubleshooting.md (#1200) 
Make a pass through the docs/troubleshooting.md file to hopefully improve readability and consistency.

Notably, some links in the existing documentation appear to point to non-existent pages. I've updated them to what I believe is an appropriate alternative. Also, there's some vague usage of "CLI" and "server", which I've -hopefully correctly- called "Gemini CLI" and "MCP server"
2025-06-20 17:51:51 +00:00

3.3 KiB
Raw Blame History

Troubleshooting Guide

This guide provides solutions to common issues and debugging tips.

Frequently asked questions (FAQs)

  • Q: How do I update Gemini CLI to the latest version?

    • A: If installed globally via npm, update Gemini CLI using the command npm install -g @gemini-cli/cli@latest. If run from source, pull the latest changes from the repository and rebuild using npm run build.

  • Q: Where are Gemini CLI configuration files stored?

    • A: The CLI configuration is stored within two settings.json files: one in your home directory and one in your project's root directory. In both locations, settings.json is found in the .gemini/ folder. Refer to CLI Configuration for more details.

Common error messages and solutions

  • Error: EADDRINUSE (Address already in use) when starting an MCP server.

    • Cause: Another process is already using the port the MCP server is trying to bind to.
    • Solution: Either stop the other process that is using the port or configure the MCP server to use a different port.

  • Error: Command not found (when attempting the run Gemini CLI).

    • Cause: Gemini CLI is not correctly installed or not in your system's PATH.
    • Solution:
      1. Ensure Gemini CLI installation was successful.
      2. If installed globally, check that your npm global binary directory is in your PATH.
      3. If running from source, ensure you are using the correct command to invoke it (e.g., node packages/cli/dist/index.js ...).

  • Error: MODULE_NOT_FOUND or import errors.

    • Cause: Dependencies are not installed correctly, or the project hasn't been built.
    • Solution:
      1. Run npm install to ensure all dependencies are present.
      2. Run npm run build to compile the project.

  • Error: "Operation not permitted", "Permission denied", or similar.

    • Cause: If sandboxing is enabled, then the application is likely attempting an operation restricted by your sandbox, such as writing outside the project directory or system temp directory.
    • Solution: See Sandboxing for more information, including how to customize your sandbox configuration.

Debugging Tips

  • CLI debugging:

    • Use the --verbose flag (if available) with CLI commands for more detailed output.
    • Check the CLI logs, often found in a user-specific configuration or cache directory.

  • Core debugging:

    • Check the server console output for error messages or stack traces.
    • Increase log verbosity if configurable.
    • Use Node.js debugging tools (e.g., node --inspect) if you need to step through server-side code.

  • Tool issues:

    • If a specific tool is failing, try to isolate the issue by running the simplest possible version of the command or operation the tool performs.
    • For run_shell_command, check that the command works directly in your shell first.
    • For file system tools, double-check paths and permissions.

  • Pre-flight checks:

    • Always run npm run preflight before committing code. This can catch many common issues related to formatting, linting, and type errors.

If you encounter an issue not covered here, consider searching the project's issue tracker on GitHub or reporting a new issue with detailed information.