# Troubleshooting the analysis

See also the Troubleshooting section on the corresponding Scanner page.

## Out of memory error <a href="#out-of-memory" id="out-of-memory"></a>

If your analysis errors out with `java.lang.OutOfMemoryError: GC overhead limit exceeded` then it means that your project is too large or too intricate for the scanner to analyze with the default memory allocation. To fix this you’ll want to allocate a larger heap (using `-Xmx[numeric value here]`) to the process running the analysis. Some CI engines may give you an input to specify the necessary values, for instance if you’re using a Maven Build Step in a Jenkins job to run analysis. Otherwise, use Java Options to set a higher value. Note that details of setting Java Options are omitted here because they vary depending on the environment.

You can also add an exclusion to manage the files and folders you don’t need to analyze by limiting your [analysis-scope](https://docs.sonarsource.com/sonarqube-server/10.5/project-administration/analysis-scope "mention"). Additionally, using a Solid-state drive or something similar will help speed up the analysis process and thus use less memory, especially for small file access.

## PKIX path building failed <a href="#pkix-path-building-failed" id="pkix-path-building-failed"></a>

If your analysis errors out with `PKIX path building failed` then it means that your SonarQube server is configured with HTTPS and a self-signed SSL certificate (see **Securing the server behind a proxy** in [operating-the-server](https://docs.sonarsource.com/sonarqube-server/10.5/setup-and-upgrade/configure-and-operate-a-server/operating-the-server "mention")). However, the certificate is not correctly configured in the scanner machine’s JVM. This configuration is outside of SonarQube scope. The server certificate is unknown and could not be validated with the provided truststore. To solve the issue, you need to [install-self-signed-certificate](https://docs.sonarsource.com/sonarqube-server/10.5/analyzing-source-code/scanner-environment/install-self-signed-certificate "mention"). See [Oracle’s documentation](https://docs.oracle.com/cd/E19830-01/819-4712/ablqw/index.html) for more information.

## Various error messages <a href="#various" id="various"></a>

### The format of the analysis property sonar.token= is invalid <a href="#the-format-of-the-analysis-property-sonartoken-is-invalid" id="the-format-of-the-analysis-property-sonartoken-is-invalid"></a>

You may encounter this issue when using SONAR\_TOKEN as a secret in a calling workflow in GitHub in case the called workflow doesn’t manage to read it as a secret. In that case, make sure that the secret is inherited from the calling workflow (you may use the `secrets: inherit` keyword). See GitHub documentation for more information.

### The maximum number of open files was reached <a href="#the-maximum-number-of-open-files-was-reached" id="the-maximum-number-of-open-files-was-reached"></a>

On a Linux system, see **Configuring the maximum number of open files and other limits** in [linux](https://docs.sonarsource.com/sonarqube-server/10.5/setup-and-upgrade/pre-installation/linux "mention").

On a MacOS system, see **Configuring the maximum number of open files** in [macos](https://docs.sonarsource.com/sonarqube-server/10.5/setup-and-upgrade/pre-installation/macos "mention").