Sonar issue after postgresql upgrade

Sonar developer version: 8.6.1
AWS RDS Aurora PostgreSQL: 11.9

Issue:
Postgres was upgraded from 9.16.6 to 11.9
RDS CPU is 99%
Increased compute resources from 2VCPUs/16GB RAM to 4VCPU/32GB RAM

Error:
Facing below error while running Sonarscan on Java code
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project xxx-xx: Unable to execute SonarQube: Fail to get bootstrap index from server: Status returned by url [[MASKED]/batch/index] is not valid: [504] → [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project lpr-mx: Unable to execute SonarQube

Hi,

Welcome to the community!

A 504 is a timeout. So the question is: what’s going on at the server that caused it not to respond to the request. Can you check your server logs for errors? If there’s nothing there, then I would look to the network and make sure the request is actually being received.

 
Ann

I think I have seen this before. Try a vacuum(full, analyze) to recreate the db indexes.

More information here on additional database maintenence Upgrade Guide | SonarQube Docs

1 Like

Issue got fixed after upgrading the Sonar developer version to 8.9 & PostgreSQL to 11.9

1 Like

The VACUUM FULL worked for me as well, upgrading from Aurora Postgresql 9.16 to 10

1 Like