SQ service starting then stopping

SonarQube
1

Hi all,

Nothing notable in the Java logs or Windows application logs. Everything was working fine the other day and everyone has denied all knowledge of touching it :slight_smile:

Any suggestions towards diagnosis please?

Carl.

2

Hi Carl,

Can you check the application logs: https://docs.sonarqube.org/display/SONAR/Troubleshooting ?

 
Ann

3

Hi Ann,

Thanks for the info, we’d already found that folder. The only logfile we have is sonar.log. Here is the contents of it. Looks like it could be Java related. We have 10.0.1 installed.

Cheers,
Carl.

–> Wrapper Started as Service
Using tick timer.
server listening on port 32000.
Launching a JVM…
command: “C:\Program Files\Java\jre-10.0.1\bin\java” -Djava.awt.headless=true -Xms3m -Xmx3m -Djava.library.path="./lib" -classpath “…/…/lib/jsw/wrapper-3.2.3.jar;…/…/lib/sonar-application-5.6.4.jar” -Dwrapper.key=“pSPGnWs6rlcQ8yS_” -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug=“TRUE” -Dwrapper.pid=892 -Dwrapper.version=“3.2.3” -Dwrapper.native_library=“wrapper” -Dwrapper.service=“TRUE” -Dwrapper.cpu.timeout=“10” -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.sonar.application.App
JVM started (PID=2444)
WrapperManager class initialized by thread: main Using classloader: jdk.internal.loader.ClassLoaders$AppClassLoader@531be3c5
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.

Wrapper Manager: JVM #1
Running a 64-bit JVM.
Wrapper Manager: Registering shutdown hook
Wrapper Manager: Using wrapper
Load native library. One or more attempts may fail if platform specific libraries do not exist.
Loading native library failed: wrapper-windows-x86-64.dll Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-64 in java.library.path: [./lib]
Loaded native library: wrapper.dll
Calling native initialization method.
Initializing WrapperManager native library.
Java Executable: C:\Program Files\Java\jre-10.0.1\bin\java.exe
Windows version: 6.3.9600
Java Version : 10.0.1+10 Java HotSpot™ 64-Bit Server VM
Java VM Vendor : “Oracle Corporation”

Control event monitor thread started.
Startup runner thread started.
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@343f4d3d, args[]) called by thread: main
Communications runner thread started.
Open socket to wrapper…Wrapper-Connection
Failed attempt to bind using local port 31000
Opened Socket from 31001 to 32000
Send a packet KEY : pSPGnWs6rlcQ8yS_
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001])
accepted a socket from 127.0.0.1 on port 31001
read a packet KEY : pSPGnWs6rlcQ8yS_
Got key from JVM: pSPGnWs6rlcQ8yS_
send a packet LOW_LOG_LEVEL : 1
send a packet PING_TIMEOUT : 0
send a packet PROPERTIES : (Property Values)
Start Application.
send a packet START : start
Received a packet LOW_LOG_LEVEL : 1
Wrapper Manager: LowLogLevel from Wrapper is 1
Received a packet PING_TIMEOUT : 0
PingTimeout from Wrapper is 0
Received a packet PROPERTIES : (Property Values)
Received a packet START : start
calling WrapperListener.start()
Waiting for WrapperListener.start runner thread to complete.
WrapperListener.start runner thread started.
WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete.
WrapperSimpleApp: invoking main method
2018.10.08 14:43:04 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sq\sonarqube-5.6.4\temp
Unrecognized VM option ‘UseParNewGC’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2018.10.08 14:43:04 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[es]: C:\Program Files\Java\jre-10.0.1\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=C:\sq\sonarqube-5.6.4\temp -javaagent:C:\Program Files\Java\jre-10.0.1\lib\management-agent.jar -cp ./lib/common/;./lib/search/ org.sonar.search.SearchServer C:\sq\sonarqube-5.6.4\temp\sq-process2105072139827502253properties
Wrapper Manager: ShutdownHook started
WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
Send a packet STOP : 0
Startup runner thread stopped.
read a packet STOP : 0
JVM requested a shutdown. (0)
wrapperStopProcess(0) called.
Sending stop signal to JVM
send a packet STOP : NULL
Send a packet START_PENDING : 5000
read a packet START_PENDING : 5000
JVM signalled a start pending with waitHint of 5000 millis.
Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
shutdownJVM(0) Thread:Wrapper-Shutdown-Hook
Send a packet STOPPED : 0
read a packet STOPPED : 0
JVM signalled that it was stopped.
Send a packet START_PENDING : 5000
WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null
WrapperListener.start runner thread stopped.
returned from WrapperListener.start()
Send a packet STARTED :
Received a packet STOP :
Closing socket.
read a packet START_PENDING : 5000
JVM signalled a start pending with waitHint of 5000 millis.
read a packet STARTED :
JVM signalled that it was started.
socket read no code (closed?).
server listening on port 32001.
Wrapper Manager: ShutdownHook complete
Server daemon shut down
JVM process exited with a code of 0, leaving the wrapper exit code set to 0.
JVM exited normally.
<-- Wrapper Stopped

4

Hi,

That would be your problem: https://docs.sonarqube.org/display/SONAR/Requirements#Requirements-SupportedPlatforms

 
Ann

5

Hi Ann,

But this is the version we have had installed since it was setup and working fine for over a month?

Cheers,
Carl.

6

Hi Carl,

If you’ve had this set up and working for over a month, then you have more logs than just sonar.log. Something must have changed on your side.

 
Ann

7

Hi Ann,

Sonar.log was honestly the only log present. Could it be the case that we need to enable these extra logs? We are running the community edition as a PoC at the moment, don’t know if that affects the logging level?

Carl.

8

Hi,

A very long time ago there was only one log…

And I realize now you haven’t stated your verson…

And I find in your initial log

So it seems that you’re running a very old version and might normally and legitimately have only one log file. (Sorry for busting your chops.)

That said,

  • this version (released Dec. 2016) will for sure not run on Java 10 (released March 2018).
  • this version is nearly 2 years old. The current version is 7.3 and the current LTS is 6.7.5. You’re going to have a hard time finding (competent) support for any older versions

I’m going to guess what changed is that Java was upgraded on your server. Perhaps you should consider an upgrade of the application it supports as well.

 
:slight_smile:
Ann

9

Hi Ann,

I’ll perform an in-line upgrade on it and report back. Doesn’t explain how it was working fine up until the other day though :slight_smile:
Cheers,
Carl.

10

Hi Ann,

After upgrading everything, it’s all back up and running :sunglasses:

Cheers,
Carl.

1 Like