Unable to execute SonarScanner analysis: Status returned by url [http://SERVER_IP:9000/batch/file?name=sonar-scanner-engine-shaded-8.9.0.43852-all.jar] is not valid: [503]

SonarQube
,
1

  • I have upgraded sonarqube from ‘7.9.6’ to ‘8.9.0.43852’

  • Upgrade completed successfully. But, when i trying to scan the code with new version of sonarqube I’m facing below error.

[ERROR] SonarQube server [http://SERVER_IP:9000] can not be reached.

Unable to execute SonarScanner analysis: Status returned by url [http://SERVER_IP:9000/batch/file?name=sonar-scanner-engine-shaded-8.9.0.43852-all.jar] is not valid: [503]

  • There is no ERROR in sonarqube server logs.

  • Following WARNINGS are there in web.log

2021.10.26 01:22:08 WARN  web[][o.s.s.p.PluginJarLoader] Use of 'Plugin-Dependencies' mechanism is planned for removal. Update the plugin PMD [pmd] to shade its dependencies instead.
2021.10.26 01:22:08 WARN  web[][o.s.s.p.PluginJarLoader] Use of 'Plugin-Dependencies' mechanism is planned for removal. Update the plugin Findbugs [findbugs] to shade its dependencies instead.

2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/plugins/download
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/permissions/search_templates
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/list_bitbucketserver_projects
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/check_pat
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/list_azure_projects
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/search_bitbucketserver_repos
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/search_azure_repos
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/list_github_organizations
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/list_github_repositories
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_integrations/get_github_client_id
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_settings/get_binding
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_settings/list
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_settings/list_definitions
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_settings/count_binding
2021.10.26 01:22:10 WARN  web[][o.s.a.s.w.WebService$Action] The response example is not set on action api/alm_settings/validate
2

Hi,

Anything in your other server logs? Any errors earlier in your web.log?

503 is a server error, so there should be corresponding errors in the SQ logs (likely web.log) but if you’re not seeing any errors there, then is there something on the network, e.g. a proxy, that could be interfering and returning this error?

 
Ann

3

Hello Ann,

Appreciate your quick response!!

I am able to proceed with the scanning through command line (Tried on the same instance where our GitLab runner is running). Project report published successfully to the SonarQube.

But, when i am triggering the SonarQube pipeline from GitLab, I’m facing below server not reachable issue.
[ERROR] SonarQube server [http://SERVER_IP:9000] can not be reached.

Note: I am using the same set of commands in the Gitlab pipline, what i tried on the command line.

Sonarqube Version: 8.9.0.43852

Thanks for your help,
Muthukumar

4

Hi Muthukumar,

You’ve demonstrated that analysis works and that connection from the build agent machine works. It looks like it’s just GitLab that’s the problem & unfortunately that’s out of scope for me.

 
:woman_shrugging:
Ann