Fail to request https://host/batch/project.protobuf?key=key&branch=master

  • SonarQube Version: Community EditionVersion 7.9.4 (build 35981)

  • Scanner Version:sonar-scanner-3.0.3.778-linux

  • Plugin Version: Sonar for Bamboo v. 2.7.3

  • How SonarQube is deployed: Onpremise Server

  • What you are trying to achieve? : To resolve the error you’re seeing in the log that’s preventing successful execution.

The Log error is:

ERROR: Error during SonarQube Scanner execution
java.lang.IllegalStateException: java.lang.IllegalStateException: Fail to request https://host/batch/project.protobuf?key=key&branch=master
at org.sonar.scanner.scan.filesystem.MetadataGenerator.setMetadata(MetadataGenerator.java:72)
at org.sonar.scanner.scan.filesystem.FileIndexer.lambda$indexFile$0(FileIndexer.java:134)
at org.sonar.api.batch.fs.internal.DefaultInputFile.checkMetadata(DefaultInputFile.java:91)
at org.sonar.api.batch.fs.internal.DefaultInputFile.charset(DefaultInputFile.java:230)

What you have tried so far to achieve this ?:

I have tested the connectivity from the server where Sonar Scanner is located to the SonarQube server by sending a curl with the URL of the SonarQube server. The response was a 200 code, up to this part of the URL: (https://host/batch/)

When I send the curl with the other part of the URL: (https://host/batch/project.protobuf?key=key&branch=master), I receive a 401 code, which means the resource is not found.

This was working correctly until April 4th of this year, then executions were performed on Monday, April 10th and this issue appeared.

I hope that you can help me find the solution. Thanks in advance

Hi,

Your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:

7.9.4 → 8.9.10 → 9.9 → 10.0 (optional)

You may find the Upgrade Guide and the LTS-to-LTS Upgrade Notes for 7.9 to 8.9, as well as the LTS to LTS release upgrade notes for 8.9 to 9.9 helpful. If you have questions about upgrading, feel free to open a new thread for that here.

If your error persists after upgrade, please come back to us.