I am using SonarQube 7.4 Community Edition on RHEL 7.6, and have followed all requirements as per documentation on https://docs.sonarqube.org/7.4/
How to reproduce
./bin/linux-x86-64/sonar.sh start shows that SonarQube is running, and it is indeed running by subsequently connecting to port 9000 through browser.
However, even while SonarQube service is running, PID file (
./temp/SonarQube.pid) disappears within few seconds, just after “Started SonarQube” message appears, and before shell script ends. I have verified this by adding debug messages within shell script.
Due to disappearance of a PID file,
./bin/linux-x86-64/sonar.sh stop and
./bin/linux-x86-64/sonar.sh status which checks for presence of PID file complains that SonarQube is not running.
Though not a foolproof method, I am considering a workaround that “start()” function of
sonar.sh will create a PID file few seconds after wrapper is run, and PID file vanishes.
Do you face similar issues on Linux system, and if yes, any suggestions to resolve this issue?