Hello SonarQube Community,
I am currently facing an issue where my SonarQube instance, after upgrading from version 10.6.0.92116 to 10.7.0.96327, remains stuck in the “SonarQube is starting” state indefinitely. I have gone through various troubleshooting steps but have not been able to get the application to fully start.
Environment Details
SonarQube Version: 10.7.0.96327
Previous Version: 10.6.0.92116 (which is working fine if I roll back)
Operating System: Red Hat Enterprise Linux 8.7
Java Version: JDK 17
Database: PostgreSQL
Troubleshooting Steps Attempted
Database Upgrade and Rollbacks:
Executed the database upgrade through url/setup as prompted. The upgrade failed, and I had to roll back the database snapshot and attempt again.
After rolling back, attempted multiple times, each resulting in the same issue.
Log Analysis and Increased Log Verbosity:
Set log levels to DEBUG and TRACE across SonarQube logs (web.log, es.log, sonar.log) for deeper insights.
Found extensive Elasticsearch logs but no clear errors in SonarQube logs. Elasticsearch logs show cluster formation and green health but no indication of why SonarQube cannot move past the starting state.
System Resource Allocation Adjustments:
Tried varying JVM memory allocations for sonar.ce.javaOpts and sonar.web.javaOpts.
Confirmed that both SonarQube and Elasticsearch processes have sufficient memory.
Verified that Elasticsearch is accessible and healthy on port 9001.
Confirmed no firewall issues between SonarQube and the database or Elasticsearch.
Despite these steps, SonarQube remains in a continuous restart loop, without successfully completing startup.