ERROR Error during SonarScanner CLI execution

SonarQube Server / Community Build
1

Hi Team,

I am facing the below error for some of the modules, other modules are working fine.
Error:

ERROR Error during SonarScanner CLI execution
java.lang.IllegalStateException: Failed to upload report: Error 413 on https://sonar-test-service.awn.sa/api/ce/submit?projectKey=fe_scanner_awn-dms-application

	at org.sonar.scanner.report.ReportPublisher.upload(ReportPublisher.java:224)
	... 20 common frames omitted
08:58:54.125 ERROR 
08:58:54.125 ERROR Re-run SonarScanner CLI using the -X switch to enable full debug logging.
WARN: Unable to locate 'report-task.txt' in the workspace. Did the SonarScanner succeed?
ERROR: SonarQube scanner exited with non-zero code: 1

full error log, please find.
Soar_Error.txt (13.2 KB)

~/sonarqube-9.9.0.65466/logs$ grep -nri “error” web.2025-03-10.log

1:2025.03.10 01:55:39 ERROR web[][o.a.c.h.Http11Processor] Error processing request
4:      at org.sonar.server.app.SecureErrorReportValve.invoke(SecureErrorReportValve.java:36)
16:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] l10nru.25.1.sqVersions should be defined
17:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] Plugin Russian Pack version 25.1 should declare compatible SQ versions
18:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] l10nzh.24.12.sqVersions should be defined
19:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] Plugin Chinese Pack version 24.12 should declare compatible SQ versions
20:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] l10nzh.25.1.sqVersions should be defined
21:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] Plugin Chinese Pack version 25.1 should declare compatible SQ versions
22:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] l10nzhtw.1.2.sqVersions should be defined
23:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] Plugin TraditionalChinese Pack version 1.2 should declare compatible SQ versions
24:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] openedge.2.30.0.sqVersions should be defined
25:2025.03.10 05:45:33 ERROR web[AZUk6GYzs4yCbaiJACvM][o.s.u.c.UpdateCenterDeserializer] Plugin OpenEdge version 2.30.0 should declare compatible SQ versions
2882:2025.03.10 11:45:24 INFO  web[][o.a.c.h.Http11Processor] Error parsing HTTP request header\n Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
2894:2025.03.10 11:45:24 ERROR web[][o.a.c.h.Http11Processor] Error processing request
2897:   at org.sonar.server.app.SecureErrorReportValve.invoke(SecureErrorReportValve.java:36)
2911:2025.03.10 21:07:13 ERROR web[][o.a.c.h.Http11Processor] Error processing request
2914:   at org.sonar.server.app.SecureErrorReportValve.invoke(SecureErrorReportValve.java:36)

Kindly help me to fix this issue.

Thank you!

3

Hi,

Did you read the error in your analysis log? It’s pretty clear:

08:58:54.123 ERROR Error during SonarScanner CLI execution
java.lang.IllegalStateException: Failed to upload report: Error 413 on https://sonar-test-service.awn.sa/api/ce/submit?projectKey=fe_scanner_awn-dms-application : <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.24.0 (Ubuntu)</center>

This is coming from your proxy, which isn’t tuned to let something as large as your analysis report through. You should talk to your network folks about this.

Yes, the behavior may vary by project because the size of the analysis report is relative to the project under analysis. You may also see projects that used to work stop working as the projects get bigger and/or more issues are found.

And BTW, these errors in your web.log are not only unrelated, but something you can ignore entirely (and something I’ve raised internally):

For these errors, I don’t have enough data to understand what’s going on with them. (Trimming the stacktraces as you have isn’t actually helpful, although I understand that they may have looked like junk.)

Since we try to keep it to one topic per thread (wtherwise it can get messy, fast), if you want to pursue those web.log errors, please create a new thread, with the full stacktraces.

 
Thx,
Ann

4

Thank you, @ganncamp ,
ERROR Error during SonarScanner CLI execution issue fixed.