SonarQube install issues

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)
  • how is SonarQube deployed: zip, Docker, Helm
  • what are you trying to achieve
  • what have you tried so far to achieve this

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

I have zero knowledge of SonarQube. I am installing it for the first time.
I have installed Postgresql14 using the following link.

I installed it offline due to that I am in a BLACKSITE.
I’m in step 5 of that link.
I have created the sonar.service file and placed everything that I am seeing.
When I try to enable the service, I am getting the following error.
Process ###### ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start (code=exited, status=203/EXEC)

I changed some of the stuff inside the sonar.service file.

ExecStart=/usr/bin/nohup /usr/bin/java -Xms32m -Xmx32m -Djava.net.preferIPv4Stack=true -jar /opt/sonarqube/lib/sonar-application-10.5.1.90531.jar

I run the enable again on the sonar.service and I am getting a differ error.
(code=exited, status=1/FAILURE)

Another issue I was having is, the instructions is asking to edit the sonar.sh file and set RUN_AS_USER=sonar.
That entry does not exist, and I am not certain where I need to add it in the .sh file.

What do the logs say?

Additionally, SonarQube v10.5.1 is EOL. Make sure you’re using the latest version.

Hello,

Sorry for the late response.
Let’s start over.
With that link you shared in mind, how do I install Sonarqube with the version that is on that link, to RHEL 8. Also, this RHEL 8 vm is offline and has no access to the postgres repo.
I am restarting the installation from the beginning.

Also, happy holidays.

I suggest you start with the docs on trying out SonarQube, or move onto installing a production instance, both cases are well documented.

So on this particular link.

4: Configure SonarQube
Step 5: Edit the sonar script file and set RUN_USER

I do not have “RUN_AS_USER=”
If I put this setting in there, where do I create this entry in the sonar.sh file?

You’re referring to nearly 2-year old unofficial documentation, not related to the version of SonarQube released a month or two ago. :slight_smile:

We don’t recommend trying to use RUN_AS_USER – if you want to start SonarQube with another user account, we suggest setting up SonarQube as a service, or using sudo – something like sudo -u sonar <sonarqubeHome>/bin/linux-x86-64/sonar.sh start

So I excluded the “RUN_AS_USER” from the instructions and I followed the rest of the instructions to edit the sonar.sh file.
Now I am having some trouble with the java. I know my java is not located in /opt/java.
I did a locate on java and I put every single output onto the sonar.sh file.
None of them worked. I put them in the file one at a time.
I made sure to disable, stop, and daemon-reload before I edited the file.
Each time, it failed.
I looked and noticed that I do have two differ java versions.
java-1.8.0-openjdk
java-11-openjdk
With this in mind, what am I supposed to put in the sonar.sh file as the path to java?

So after careful reading, I noticed that I cannot run sonarqube as a service due to having more than one java installed.
By using “update-alternative --config java” I pointed the java version to the correct java that sonarqube requires.
I manually started sonarqube and that seems to start properly.
I did make sure to start the service as “sonar”.
The output I get is:
/usr/bin/java
Staring SonarQube…
Started SonarQube.
I tried to bring up SonarQube on the browser but nothing seems to be happening.
Any suggestions?

I just saw my mistake. I was still running java 11 for the version of sonarqube I had. I did download the most current version and I just updated java to 17.
The gui is now up. I just have to put in our licensing information.
Thank you Colin for your help. I think just giving me that updated document helped me troubleshoot the rest on my own.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.