Sonarqube service is not running

SonarQube Server / Community Build
1

Ubuntu 20 with Latest sonarqube package.

sudo systemctl status sonar
● sonar.service - SonarQube service
Loaded: loaded (/etc/systemd/system/sonar.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2022-08-23 08:28:43 UTC; 8s ago
Process: 3096 ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start (code=exited, status=0/SUCCESS)
Process: 3120 ExecStop=/opt/sonarqube/bin/linux-x86-64/sonar.sh stop (code=exited, status=0/SUCCESS)

Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3096]: /usr/bin/java
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3096]: Starting SonarQube…
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3096]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3119]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create …/…/logs/nohup.log: Permission denied
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3096]: Failed to start SonarQube.
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3120]: /usr/bin/java
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3120]: Gracefully stopping SonarQube…
Aug 23 08:28:43 ip-192-168-0-116 sonar.sh[3120]: SonarQube was not running.
Aug 23 08:28:43 ip-192-168-0-116 systemd[1]: sonar.service: Succeeded.
Aug 23 08:28:43 ip-192-168-0-116 systemd[1]: Started SonarQube service.

3

Updated the sonar.service file as per the document from Sonarqube URL:

image
image1321×800 50.7 KB

ERROR:

sudo systemctl status sonar.service
● sonar.service - SonarQube service
Loaded: loaded (/etc/systemd/system/sonar.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-08-23 10:16:20 UTC; 33s ago
Process: 5350 ExecStart=/bin/nohup /lib/jvm/java-11-openjdk-amd64 -Xms32m -Xmx32m -Djava.net.preferIPv4Stack=true -jar /opt/sonarqube/lib/sonar-application-9.6.0.59041.jar (>
Main PID: 5350 (code=exited, status=217/USER)

Aug 23 10:16:20 ip-192-168-0-116 systemd[1]: sonar.service: Scheduled restart job, restart counter is at 5.
Aug 23 10:16:20 ip-192-168-0-116 systemd[1]: Stopped SonarQube service.
Aug 23 10:16:20 ip-192-168-0-116 systemd[1]: sonar.service: Start request repeated too quickly.
Aug 23 10:16:20 ip-192-168-0-116 systemd[1]: sonar.service: Failed with result ‘exit-code’.
Aug 23 10:16:20 ip-192-168-0-116 systemd[1]: Failed to start SonarQube service.

4

Hi @sandeepraj and welcome to the community :wave:

Anything interesting in the logs (logs folder in your sonarqube directory) or in the journal (journalctl -u sonar)?

5

– Logs begin at Mon 2022-08-08 12:09:21 UTC, end at Wed 2022-08-24 06:06:30 UT>

Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: /usr/bin/java
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: Starting SonarQube...
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: /opt/sonarqube/bin/linux-x86-6>
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: Failed to start SonarQube.
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5974]: /opt/sonarqube/bin/linux-x86-6>
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: sonar.service: Main process exited>
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: sonar.service: Failed with result >
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: sonar.service: Scheduled restart j>
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Stopped SonarQube service.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: /usr/bin/java
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: Starting SonarQube...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: /opt/sonarqube/bin/linux-x86-6>
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5999]: /opt/sonarqube/bin/linux-x86-6>
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: Failed to start SonarQube.
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: /usr/bin/java
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: Gracefully stopping SonarQube.>
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: SonarQube was not running.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: sonar.service: Succeeded.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Started SonarQube service.
lines 1-23...skipping...
-- Logs begin at Mon 2022-08-08 12:09:21 UTC, end at Wed 2022-08-24 06:06:30 UTC. --
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: /usr/bin/java
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: Starting SonarQube...
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: Failed to start SonarQube.
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5974]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: sonar.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: sonar.service: Failed with result 'exit-code'.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: sonar.service: Scheduled restart job, restart counter is at 1.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Stopped SonarQube service.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: /usr/bin/java
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: Starting SonarQube...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5999]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: Failed to start SonarQube.
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: /usr/bin/java
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: Gracefully stopping SonarQube...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: SonarQube was not running.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: sonar.service: Succeeded.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: /usr/bin/java
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: Starting SonarQube...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: Failed to start SonarQube.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6069]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Failed with result 'exit-code'.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Scheduled restart job, restart counter is at 1.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Stopped SonarQube service.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6070]: /usr/bin/java
lines 1-36...skipping...
-- Logs begin at Mon 2022-08-08 12:09:21 UTC, end at Wed 2022-08-24 06:06:30 UTC. --
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: /usr/bin/java
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: Starting SonarQube...
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5951]: Failed to start SonarQube.
Aug 17 11:06:38 ip-192-168-0-116 sonar.sh[5974]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: sonar.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 17 11:06:38 ip-192-168-0-116 systemd[1]: sonar.service: Failed with result 'exit-code'.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: sonar.service: Scheduled restart job, restart counter is at 1.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Stopped SonarQube service.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: /usr/bin/java
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: Starting SonarQube...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5999]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[5976]: Failed to start SonarQube.
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: /usr/bin/java
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: Gracefully stopping SonarQube...
Aug 17 11:06:39 ip-192-168-0-116 sonar.sh[6000]: SonarQube was not running.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: sonar.service: Succeeded.
Aug 17 11:06:39 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: /usr/bin/java
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: Starting SonarQube...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6046]: Failed to start SonarQube.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6069]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Failed with result 'exit-code'.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Scheduled restart job, restart counter is at 1.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Stopped SonarQube service.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6070]: /usr/bin/java
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6070]: Starting SonarQube...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6070]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 162: cannot create ./SonarQube.pid: Permission denied
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6093]: /opt/sonarqube/bin/linux-x86-64/sonar.sh: 161: cannot create ../../logs/nohup.log: Permission denied
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6070]: Failed to start SonarQube.
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6094]: /usr/bin/java
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6094]: Gracefully stopping SonarQube...
Aug 17 11:10:55 ip-192-168-0-116 sonar.sh[6094]: SonarQube was not running.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: sonar.service: Succeeded.
Aug 17 11:10:55 ip-192-168-0-116 systemd[1]: Started SonarQube service.
Aug 18 04:31:15 ip-192-168-0-116 systemd[1]: Starting SonarQube service...
Aug 18 04:31:15 ip-192-168-0-116 sonar.sh[11459]: /usr/bin/java
Aug 18 04:31:15 ip-192-168-0-116 sonar.sh[11459]: Starting SonarQube...
6

So you have a permission problem. The user specified in the systemd service does not have the required permissions to create these files.

I am confused tho. Didn’t you wrote that you updated the systemd service to match what is in the documentation? The sonar.sh script should not be called anymore with that. Did you maybe forget to reload the systemd daemon (sudo systemctl daemon-reload)?