Stopping Sonarqube takes a long time

SonarQube Server / Community Build 9.9 LTA Upgrade
1

Make sure to tell us:

  • What version are you upgrading from? 9.9
  • System information (Operating system, Java version, Database provider/version) RHEL 8, Postgres 14.12
  • What’s the issue you’re facing?

I stopped sonar services via ./sonar.sh stop and it’s taking a long time. I checked sonar.log and it’s blocked at Compute Engine process.

[sonar@pgm010b07 logs]$ tail -f sonar.log
2024.09.16 04:12:12 WARN  app[][startup] ################################################################################
2024.09.16 04:12:12 WARN  app[][startup] The database must be manually upgraded. Please backup the database and browse /setup. For more information: https://docs.sonarqube.org/latest/setup/upgrading
2024.09.16 04:12:12 WARN  app[][startup] ################################################################################
2024.09.16 04:14:48 INFO  app[][o.s.a.SchedulerImpl] Process[web] is up
2024.09.16 04:14:48 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[COMPUTE_ENGINE] from [/opt/sonarqube-9.9.6.92038]: /usr/lib/jvm/java-17-openjdk-17.0.11.0.9-2.el8.x86_64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube-9.9.6.92038/temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -Dcom.redhat.fips=false -Xmx2G -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-9.9.6.92038.jar:/opt/sonarqube-9.9.6.92038/lib/jdbc/postgresql/postgresql-42.5.1.jar org.sonar.ce.app.CeServer /opt/sonarqube-9.9.6.92038/temp/sq-process2917773394386030116properties
2024.09.16 04:14:52 INFO  app[][o.s.a.SchedulerImpl] Process[ce] is up
2024.09.16 04:14:52 INFO  app[][o.s.a.SchedulerImpl] SonarQube is operational
2024.09.16 04:38:39 INFO  app[][o.s.a.SchedulerImpl] Stopping SonarQube
2024.09.16 04:38:39 INFO  app[][o.s.a.SchedulerImpl] Sonarqube has been requested to stop
2024.09.16 04:38:39 INFO  app[][o.s.a.SchedulerImpl] Stopping [Compute Engine] process...

I just wanted to put the start and stop process of sonar.sh in the systemctl that’s why I stopped it. Any idea how to proceed with this issue?

2

I am already unblocked. Killed the process and restarted sonarqube, software started successfully after putting it in systemctl.

3

Hi,

I’m glad your unblocked.

For the sake of posterity, I wanted to drop a note here that the “usual suspect” for the CE process being slow to shut down is that it’s in the middle of processing an analysis report. If you’re certain that’s not the case, then I suppose it’s fine to force-kill it. Otherwise, you probably want to give it the time to finish what it’s doing.

 
Ann