Sonarqube is not running - throwing error while starting up

Hi Team,

I am facing an issue with the installation of SonarQube. After installing the SonarQube with docker and it exited and logs are showing below errors. I suspected that this was the issue with connection to the SQL, but when I checked with PSQL client I was able to connect to the SQL with SQL certs. Could you help me on this issue pls? I am using 9.5 version of SonarQube Community Edition. Below are the logs:

I removed the SQL IP from the logs for security purposes.

ce.log

2022.07.27 06:57:11 DEBUG ce[][jdk.event.security]  TLSHandshake: <<SQL IP>>:5432, TLSv1.3, TLS_AES_128_GCM_SHA256, -1469443701
2022.07.27 07:07:11 DEBUG ce[][o.postgresql.Driver] Connecting with URL: jdbc:postgresql://<<SQL IP>>:5432/sonarqube?ssl=true&sslmode=verify-ca&sslrootcert=/opt/sonarqube/certs/server-ca.pem&sslkey=/opt/sonarqube/certs/client-key.der&sslcert=/opt/sonarqube/certs/client-cert.pem
2022.07.27 07:07:11 DEBUG ce[][o.p.c.v.ConnectionFactoryImpl] Trying to establish a protocol version 3 connection to 10.117.1.27:5432
2022.07.27 07:07:11 DEBUG ce[][o.p.c.v.ConnectionFactoryImpl] Receive Buffer Size is 183,680
2022.07.27 07:07:11 DEBUG ce[][o.p.c.v.ConnectionFactoryImpl] Send Buffer Size is 23,040
2022.07.27 07:07:11 DEBUG ce[][o.p.ssl.MakeSSL] converting regular socket connection to ssl
2022.07.27 07:07:11 DEBUG ce[][jdk.event.security] ValidationChain: -1716301095, -1469443701
2022.07.27 07:07:11 DEBUG ce[][jdk.event.security]  TLSHandshake: <<SQL IP>>:5432, TLSv1.3, TLS_AES_128_GCM_SHA256, -1469443701
2022.07.27 07:16:41 INFO  ce[][o.s.p.ProcessEntryPoint] Gracefully stopping process
2022.07.27 07:16:41 INFO  ce[][o.s.ce.app.CeServer] Compute Engine is stopping...
2022.07.27 07:16:41 INFO  ce[][o.s.c.t.CeProcessingSchedulerImpl] Gracefully stopping workers...
2022.07.27 07:16:41 DEBUG ce[][o.s.c.t.CeProcessingSchedulerImpl] Waiting for workers to finish in-progress tasks for at most 21600000ms
2022.07.27 07:16:41 DEBUG ce[][f.i.elonen.NanoHTTPD] Communication with the client broken
java.net.SocketException: Socket closed
        at java.base/java.net.PlainSocketImpl.socketAccept(Native Method)
        at java.base/java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:458)
        at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:565)
        at java.base/java.net.ServerSocket.accept(ServerSocket.java:533)
        at fi.iki.elonen.NanoHTTPD$ServerRunnable.run(NanoHTTPD.java:1769)
        at java.base/java.lang.Thread.run(Thread.java:829)
2022.07.27 07:16:41 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager is shutting down
2022.07.27 07:16:41 DEBUG ce[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager shut down
2022.07.27 07:16:41 INFO  ce[][o.s.ce.app.CeServer] Compute Engine is stopped

web.log

2022.07.27 07:03:35 DEBUG web[][jdk.event.security]  TLSHandshake: <<SQL IP>>:5432, TLSv1.3, TLS_AES_128_GCM_SHA256, -1469443701
2022.07.27 07:13:35 DEBUG web[][o.postgresql.Driver] Connecting with URL: jdbc:postgresql://<<SQL IP>>:5432/sonarqube?ssl=true&sslmode=verify-ca&sslrootcert=/opt/sonarqube/certs/server-ca.pem&sslkey=/opt/sonarqube/certs/client-key.der&sslcert=/opt/sonarqube/certs/client-cert.pem
2022.07.27 07:13:35 DEBUG web[][o.p.c.v.ConnectionFactoryImpl] Trying to establish a protocol version 3 connection to <<SQL IP>>:5432
2022.07.27 07:13:35 DEBUG web[][o.p.c.v.ConnectionFactoryImpl] Receive Buffer Size is 183,680
2022.07.27 07:13:35 DEBUG web[][o.p.c.v.ConnectionFactoryImpl] Send Buffer Size is 23,040
2022.07.27 07:13:35 DEBUG web[][o.p.ssl.MakeSSL] converting regular socket connection to ssl
2022.07.27 07:13:35 DEBUG web[][jdk.event.security] ValidationChain: -1716301095, -1469443701
2022.07.27 07:13:35 DEBUG web[][jdk.event.security]  TLSHandshake: <<SQL IP>>:5432, TLSv1.3, TLS_AES_128_GCM_SHA256, -1469443701
2022.07.27 07:16:41 INFO  web[][o.s.p.ProcessEntryPoint] Gracefully stopping process
2022.07.27 07:16:41 INFO  web[][o.s.s.n.NotificationDaemon] Notification service stopped
2022.07.27 07:16:41 DEBUG web[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager is shutting down
2022.07.27 07:16:41 DEBUG web[][o.a.h.i.n.c.ManagedNHttpClientConnectionImpl] http-outgoing-0 127.0.0.1:57084<->127.0.0.1:9001[ACTIVE][r:r]: Close
2022.07.27 07:16:41 DEBUG web[][o.a.h.i.n.c.InternalIODispatch] http-outgoing-0 [CLOSED]: Disconnected
2022.07.27 07:16:41 DEBUG web[][o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager shut down
2022.07.27 07:16:41 WARN  web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [logback-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@11.0.12/jdk.internal.misc.Unsafe.park(Native Method)\n java.base@11.0.12/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)\n java.base@11.0.12/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1170)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n java.base@11.0.12/java.lang.Thread.run(Thread.java:829)
2022.07.27 07:16:41 WARN  web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [logback-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@11.0.12/jdk.internal.misc.Unsafe.park(Native Method)\n java.base@11.0.12/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)\n java.base@11.0.12/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1170)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n java.base@11.0.12/java.lang.Thread.run(Thread.java:829)
2022.07.27 07:16:41 DEBUG web[][o.s.s.a.TomcatAccessLog] Tomcat is stopped
2022.07.27 07:16:41 INFO  web[][o.s.s.app.WebServer] WebServer stopped

Hey there.

What version of Java do you have installed that’s running your SonarQube instance?

Hi Colin,

Thanks for your reply. We are using REDHAT-8.4 with below version of java
openjdk version “11.0.15” 2022-04-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.15+9-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.15+9-LTS, mixed mode, sharing)

And sonarqube as docker image on the VM.

Thanks,
Prasad.

Thanks. My first thought was that it could be a version of Java not playing friendly with TLS 1.3… and I’m still not totally convinced that’s not the case. Could you try

  • Using the 9.6 image (it uses a newer version of Alpine Linux)
  • Try installing SonarQube manually (without Docker) and see if you face the same error
1 Like

Hi Colin,

When I run this docker image on another server I am able to run the container, able to launch the SonarQube on http, but when I use this on the Managed Instance group VM, we are facing issue.

On this server it worked after manually running the docker image:

sudo docker run -d --name sonarqube -p 9000:9000 -p 9092:9092 :19072022

Linux hostname 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

openjdk version “1.8.0_312”
OpenJDK Runtime Environment (build 1.8.0_312-b07)
OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)

MIG VM Version:

Linux sonarqube 4.18.0-372.13.1.el8_6.x86_64 #1 SMP Mon Jun 6 15:05:22 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux

openjdk version “11.0.15” 2022-04-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.15+9-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.15+9-LTS, mixed mode, sharing)

There is no problem with the image as I could run the image on another VM as stated above

Thanks,
Prasad.

Did you run this with the JDBC configuration?

    -e SONAR_JDBC_URL=... \
    -e SONAR_JDBC_USERNAME=... \
    -e SONAR_JDBC_PASSWORD=... \
1 Like

Hi Colin,

I have ran the docker as you mentioned but facing same issue: compute engine is starting at all.

2022.07.27 07:07:11 DEBUG ce[o.postgresql.Driver] Connecting with URL: jdbc:postgresql://<>:5432/sonarqube?ssl=true&sslmode=verify-ca&sslrootcert=/opt/sonarqube/certs/server-ca.pem&sslkey=/opt/sonarqube/certs/client-key.der&sslcert=/opt/sonarqube/certs/client-cert.pem
2022.07.27 07:07:11 DEBUG ce[o.p.c.v.ConnectionFactoryImpl] Trying to establish a protocol version 3 connection to <>:5432
2022.07.27 07:07:11 DEBUG ce[o.p.c.v.ConnectionFactoryImpl] Receive Buffer Size is 183,680
2022.07.27 07:07:11 DEBUG ce[o.p.c.v.ConnectionFactoryImpl] Send Buffer Size is 23,040
2022.07.27 07:07:11 DEBUG ce[o.p.ssl.MakeSSL] converting regular socket connection to ssl
2022.07.27 07:07:11 DEBUG ce[jdk.event.security] ValidationChain: -1716301095, -1469443701
2022.07.27 07:07:11 DEBUG ce[jdk.event.security] TLSHandshake: <>:5432, TLSv1.3, TLS_AES_128_GCM_SHA256, -1469443701
2022.07.27 07:16:41 INFO ce[o.s.p.ProcessEntryPoint] Gracefully stopping process
2022.07.27 07:16:41 INFO ce[o.s.ce.app.CeServer] Compute Engine is stopping…
2022.07.27 07:16:41 INFO ce[o.s.c.t.CeProcessingSchedulerImpl] Gracefully stopping workers…
2022.07.27 07:16:41 DEBUG ce[o.s.c.t.CeProcessingSchedulerImpl] Waiting for workers to finish in-progress tasks for at most 21600000ms
2022.07.27 07:16:41 DEBUG ce[f.i.elonen.NanoHTTPD] Communication with the client broken
java.net.SocketException: Socket closed
at java.base/java.net.PlainSocketImpl.socketAccept(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:458)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:565)
at java.base/java.net.ServerSocket.accept(ServerSocket.java:533)
at fi.iki.elonen.NanoHTTPD$ServerRunnable.run(NanoHTTPD.java:1769)
at java.base/java.lang.Thread.run(Thread.java:829)
2022.07.27 07:16:41 DEBUG ce[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager is shutting down
2022.07.27 07:16:41 DEBUG ce[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager shut down
2022.07.27 07:16:41 INFO ce[o.s.ce.app.CeServer] Compute Engine is stopped

in Web.log:

2022.07.27 07:16:41 DEBUG web[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager is shutting down
2022.07.27 07:16:41 DEBUG web[o.a.h.i.n.c.ManagedNHttpClientConnectionImpl] http-outgoing-0 127.0.0.1:57084<->127.0.0.1:9001[ACTIVE][r:r]: Close
2022.07.27 07:16:41 DEBUG web[o.a.h.i.n.c.InternalIODispatch] http-outgoing-0 [CLOSED]: Disconnected
2022.07.27 07:16:41 DEBUG web[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection manager shut down
2022.07.27 07:16:41 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [logback-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@11.0.12/jdk.internal.misc.Unsafe.park(Native Method)\n java.base@11.0.12/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)\n java.base@11.0.12/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1170)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n java.base@11.0.12/java.lang.Thread.run(Thread.java:829)
2022.07.27 07:16:41 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [logback-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@11.0.12/jdk.internal.misc.Unsafe.park(Native Method)\n java.base@11.0.12/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)\n java.base@11.0.12/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1170)\n java.base@11.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)\n java.base@11.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n java.base@11.0.12/java.lang.Thread.run(Thread.java:829)
2022.07.27 07:16:41 DEBUG web[o.s.s.a.TomcatAccessLog] Tomcat is stopped
2022.07.27 07:16:41 INFO web[o.s.s.app.WebServer] WebServer stopped

Thanks,
Prasad.