Sonarqube-7.9.1 HeapDumpOnOutOfMemoryError - sonarqube

I installed sonarqube-7.9.1 on my Ubuntu 18.04 machine. JAVA 11 is installed and Mysql used as database.
Some important rows from sonar.properties are as follows
sonar.web.javaOpts=-Xmx1024m -Xms1024m -XX:+HeapDumpOnOutOfMemoryError
sonar.web.host=127.0.0.1
sonar.ce.javaOpts=-Xmx1024m -Xms1024m -XX:+HeapDumpOnOutOfMemoryError
Sonarqube log file shows following lines
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2019.10.17 12:36:49 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/sonarqube-7.9.1/temp
2019.10.17 12:36:49 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.10.17 12:36:49 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/sonarqube-7.9.1/elasticsearch]: /opt/sonarqube/sonarqube-7.9.1/elasticsearch/bin/elasticsearch
2019.10.17 12:36:49 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2019.10.17 12:36:49 INFO app[][o.e.p.PluginsService] no modules loaded
2019.10.17 12:36:49 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.10.17 12:37:01 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2019.10.17 12:37:01 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube/sonarqube-7.9.1]: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/sonarqube-7.9.1/temp --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED -Xmx1024m -Xms1024m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*:/opt/sonarqube/sonarqube-7.9.1/lib/jdbc/mysql/mysql-connector-java-5.1.46.jar org.sonar.server.app.WebServer /opt/sonarqube/sonarqube-7.9.1/temp/sq-process4977560398960418438properties
2019.10.17 12:37:04 INFO app[][o.s.a.SchedulerImpl] Process[web] is stopped
2019.10.17 12:37:05 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143
2019.10.17 12:37:05 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped
2019.10.17 12:37:05 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped

I was also getting the same issue of starting Sonarqube-7.9.1 with OpenJDK-11 because of the port conflicts. I tried changing port numbers and issue got resolved. Try replacing below lines in sonar.properties:
sonar.web.port=9004
sonar.search.port=9005
we can replace below lines also,already given in this question at the start [For me it worked without replacing below lines]:
sonar.web.javaOpts=-Xmx1024m -Xms1024m -XX:+HeapDumpOnOutOfMemoryError
sonar.ce.javaOpts=-Xmx1024m -Xms1024m -XX:+HeapDumpOnOutOfMemoryError

I believe SonarQube is not starting for any reason related to memory but rather from the fact that you attempt to connect to MySQL Database and this DB is not supported anymore (see "Release 7.9 LTS Upgrade Notes" at https://docs.sonarqube.org/latest/setup/upgrade-notes/).
Have a look at web.log (see "Checking the logs" at https://docs.sonarqube.org/latest/setup/troubleshooting/) to confirm it, you will find a clear message there.

Related

ElasticSearch-based problem when starting Sonarqube: 944 main ERROR Unable to locate plugin type for IfFileName

I've recently unpacked sonarqube-8.1.0.31237, installed Oracle Java 11 SDK, set Environment Parameters for JAVA_HOME and PATH. When I try to start sonarqube, several errors are logged regarding ElasticSearch.
At sonarqube website, it recommends deleting es6 directory and starting it again but it doesn't work.
Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
Log
2020.01.31 10:43:14 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory D:\EclUtil\sonarqube-8.1.0.31237\sonarqube-8.1.0.31237\temp
2020.01.31 10:43:14 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2020.01.31 10:43:14 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [D:\EclUtil\sonarqube-8.1.0.31237\sonarqube-8.1.0.31237\elasticsearch]: C:\Program Files (x86)\Java\jdk-11.0.6\bin\java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=D:\EclUtil\sonarqube-8.1.0.31237\sonarqube-8.1.0.31237\temp -XX:ErrorFile=../logs/es_hs_err_pid%p.log -Xmx512m -Xms512m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=D:\EclUtil\sonarqube-8.1.0.31237\sonarqube-8.1.0.31237\elasticsearch -Des.path.conf=D:\EclUtil\sonarqube-8.1.0.31237\sonarqube-8.1.0.31237\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2020.01.31 10:43:14 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2020.01.31 10:43:15 INFO app[][o.e.p.PluginsService] no modules loaded
2020.01.31 10:43:15 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2020-01-31 10:43:16,944 main ERROR Unable to locate plugin type for IfFileName
2020-01-31 10:43:16,991 main ERROR Unable to locate plugin for IfAccumulatedFileCount
2020-01-31 10:43:16,991 main ERROR Unable to locate plugin for IfFileName
2020-01-31 10:43:16,991 main ERROR Unable to invoke factory method in class

SonarQube Unable to Start localhost

I'm having some trouble to start the sonar in Ubuntu box, even i could not trace the sonar log with more information.
sonar.logs
root#jenkins-linux-vm:/opt/sonar/logs# cat sonar.log
--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2019.12.24 13:16:23 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonar/temp
2019.12.24 13:16:23 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.12.24 13:16:23 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonar/elasticsearch]: /opt/sonar/elasticsearch/bin/elasticsearch
2019.12.24 13:16:23 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2019.12.24 13:16:24 INFO app[][o.e.p.PluginsService] no modules loaded
2019.12.24 13:16:24 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.12.24 13:16:29 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 1
2019.12.24 13:16:29 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped
2019.12.24 13:16:29 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped
java version
'''
java -version
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment (build 11.0.5+10-post-Ubuntu-0ubuntu1.118.04)
OpenJDK 64-Bit Server VM (build 11.0.5+10-post-Ubuntu-0ubuntu1.118.04, mixed mode, sharing)
'''
can you please some one help me on this.

How to fix Out Of Memory issue on sonarqube server 6.7.2.37468

When Sonarqube server version 6.7.2 is running on AWS EC2 instance, once by month approximatively, there is an out of memory error and the server is shutdown, we need to restart it manually, there is a memory leak or bad setup configuration on OS/JRE level or Application server level.
At the beginning, the sonarqube server goes down twice a month due to Out Of Memory issue, we follow the official setup doc for PRD instance and try to scale vertically the capacity from a t2.small to a t2.medium on the EC2 instance and run the 3 java processes with more memory:
For Web:
sonar.web.javaOpts=-Xms256m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError
For ElasticSearch:
sonar.search.javaOpts=-Xms1024m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError
For Compute Engine:
sonar.ce.javaOpts=-Xms256m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError
But the issue is still present
--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2019.04.29 06:59:38 INFO app[][o.s.a.AppFileSystem] Cleaning or creating
temp directory /opt/sonarqube-6.7.2/temp
2019.04.29 06:59:38 INFO app[][o.s.a.es.EsSettings] Elasticsearch
listening on /127.0.0.1:9001
2019.04.29 06:59:38 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch
process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube-6.7.2/elasticsearch]: /opt/sonarqube- 6.7.2/elasticsearch/bin/elasticsearch -Epath.conf=/opt/sonarqube- 6.7.2/temp/conf/es
2019.04.29 06:59:38 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2019.04.29 06:59:39 INFO app[][o.e.p.PluginsService] no modules loaded
2019.04.29 06:59:39 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.04.29 07:00:00 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2019.04.29 07:00:00 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube- 6.7.2]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12- 1.el7_6.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 - Djava.io.tmpdir=/opt/sonarqube-6.7.2/temp -Xmx1024m -Xms256m - XX:+HeapDumpOnOutOfMemoryError -Dhttp.proxyHost= -Dhttp.proxyPort= - Dhttp.auth.ntlm.domain= -DsocksProxyHost= -DsocksProxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort= -cp ./lib/common/*:./lib/server/*:/opt/sonarqube- 6.7.2/lib/jdbc/postgresql/postgresql-42.2.1.jar org.sonar.server.app.WebServer /opt/sonarqube-6.7.2/temp/sq-process5028201971842772853properties
2019.04.29 07:00:25 INFO app[][o.s.a.SchedulerImpl] Process[web] is up
2019.04.29 07:00:25 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='ce', ipcIndex=3, logFilenamePrefix=ce]] from [/opt/sonarqube- 6.7.2]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12- 1.el7_6.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 - Djava.io.tmpdir=/opt/sonarqube-6.7.2/temp -Xms256m -Xmx1024m - XX:+HeapDumpOnOutOfMemoryError -Dhttp.proxyHost= -Dhttp.proxyPort= - Dhttp.auth.ntlm.domain= -DsocksProxyHost= -DsocksProxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort= -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/opt/sonarqube- 6.7.2/lib/jdbc/postgresql/postgresql-42.2.1.jar org.sonar.ce.app.CeServer /opt/sonarqube-6.7.2/temp/sq-process7912202285523412339properties
2019.04.29 07:00:30 INFO app[][o.s.a.SchedulerImpl] Process[ce] is up
2019.04.29 07:00:30 INFO app[][o.s.a.SchedulerImpl] SonarQube is up
2019.04.29 15:10:28 INFO app[][o.s.a.SchedulerImpl] Process [ce] is stopped
2019.04.29 15:10:31 INFO app[][o.s.a.SchedulerImpl] Process [web] is stopped
2019.04.29 15:10:31 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143
2019.04.29 15:10:31 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
2019.04.29 15:10:31 INFO app[][o.s.a.SchedulerImpl] SonarQube is restarting
2019.04.29 15:10:31 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143
2019.04.29 15:10:31 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-6.7.2/temp
2019.04.29 15:10:31 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.04.29 15:10:31 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube- 6.7.2/elasticsearch]: /opt/sonarqube-6.7.2/elasticsearch/bin/elasticsearch - Epath.conf=/opt/sonarqube-6.7.2/temp/conf/es
2019.04.29 15:10:31 INFO app[][o.e.p.PluginsService] no modules loaded
2019.04.29 15:10:31 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.04.29 15:10:51 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2019.04.29 15:10:51 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube- 6.7.2]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12- 1.el7_6.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 - Djava.io.tmpdir=/opt/sonarqube-6.7.2/temp -Xmx1024m -Xms256m - XX:+HeapDumpOnOutOfMemoryError -Dhttp.proxyHost= -Dhttp.proxyPort= - Dhttp.auth.ntlm.domain= -DsocksProxyHost= -DsocksProxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort= -cp ./lib/common/*:./lib/server/*:/opt/sonarqube- 6.7.2/lib/jdbc/postgresql/postgresql-42.2.1.jar org.sonar.server.app.WebServer /opt/sonarqube-6.7.2/temp/sq-process2158511348006070798properties
2019.04.29 15:11:12 INFO app[][o.s.a.SchedulerImpl] Process[web] is up
2019.04.29 15:11:12 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='ce', ipcIndex=3, logFilenamePrefix=ce]] from [/opt/sonarqube- 6.7.2]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12- 1.el7_6.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 - Djava.io.tmpdir=/opt/sonarqube-6.7.2/temp -Xms256m -Xmx1024m - XX:+HeapDumpOnOutOfMemoryError -Dhttp.proxyHost= -Dhttp.proxyPort= - Dhttp.auth.ntlm.domain= -DsocksProxyHost= -DsocksProxyPort= -Dhttps.proxyHost= -Dhttps.proxyPort= -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/opt/sonarqube- 6.7.2/lib/jdbc/postgresql/postgresql-42.2.1.jar org.sonar.ce.app.CeServer /opt/sonarqube-6.7.2/temp/sq-process1917579452884722345properties
2019.04.29 15:11:17 INFO app[][o.s.a.SchedulerImpl] Process[ce] is up
2019.04.29 15:11:17 INFO app[][o.s.a.SchedulerImpl] SonarQube is up
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000dbc80000, 43515904, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 43515904 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /opt/sonarqube-6.7.2/hs_err_pid10967.log
2019.05.14 09:56:08 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [ce]: 1
2019.05.14 09:56:08 INFO app[][o.s.a.SchedulerImpl] Process [ce] is stopped
2019.05.14 09:56:11 INFO app[][o.s.a.SchedulerImpl] Process [web] is stopped
2019.05.14 09:56:11 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
2019.05.14 09:56:11 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143
2019.05.14 09:56:11 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped
We expect a Sonarqube server up and running without insufficient memory for the JRE to continue. If you need the dump of JVM in /opt/sonarqube-6.7.2/hs_err_pid10967.log, I can also provide it if this can help to debug the memory issue.
Thanks for your help and support.
It looks like the memory allocated for Compute Engine is not sufficient.
In order to fix it, you'll need to upgrade to at least a t2.large and increase the size allocated for Compute Engine to 2 or 4Gb of memory.

SonarQube isn't starting and no error seems to show up in the console output. Could someone help me figure what's wrong?

I'm trying to start SonarQube on a Windows 10 box. I've installed Postgres 10. When I run StartSonar.bat, I get the following:
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2019.02.07 06:22:23 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\temp
jvm 1 | 2019.02.07 06:22:23 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1 | 2019.02.07 06:22:23 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\elasticsearch]: C:\Program Files\Java\jre1.8.0_201\bin\java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -Xms512m -Xmx512m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\elasticsearch -cp lib/* org.elasticsearch.bootstrap.Elasticsearch -Epath.conf=C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\temp\conf\es
jvm 1 | 2019.02.07 06:22:23 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1 | 2019.02.07 06:22:23 INFO app[][o.e.p.PluginsService] no modules loaded
jvm 1 | 2019.02.07 06:22:23 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1 | 2019.02.07 06:22:34 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
jvm 1 | 2019.02.07 06:22:34 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5]: C:\Program Files\Java\jre1.8.0_201\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*;C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\lib\jdbc\postgresql\postgresql-42.2.5.jar org.sonar.server.app.WebServer C:\Users\Administrator\Downloads\sonarqube-7.5\sonarqube-7.5\temp\sq-process8601102404220274862properties
jvm 1 | 2019.02.07 06:22:36 INFO app[][o.s.a.SchedulerImpl] Process [web] is stopped
jvm 1 | 2019.02.07 06:22:36 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
jvm 1 | 2019.02.07 06:22:36 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
wrapper | <-- Wrapper Stopped
The following are the changes I've made to the sonar.properties file:
sonar.jdbc.url=jdbc:postgresql://localhost/sonarqube
# By default, ports will be used on all IP addresses associated with the server.
sonar.web.host=192.0.0.1
# TCP port for incoming HTTP connections. Default value is 9000.
sonar.web.port=9000
# Defaults are respectively <installation home>/data and <installation home>/temp
sonar.path.data=data
sonar.path.temp=temp
The following are screenshots from pgAdmin:
So there were two issues.
The first was due to the sonar.web.host property. I had set it to 192.0.0.1 and after I changed it to 127.0.0.1, this issue was resolved.
The second issue was due to the port the database server was using. After I changed it to the default (i.e. 5432), it worked.

Sonarqube 5.2 starts, but not accessible

Sonarqube 5.2 starts without errors, but is not accessible. It was working fine until a couple of days ago.
1. Sonar is configured to run on Port 9000, but the port is free.
2. Firefox cannot access the url.
This is the sonar.log entry:
*--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2018.04.11 22:44:47 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[search]: /usr/java/jre1.8.0_161/bin/java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djava.net.preferIPv4Stack=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/scratch/aime/Sonar/sonarqube-5.2/temp -cp ./lib/common/*:*./lib/search/* *org.sonar.search.SearchServer /tmp/sq-process3042361883049663302properties
2018.04.11 22:44:47 INFO es[o.s.p.ProcessEntryPoint] Starting search
2018.04.11 22:44:47 INFO es[o.s.s.SearchSettings] Elasticsearch listening on 127.0.0.1:9001
2018.04.11 22:44:48 INFO es[o.elasticsearch.node] [sonar-1523511887257] version[1.7.2], pid[1648], build[e43676b/2015-09-14T09:49:53Z]
2018.04.11 22:44:48 INFO es[o.elasticsearch.node] [sonar-1523511887257] initializing ...
2018.04.11 22:44:48 INFO es[o.e.plugins] [sonar-1523511887257] loaded [], sites []*
There has been no change in the sonar.properties and sonar was fine until a few days ago.
What is going wrong?

Resources