Must-share information (formatted with Markdown):
- which versions are you using Sonarqube 8.9.4 (it will be upgraded as soon as I can)
- how is SonarQube deployed: zip
- what are you trying to achieve: get Sonarqube running on a new server
- what have you tried so far to achieve this: Installed sonarqube, copied over sonar.properties and all other pertinent files from old server.
Good day folks. I have a single-server Sonarqube installation that I am trying to move from a RHEL7 server to a new RHEL8 server that for some reason will simply just refuse to come up and online. Unfortunately it is on an air-gapped network so I am unable to share any logs or anything but I will try my best to summarize what is happening.
Sonarqube says that it is staring up, it creates a sonar.log file, and the service shows as ‘running’. Lots of entries in the sonar.log indicating ‘connection refused’ to port 9001. Elasicsearch tries to start but never really does - an es.log file is created and has entries indicating ‘java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native’. Not sure if that is relavent or not but that’s the only real anomaly I see in the log. I can assume that Elasticsearch never starts because port 9001 never opens (neither does port 9000 so maybe Sonarqube really isn’t running like it indicates it is???).
Looking at the database server logs, there never is a connection from the server, so apparently it’s never even getting to the “connect to database” stage. No other logs are ever created either - only the sonar.log and the es.log - so it’s dying before any of the other ‘services’ get up and running and creating their log files.
If anyone is still reading this long-winded post you might recall I had a few posts a couple of weeks ago in regards to FIPS blocking Sonarqube from running. I disabled FIPS on that server and Sonarqube is running fine. I disable FIPS on this server and it STILL won’t run. Any insight would be appreciated!