Upgraded SonarQube 7.4 failing to run

SonarQube Server / Community Build
1

When trying to upgrade our SonarQube Community Ed. from 6.5 to 7.4, after updating sonar.properties with the following, StartSonar.bat stops. Can someone tell me why? I’m using SQL server 2016 and SQL authentication.
sonar.jdbc.username=SonarUser
sonar.jdbc.password=
sonar.web.port=9090
sonar.jdbc.url=jdbc:sqlserver://psql99v:40018;instance=confprod1;databaseName=sonar;SelectMethod=Cursor

Using default embedded H2 database works fine so my SQL database configuration is not working.

Here’s the SQ log. Thanks in advanced.

–> 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.

2018.12.17 11:17:14 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\SonarQube\sonarqube-7.4\temp
2018.12.17 11:17:14 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2018.12.17 11:17:14 INFO app[o.s.a.p.ProcessLauncherImpl] Launch process[[key=‘es’, ipcIndex=1, logFilenamePrefix=es]] from [C:\SonarQube\sonarqube-7.4\elasticsearch]: C:\Program Files\Java\jre1.8.0_60\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:\SonarQube\sonarqube-7.4\elasticsearch -cp lib/* org.elasticsearch.bootstrap.Elasticsearch -Epath.conf=C:\SonarQube\sonarqube-7.4\temp\conf\es
2018.12.17 11:17:14 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2018.12.17 11:17:14 INFO app[o.e.p.PluginsService] no modules loaded
2018.12.17 11:17:14 INFO app[o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2018.12.17 11:17:23 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2018.12.17 11:17:23 INFO app[o.s.a.p.ProcessLauncherImpl] Launch process[[key=‘web’, ipcIndex=2, logFilenamePrefix=web]] from [C:\SonarQube\sonarqube-7.4]: C:\Program Files\Java\jre1.8.0_60\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\SonarQube\sonarqube-7.4\temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*;C:\SonarQube\sonarqube-7.4\lib\jdbc\mssql\mssql-jdbc-6.2.2.jre8.jar org.sonar.server.app.WebServer C:\SonarQube\sonarqube-7.4\temp\sq-process6864984652220716941properties
2018.12.17 11:17:42 INFO app[o.s.a.SchedulerImpl] Process [web] is stopped
2018.12.17 11:17:42 INFO app[o.s.a.SchedulerImpl] Process [es] is stopped
2018.12.17 11:17:42 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped

2

You should have multiple log files – web.log, es.log, ce.log, sonar.log. I’d check in all 4 and see if anything looks interesting.

1 Like
3

Thanks Colin. I found following error message. Thus, I guess I need to upgrade to LTS 6.7.6, then upgrade to 7.4.
ERROR web[o.s.s.p.Platform] Web server startup failed: Current version is too old. Please upgrade to Long Term Support version firstly.

4

:tada: glad you found the problem.