Must-share information (formatted with Markdown ): which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) SonarQube 10.1.0.73491 how is SonarQube deployed: zip, Docker, Helm Server is running on a standalone AWS EC2 instance connected to an AWS RDS instance sonar-s…

I Got the same error. The 05/21/2024 it was working with the latest version. The 05/27/2024 it was no more working. I’ve checked last docker releases of the sonnar-cli, and a latest has been released the 05/23/2024. So I’ve fixed the version of the sonnar-cli to : sonarsource/sonar-scanner-cli:5…

Hey @Drew_Morone and @JayPe69 Can you please provide DEBUG level analysis logs (sonar-scanner -X) that end with this error?

Thanks, I did try a previous version, not sure if it was this exact one. I’ll give it a try and let you know. Thanks

Hey Jean-Philippe, I tried this, and it seemed to work! Thanks! I have a question though, what is the host OS of your Docker instances? We’re using SonarQube in our Gitlab env. and noticed that when our runner instances updated from v16.11.1 to 17.0.0, this error started occurring. sonar-scanner is…

[image] Colin: DEBUG level analysis logs (sonar-scanner -X) Hey Colin, that’s in the original post, unless you mean something else?

Just want to add, regardless of whether I used: sonarsource/sonar-scanner-cli:5.0.1 or sonarsource/sonar-scanner-cli:latest The logs will show INFO: SonarScanner 5.0.1.3006 however, if I use the “latest” tag, the job fails. If I use the :5.0.1 tag, it works. I’m totally confused now.

You’re right, I didn’t realize they were at DEBUG mode. I’ve flagged this for attention. [image] Drew Morone: sonarsource/sonar-scanner-cli:5.0.1 or sonarsource/sonar-scanner-cli:latest The logs will show INFO: SonarScanner 5.0.1.3006 We recently changed the versioning strategy to decou…

Hi, The issue you described feel similar to the side effect of the Root user change: [image] Sonar execution is failing in sonar-scanner-cli:latest image SonarQube Hello, Sonar execution is failing in sonar-scanner-cli:latest image Could you please help us to resolve t…

Having the same issue here with sonarsource/sonar-scanner-cli:10.0, running in Gitlab CI, with gitlab-runner 17.0.0 RROR: Error during SonarScanner execution java.lang.IllegalStateException: Unable to load components interface org.sonar.api.batch.sensor.Sensor at org.sonar.core.platform.SpringComp…

Hey Csaba, I don’t think it’s related since I’m not using any plugins, which seems to be the issue with the linked article. The issue, for us, is resolved by just using a specific release as opposed to :latest.

Unable to load components interface org.sonar.api.batch.sensor.Sensor

SonarQube Server / Community Build

Csaba_Feher (Csaba Fehér) June 13, 2024, 1:06pm 11

Hi,

The issue you described feel similar to the side effect of the Root user change:

If this does not solve, could you please send me how you use the image within your GitLab workflow? Maybe a reproducer would be nice if possible.

Thanks
Csaba

Topic		Replies	Views
Unable to load components interface org.sonar.api.batch.sensor.Sensor SonarQube Server / Community Build java , sonarqube , scanner , coverage	2	191	February 28, 2025
Unable to load component error in Sonarqube 7.1 Developer Edition SonarQube Server / Community Build bug-no-category	4	1430	September 10, 2019
Sonar-scanner-cli:latest Failing on Gitlab CI SonarQube Cloud scanner , coverage , me-too	5	882	May 23, 2024
Scanner error on version 9.8 SonarQube Server / Community Build sonarqube	5	2036	April 17, 2023
Getting error while running sonar-scanner in gitlab CI/CD pipeline SonarQube Server / Community Build javascript , typescript , sonarqube , sonar-scanner	3	482	July 15, 2024

Unable to load components interface org.sonar.api.batch.sensor.Sensor

Related topics