ERROR Error during SonarScanner Engine execution

SonarQube Server / Community Build
,
1

Version I am using:

  • SonarQube: Enterprise 10.6.0.92116

  • Scanner: sonar-scanner-6.2.1.4610-macosx-aarch64(installed on Linux node)

  • SonarQube is running on a Windows agent installed via zip

  • Node: Linux

  • what are you trying to achieve:
    We recently update SonarQube from 9.9 LTA to 10.6. and upgraded Java to 17 from 11 as well. Now when we try to run the project in Jenkins we are getting this error. It was running successfully before, but now it’s throwing this error, which we can’t seem to figure it out.

Here is the logs :

15:34:23.289 DEBUG Missing headers stats: [opengl/gltypes.h(1);opengl/(1)]
15:34:23.289 INFO  79 compilation units analyzed
15:34:23.289 DEBUG CFamily Java memory usage statistics (used, peak) with initial 73MB used:
At the end of analysis setup: 50MB, 94MB
At the end of lexical analysis: 89MB, 101MB
At the end of analysis requests computation: 96MB, 108MB
At the end of the analysis: 85MB, 110MB
At the end of the sensor: 40MB , 105MB
Note that these values may not be accurate due to garbage collection; they should only be used to detect significant outliers.
15:34:23.345 ERROR Error during SonarScanner Engine execution
java.lang.IllegalArgumentException: group id '55320096' is too big ( > 2097151 ). Use STAR or POSIX extensions to overcome this limit
	at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.failForBigNumber(TarArchiveOutputStream.java:385)
	at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.failForBigNumberWithPosixMessage(TarArchiveOutputStream.java:401)
	at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.failForBigNumbers(TarArchiveOutputStream.java:392)
	at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.putArchiveEntry(TarArchiveOutputStream.java:555)
	at com.sonar.cpp.plugin.CFamilySensor.addTarEntry(CFamilySensor.java:367)
	at com.sonar.cpp.plugin.CFamilySensor.addTarEntry(CFamilySensor.java:362)
	at com.sonar.cpp.plugin.CFamilySensor.createReproducerArchive(CFamilySensor.java:336)
	at com.sonar.cpp.plugin.CFamilySensor.execute(CFamilySensor.java:190)
	at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(AbstractSensorWrapper.java:64)
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:88)
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:64)
	at org.sonar.scanner.scan.SpringModuleScanContainer.doAfterStart(SpringModuleScanContainer.java:82)
	at org.sonar.core.platform.SpringComponentContainer.startComponents(SpringComponentContainer.java:226)
	at org.sonar.core.platform.SpringComponentContainer.execute(SpringComponentContainer.java:205)
	at org.sonar.scanner.scan.SpringProjectScanContainer.scan(SpringProjectScanContainer.java:204)
	at org.sonar.scanner.scan.SpringProjectScanContainer.scanRecursively(SpringProjectScanContainer.java:200)
	at org.sonar.scanner.scan.SpringProjectScanContainer.doAfterStart(SpringProjectScanContainer.java:173)
	at org.sonar.core.platform.SpringComponentContainer.startComponents(SpringComponentContainer.java:226)
	at org.sonar.core.platform.SpringComponentContainer.execute(SpringComponentContainer.java:205)
	at org.sonar.scanner.bootstrap.SpringScannerContainer.doAfterStart(SpringScannerContainer.java:351)
	at org.sonar.core.platform.SpringComponentContainer.startComponents(SpringComponentContainer.java:226)
	at org.sonar.core.platform.SpringComponentContainer.execute(SpringComponentContainer.java:205)
	at org.sonar.scanner.bootstrap.SpringGlobalContainer.doAfterStart(SpringGlobalContainer.java:144)
	at org.sonar.core.platform.SpringComponentContainer.startComponents(SpringComponentContainer.java:226)
	at org.sonar.core.platform.SpringComponentContainer.execute(SpringComponentContainer.java:205)
	at org.sonar.scanner.bootstrap.ScannerMain.runScannerEngine(ScannerMain.java:149)
	at org.sonar.scanner.bootstrap.ScannerMain.run(ScannerMain.java:66)
	at org.sonar.scanner.bootstrap.ScannerMain.main(ScannerMain.java:52)

15:34:23.347 DEBUG Cleanup org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda$346/0x0000000800356828@35ff8fc9 during JVM shutdown
15:34:23.355 DEBUG Java command exited with code 1
15:34:23.355 INFO  EXECUTION FAILURE
2

Hi,

Welcome to the community!

Could we have the full analysis log, starting from the analysis command itself, please?

 
Thx,
Ann

3

I can’t send it. It’s not a personal project. Is there any way to send it privately? Also to explain situation better, we have out SonarQube service running on Jenkins windows node as services. We recently updated the SonarQube to 10.6 and also added java 17 path on both node, windows and mac. Windows projects are running fine but the problem is on the iOS project.

6

Hi @khusi, and welcome to the community,

I can see two separate problems from the logs:

  1. The CFamily analyzer was not able to resolve an include to opengl/gltypes.h in the project. This can happen if the compile_commands.json or build-wrapper output directory don’t have the correct include directories for some reason. When the analyzer detects the issue, it usually logs a warning with a reproducer file that you can share with us to aid with tracking down the problem. If you still have access to the old analysis logs, you can check if this problem was already existent in the old version by looking for a log entry starting with "The analyzer was not able to find file".

  2. While trying to create the reproducer in 1, the analyzer hits a bug CPP-5472, and crashes with a different stack trace as a result.

I would suggest the following:

  1. The bug I mentioned was resolved in SQ 10.7, so upgrading should resolve the issue, but it doesn’t resolve the underlying problem (why the analyzer fails to resolve the header). If updating can’t be done at the moment, a workaround is to run the analysis is a user whose UID is less than 2097151 (if possible).
  2. Try to understand why the generated compilation database doesn’t have the needed information to resolve opengl/gltypes.h. For example, does analysis happen on the same host where build took place? Are the paths where you have this library installed accessible to the analyzer? Solving this can increase the analysis quality, and help the analyzer detect issues more accurately.

I am also starting a private thread in case you would like to share more information…

I hope this helps,
Best regards,
Michael

7

Thank You!! Upgrade resolved the issue.

1 Like