Sonarqube upgrade issues from 7.3 to 7.9 LTS

SonarQube
1

Hi,

We have tried to upgrade Sonarqube server from 7.3 to 9.9 LTS version. And it gave me below error and upgrade failed.

As a pre-requisite we have upgrade the Java version to 11. Initially it was Java 8. Please help us with this error and make the upgrade successful.

2019.07.08 14:32:34 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/apps/sonar/sonarqube-7.9/elasticsearch]: /apps/sonar/sonarqube-7.9/elasticsearch/bin/elasticsearch
2019.07.08 14:32:34 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.
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2019.07.08 14:32:34 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 1
2019.07.08 14:32:34 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
2019.07.08 14:32:34 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
FATAL StatusLogger Interrupted before Log4j Providers could be loaded.
 java.lang.InterruptedException
        at java.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)
        at org.sonar.application.process.ManagedProcessHandler.refreshState(ManagedProcessHandler.java:201)
        at 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 console...
<-- Wrapper Stopped

Thanks,
Srikanth

2

Hi,

How are you starting SonarQube? I don’t think the startup scripts that are bundled use the JVM option UseParNewGC.

3

Hi Durate,

Thanks for the quick response.

I am using ./sonar.sh start to start the server.

Thanks,
Srikanth

4

I searched our scripts and the options used to launch the 3 processes and can’t find UseParNewGC.

Could it be that you defined additional java options? For example, do you have sonar.web.javaOpts, sonar.ce.javaOpts or sonar.search.javaOpts defined in conf/sonar.properties?

5

Hello Team,
We are also facing the same issue.
I think this is coming from ElasticSearch JVM initialisation, but I could not find UseParNewGC Options in Elasticsearch/config/jvm.options

Any Help?

6

Hi Amit,
Could you tell us the exact versions of OS, JRE and SonarQube?

As I mentioned in my previous post, do you have any sonar.{web/ce/search}.javaOpts configured in [sonarqube_home]/conf/sonar.properties?

7

Also, for each process started in SonarQube, the command launching the jvm is printed in [sonarqube_home]/logs/sonar.log. Example:

2019.07.18 12:44:57 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [sonarqube-7.9.1]: C:\Program Files\Java\jdk-11.0.3\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=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 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*;sonarqube-7.9.1\lib\jdbc\postgresql\postgresql-42.2.5.jar org.sonar.server.app.WebServer sonarqube-7.9.1\temp\sq-process16273308365715655286properties

Could you please post the commands for all 3 processes (ce, web and es)?
Thanks.