We are currently using SonarQube Community Edition v8.0 and recently tried to upgrade to v8.6.1.
As mentioned in the documentation, we took a dump of our postgres db, reconfigured the properties.conf file accordingly and finally performed the upgrade with no issue.
However, a few hours later the SonarQube server started showing up as unavailable and in the logs we were receiving an error that the Elastic Search limits were too low. We thus increased the limits, rebooted our vm and re-ran the
sonar.sh script. We were now receiving no error in our logs, the SonarQube service status showed that it was successfully running, but when we were trying to connect through the web or publish a sonar analysis, we were receiving a
Connection Timed Out and
Server Unreachable accordingly.
What we’ve tried to resolve the issue but did not work:
- Make sure we were executing the
sonar.shscript as sonar user and not as root.
sonar.web.portproperties with the correct values.
- Set proper limits for:
- Perform a
VACUUM FULLon our db, just in case it was slowing down the server.
- We are using a reverse proxy so we also set:
setsebool -P httpd_can_network_connect 1.
Can anyone point us to the right direction about where we went wrong?
As previously mentioned, no errors showed up on our logs to guide us, everything seemed to be running smoothly, but the SonarQube server was inaccessible.