Troubleshooting
If you stumble upon a problem while working with IDE Services, make sure to contact the IDE Services support team. If possible, we recommend including the following information in your report:
Screenshots or a screencast demonstrating the problem in the user interface
Reproduction steps
Logs from your IDE and Toolbox App
Large files can be uploaded here: https://uploads.jetbrains.com
Logs and diagnostic data
Collect IDE and Toolbox App logs
The log files are called idea.log and toolbox.log respectively and can be collected from the IDE.
Navigate to the product log files from the IDE
From the main menu, select and choose Show in Finder (for macOS) or Show in Explorer (for Windows and Linux).
Your IDE will generate a ZIP archive with all the log files, including build logs and automatic thread dumps.
As an alternative, you can find IDE logs in your file system:
macOS:
~/Library/Logs/JetBrains/<IDE_NAME_AND_VERSION>Windows:
%LOCALAPPDATA%\JetBrains\<IDE_NAME_AND_VERSION>\logLinux:
~/.cache/JetBrains/<IDE_NAME_AND_VERSION>/log
Collect server-side logs
Depending on the deployment option in use, provide the support team with the following information:
Cloud deployment (AWS, GoogleCloud, Azure)
The cloud log processor output for the necessary time period
Kubernetes (on premises)
The time-series log offload from your centralized logging solution (Grafana, Prometheus, Datadog, and so on)
If no logging solution is present, run the following command to collect logs:
kubectl logs <IDE_Services_pods>
Docker (on premises)
The Stream container output exported to a file
Alternatively, run the following command:
docker logs <container_id>To obtain the container ID, run the following command:
docker ps
Change the application's logging level
The support team may ask you to change the logging level of your application to gain more insights.
In your server configuration file, change the logging configuration as follows:
logging: level: root: INFO # can be changed to WARN/DEBUG/TRACElogging: level: root: INFO # can be changed to WARN/DEBUG/TRACE
Safe mode
Safe mode is a temporary fallback mechanism that ensures continued access to JetBrains IDEs when the IDE Services Server or other critical services (such as a PostgreSQL database, object storage, or authentication provider) are unavailable. It is intended for emergency use only and can be enabled solely with the assistance of the IDE Services support team.
To enable safe mode, the support team issues a special safe mode key. By registering this key as an environment variable, your organization’s developers can continue using JetBrains IDEs for up to 72 hours from the moment the key is issued. During this time, the support team will work urgently to resolve underlying issues.
Enable safe mode
Contact the IDE Services support team, describe your current issues, and provide them with your License ID.
The IDE Services support team generates a safe mode key for you. Add a
SAFEMODE_KEYenvironment variable and use the provided key as its value.The exact steps to register an environment variable depend on your deployment method. Examples:
Add the following configuration to the values.yaml file:
ides: ... config: additionalEnvs: - name: SAFEMODE_KEY value: "YOUR_SAFE_MODE_KEY"Run the following command:
kubectl set env deployments/<YOUR_IDE_SERVICES_DEPLOYMENT> SAFEMODE_KEY=<YOUR_SAFE_MODE_KEY>Use one of the options described in the Google Cloud documentation.
Restart your IDE Services Server. For more details, refer to the instructions for Docker and Kubernetes installations.
Your IDE Services Server will run in safe mode and operate as a License server. If necessary, provide instructions to your developers on how to activate IDE licenses manually.
Once the issue with your IDE Services instance is resolved, you can proceed with reverting the configuration changes and restarting the IDE Services Server to restore full functionality.
Exceeded limit on max bytes to buffer
Exceeded limit on max bytes to buffer : <current setting value>
This error appears when the size of the request exceeds the value configured in spring.http.codecs.max-in-memory-size. The default value is 10MB.
To fix the issue, set a higher value in the configuration file. Only use the values necessary for the request.