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.
Related
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
I am getting below error while starting sonarqube
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2020.01.03 10:31:26 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory
/sonarqube/sonarqube-7.9.1/temp
2020.01.03 10:31:26 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2020.01.03 10:31:26 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1,
logFilenamePrefix=es]] from [/sonarqube/sonarqube
-7.9.1/elasticsearch]: /sonarqube/sonarqube-7.9.1/elasticsearch/bin/elasticsearch
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on2020.01.03 10:31:26 INFO app[]
Waiting for Elasticsearch to be up and running
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will l
likely be removed in a future release.
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2020.01.03 10:31:26 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]:
2020.01.03 10:31:26 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped
2020.01.03 10:31:26 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
FATAL StatusLogger Interrupted before Log4j Providers could be loaded.
java.lang.InterruptedExceptionjava.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1261)
at java.base/java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:317)
at org.apache.logging.log4j.util.ProviderUtil.lazyInit(ProviderUtil.java:121)
at org.apache.logging.log4j.util.ProviderUtil.hasProviders(ProviderUtil.java:108)
at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:89)
at org.elasticsearch.common.unit.ByteSizeValue.<clinit>(ByteSizeValue.java:39)
at org.elasticsearch.common.network.NetworkService.<clinit>(NetworkService.java:57)
at org.elasticsearch.transport.TransportSettings.<clinit>(TransportSettings.java:74)
at org.elasticsearch.client.transport.TransportClient.newPluginService(TransportClient.java:105)
at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:135)
at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:277)
at org.sonar.application.es.EsConnectorImpl$MinimalTransportClient.<init>
(EsConnectorImpl.java:103)
at org.sonar.application.es.EsConnectorImpl.buildTransportClient(EsConnectorImpl.java:89)
at org.sonar.application.es.EsConnectorImpl.getTransportClient(EsConnectorImpl.java:74)
at org.sonar.application.es.EsConnectorImpl.getClusterHealthStatus(EsConnectorImpl.java:61)
at org.sonar.application.process.EsManagedProcess.checkStatus(EsManagedProcess.java:88)
at org.sonar.application.process.EsManagedProcess.checkOperational(EsManagedProcess.java:73)
at org.sonar.application.process.EsManagedProcess.isOperational(EsManagedProcess.java:58)
org.sonar.application.process.ManagedProcessHandler.refreshState(ManagedProcessHandler.java:201)
org.sonar.application.process.ManagedProcessHandler$EventWatcher.run(ManagedProcessHandler.java:258)
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the
classpath. Using SimpleLogger to log to the consol
e...
<-- Wrapper Stopped
Java -version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
openjdk version "11.0.5" 2019-10-15 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing)
Need help to resolve this issue
The error that's causing Sonarqube to exit is Unrecognized VM option 'UseParNewGC'. This indicates you have a JAVA_OPTIONS (or command-line parameter) - set to +XX:UseParNewGC. As UseParNewGC was dropped in Java 10, this option can be safely removed.
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.
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.
I had downloaded latest sonarqube 7.1. And trying to start using command:
./bin/macosx-universal-64/sonar.sh console
But, It's not get started. Logs are:
Running SonarQube...
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 | 2018.04.26 14:57:34 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /Users/deepakagrawal/softwares/sonarqube-7.1/temp
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/Users/deepakagrawal/softwares/sonarqube-7.1/elasticsearch]: /Users/deepakagrawal/softwares/sonarqube-7.1/elasticsearch/bin/elasticsearch -Epath.conf=/Users/deepakagrawal/softwares/sonarqube-7.1/temp/conf/es
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.e.p.PluginsService] no modules loaded
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1 | Error: Could not find or load main class -XX:+UseConcMarkSweepGC
jvm 1 | 2018.04.26 14:57:34 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
jvm 1 | 2018.04.26 14:57:34 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
wrapper | <-- Wrapper Stopped
I tried other versions like 7.0. But it's still not working.
I had installed Oracle Java 8.
java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
root user will not work
Looks like elastic search is failing to start. Do not attempt to run sonar as a root. Elastic is designed to prevent you from doing running as root.
$ tail logs/es.log
Caused by: java.lang.RuntimeException: can not run elasticsearch as root
at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:103) ~[elasticsearch-6.8.4.jar:6.8.4]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:170) ~[elasticsearch-6.8.4.jar:6.8.4]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-6.8.4.jar:6.8.4]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-6.8.4.jar:6.8.4]
... 6 more
If you are running as root:
Prepare system user.
Open sonar.sh find RUN_AS_USER and assign your system user.
Notes
If you were using root to avoid file permission issues and just quickly want to get something running, you can do this instead:
sudo chown $(whoami) temp logs -Rv
After a macOS update to 10.14.5 I got a similar log. I found out that write permissions were removed from /opt/sonarqube/temp/, which are needed by elastic search (ls -l /opt/sonarqube/temp/). After re-adding write permissions using chmod, sonarqube started successfully again.