my sonarqube application/webportal is down,I have tried to bring it up but failed to do so,any help here?
I am using oracle database
Hello @kagabaj and welcome to the Community! Could you have a look at your server logs and see if there are any errors logged there? In particular, sonar.log is the file that most likely contains some hints, assuming your issue is with the startup. If the issue is with the web app, then you might find more hints on web.log.
I have actually checked on both files and I don’t see special error preventing the startup.
kindly support,regards
Could you share the logs here?
In sonar.log, do you see something like this:
2026.06.16 13:24:37 INFO app[][o.s.a.SchedulerImpl] SonarQube is operational
And in web.log, something like this:
2026.06.16 13:24:34 INFO web[][o.s.s.p.Platform] Web Server is operational
here are sonar.log
5.1.1.104738/elasticsearch -Des.path.conf=/var/sonarqube-2025.1.1.104738/temp/conf/es -Des.distribution.type=tar -cp /opt/sonarqube-2025.1.1.104738/elasticsearch/lib/:/opt/sonarqube-2025.1.1.104738/elasticsearch/lib/cli-launcher/ org.elasticsearch.launcher.CliToolLauncher
2026.06.11 09:21:28 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2026.06.11 09:21:33 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2026.06.11 09:21:33 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2026.06.11 09:21:33 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
and below are web.log
2026.06.10 02:17:05 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@17.0.9/jdk.internal.misc.Unsafe.park(Native Method)\n java.base@17.0.9/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)\n java.base@17.0.9/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1672)\n app//oracle.jdbc.internal.Monitor$WaitableMonitor.monitorWait(Monitor.java:325)\n app//oracle.jdbc.internal.Monitor$WaitableMonitor.monitorWait(Monitor.java:307)\n app//oracle.jdbc.driver.BlockSource$ThreadedCachingBlockSource$BlockReleaser.run(BlockSource.java:347)
2026.06.10 02:17:05 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [InterruptTimer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base@17.0.9/java.lang.Object.wait(Native Method)\n java.base@17.0.9/java.lang.Object.wait(Object.java:338)\n java.base@17.0.9/java.util.TimerThread.mainLoop(Timer.java:537)\n java.base@17.0.9/java.util.TimerThread.run(Timer.java:516)
2026.06.10 02:17:05 INFO web[o.s.p.ProcessEntryPoint] Hard stopping process
Hey @kagabaj, aha, so the logs from the main process (sonar.log) are telling you that the Elasticsearch process launched by the main process is erroring out. So the next step is to check the logs from the Elasticsearch process (es.log). What error do you see there?
The issue is mainly on the sonar.properties file,I have deployed a default sonar.properties file and the service has started
however when restoring the old sonar.properties file,the issuer perisisted
The one who has deployed the oracle external db was using port 1525,any ways to have clear configurations for this file in case of oracle db?
Could you share which differences are there between the 2 property files?
It would also be interesting to see if there’a an error in es.log. The logs you previously shared implied there might be.
the differerence was on the jdbc registration however the oracle db also refused to recognize the service and starts collectly
the DB issue is solved now the sonarqube services/elasticsearch refused to start with below logs;
2026.06.23 16:49:41 INFO es[o.e.n.NativeAccess] Using [jna] native provider and native methods for [Linux]
2026.06.23 16:49:41 ERROR es[o.e.b.Elasticsearch] fatal exception while booting Elasticsearch
java.lang.RuntimeException: can not run elasticsearch as root
at org.elasticsearch.bootstrap.Elasticsearch.initializeNatives(Elasticsearch.java:287) ~[elasticsearch-8.16.1.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:169) ~[elasticsearch-8.16.1.jar:?]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:74) ~[elasticsearch-8.16.1.jar:?]
not that I am not starting the services being a root user,I don’t know how that keeps coming and block the elasticsearch services to properly start.
This is a common issue, so common that it’s even documented: Elasticsearch-related issues | SonarQube Server | Sonar Documentation
You could check which user actually owns the process with something like:
ps -eo user,uid,cmd | egrep 'sonar|elastic' | grep -v egrep
This will let you confirm whether a systemd unit or wrapper is launching the JVM as root (a common pattern in similar cases).
this was fixed by rectifying some parameters.