SonarQube service exits with status 254

What does a status of 254 indicate? Are these documented somewhere?

– Support: Enterprise open source support | Ubuntu

– A start job for unit nexus.service has begun execution.

– The job identifier is 286554.
Sep 15 07:25:25 sunroom nexus[2734817]: Starting nexus
Sep 15 07:25:25 sunroom systemd[1]: Started SonarQube Service.
– Subject: A start job for unit nexus.service has finished successfully
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– A start job for unit nexus.service has finished successfully.

– The job identifier is 286554.
Sep 15 07:25:26 sunroom systemd[1]: nexus.service: Main process exited, code=exited, status=254/n/a
– Subject: Unit process exited
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– An ExecStart= process belonging to unit nexus.service has exited.

– The process’ exit code is ‘exited’ and its exit status is 254.
Sep 15 07:25:26 sunroom systemd[1]: nexus.service: Failed with result ‘exit-code’.
– Subject: Unit failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– The unit nexus.service has entered the ‘failed’ state with result ‘exit-code’.
Sep 15 07:25:44 sunroom tracker-store[2734626]: OK
Sep 15 07:25:44 sunroom systemd[2729793]: tracker-store.service: Succeeded.
– Subject: Unit succeeded
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– The unit UNIT has successfully entered the ‘dead’ state.
root@sunroom:/etc/systemd/system# mv nexus.service sonarqube.service
root@sunroom:/etc/systemd/system# systemctl daemon-reload
root@sunroom:/etc/systemd/system# systemctl status sonarqube.service
● sonarqube.service - SonarQube Service
Loaded: loaded (/etc/systemd/system/sonarqube.service; disabled; vendor preset: enabled)
Active: inactive (dead)
root@sunroom:/etc/systemd/system# systemctl enable sonarqube.service
Created symlink /etc/systemd/system/multi-user.target.wants/sonarqube.service → /etc/systemd/system/sonarqube.service.
root@sunroom:/etc/systemd/system# systemctl status sonarqube.service
● sonarqube.service - SonarQube Service
Loaded: loaded (/etc/systemd/system/sonarqube.service; enabled; vendor preset: enabled)
Active: inactive (dead)
root@sunroom:/etc/systemd/system# systemctl start sonarqube.service
root@sunroom:/etc/systemd/system# systemctl status sonarqube.service
● sonarqube.service - SonarQube Service
Loaded: loaded (/etc/systemd/system/sonarqube.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-09-15 07:26:57 EDT; 3s ago
Process: 2735584 ExecStart=/opt/app/sonartype/sonarqube/v3.34.0-01/bin/nexus start (code=exited, status=0/SUCCESS)
Main PID: 2735769 (code=exited, status=254)

Sep 15 07:26:57 sunroom systemd[1]: Starting SonarQube Service…
Sep 15 07:26:57 sunroom nexus[2735584]: Starting nexus
Sep 15 07:26:57 sunroom systemd[1]: Started SonarQube Service.
Sep 15 07:26:57 sunroom systemd[1]: sonarqube.service: Main process exited, code=exited, status=254/n/a
Sep 15 07:26:57 sunroom systemd[1]: sonarqube.service: Failed with result ‘exit-code’.

Hello @EdDowgiallo and welcome to the community :wave:

i think you are mixing things up here :sweat_smile: SonarType Nexus is not the same thing as SonarQube.

looking at the startup command you should head over to the folks at SonarType to help you.

If you want to setup SonarQube i would need you to clear the logs of the other services and explain to me what you already tried, as SonarQube can be started with systemd, but only with manual configuration.

Hope that helps :slight_smile:

It does. Sorry for the mixup, and thank you for replying quickly.

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