I have problem with SonarQube-5.6.6 Server Service Startup
Our Environment details as follows:
SonarQube Server Version - 5.6.6 (64-Bit)
Operating System – Ubuntu - 14.04.5 LTS (64-Bit)
mysql Ver 14.14 Distrib 5.6.33, for debian-linux-gnu (x86_64) using EditLine wrapper
Problem Description:
I have copied the dumped mysql file from another sonarqube-5.1 version server and I have successfully restored in my current sonarqube-5.6.6 server.
Later when I tried to start the SonarQube service, It shows below details,
2017.05.23 14:46:36 INFO app[o.s.p.m.Monitor] Process[web] is up
2017.05.23 14:46:36 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[ce]: /usr/lib/jvm/jdk1.8.0_131/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/opt/sonarqube-5.6.6/temp -javaagent:/usr/lib/jvm/jdk1.8.0_131/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/opt/sonarqube-5.6.6/lib/jdbc/mysql/mysql-connector-java-5.1.35.jar org.sonar.ce.app.CeServer /opt/sonarqube-5.6.6/temp/sq-process2919432455637110534properties
2017.05.23 14:46:37 INFO ce[o.s.p.ProcessEntryPoint] Starting ce
2017.05.23 14:46:37 INFO ce[o.s.c.a.WebServerWatcherImpl] Waiting for Web Server to be operational...
2017.05.23 14:46:38 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2017.05.23 14:46:40 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2017.05.23 14:46:45 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2017.05.23 14:46:58 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2017.05.23 14:47:32 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2017.05.23 14:49:06 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2017.05.23 14:53:21 INFO ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
So could you help me to resolve the same.
Related
I have set up Quorom 3 nodes by following the guide and now I am setting of the Tessera nodes for the 3 nodes. however the Tessera node are not starting up.
https://docs.goquorum.com/en/latest/Getting%20Started/Creating-A-Network-From-Scratch/#tessera
Here are logs captured.
2019-11-09 00:57:30.942 [main] INFO org.eclipse.jetty.util.log - Logging initialized #7972ms to org.eclipse.jetty.util.log.Slf4jLog
2019-11-09 00:57:31.069 [main] INFO c.quorum.tessera.server.JerseyServer - Starting http://localhost:9081
2019-11-09 00:57:31.075 [main] INFO org.eclipse.jetty.server.Server - jetty-9.4.z-SNAPSHOT; built: 2019-04-18T19:45:35.259Z; git: aa1c656c315c011c01e7b21aabb04066635b9f67; jvm 1.8.0_231-b11
2019-11-09 00:57:32.051 [main] WARN o.g.jersey.internal.inject.Providers - A provider com.quorum.tessera.thirdparty.RawTransactionResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.quorum.tessera.thirdparty.RawTransactionResource will be ignored.
2019-11-09 00:57:32.519 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#37c5284a{/,null,AVAILABLE}
Failed to bind to 0.0.0.0/0.0.0.0:9081
2019-11-09 00:57:32.540 [Thread-2] INFO c.quorum.tessera.server.JerseyServer - Stopping Jersey server at http://localhost:9081
2019-11-09 00:57:32.555 [Thread-2] INFO o.e.jetty.server.AbstractConnector - Stopped ServerConnector#41853299{HTTP/1.1,[http/1.1]}{0.0.0.0:9081}
2019-11-09 00:57:32.782 [Thread-2] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler#37c5284a{/,null,UNAVAILABLE}
2019-11-09 00:57:32.787 [Thread-2] INFO c.quorum.tessera.server.JerseyServer - Stopped Jersey server at http://localhost:9081
2019-11-09 00:57:32.787 [Thread-2] INFO c.quorum.tessera.server.JerseyServer - Stopping Jersey server at unix:/home/srikant/Desktop/fromscratch/new-node-1t/tm.ipc
2019-11-09 00:57:32.787 [Thread-2] INFO c.quorum.tessera.server.JerseyServer - Stopped Jersey server at unix:/home/srikant/Desktop/fromscratch/new-node-1t/tm.ipc
2019-11-09 00:57:32.788 [Thread-2] INFO c.quorum.tessera.server.JerseyServer - Stopping Jersey server at http://localhost:9001
2019-11-09 00:57:32.788 [Thread-2] INFO c.quorum.tessera.server.JerseyServer - Stopped Jersey server at http://localhost:9001
Any help would be really appreciable.
The 'Failed to bind' message implies that the port is in use.
Perhaps Tessera is already running?
You can use lsof -nP -i4TCP:9081 to check which process is using port 9081.
I came across the same issue. I restarted the VM and then it worked
After building the app, the deployment process works. The SpringBoot (mysql) application is deployed and marked as the usual "Starting the application".
After a few seconds, there is a message saying it "kills" the application. Notice, I am just within the limits of my Openshift free quota.
What is the mesage? .../wildfly/bin/standalone.sh: line 307: 183 Killed "java" -D"[Standalone]"
See the line in bold.
On another time I see is that the application is started, I can even login, but then after a minute is is killed.
14:47:15,334 INFO [nl.xyz.Application] (ServerService Thread Pool --
66) Started Application in 26.49 seconds (JVM running for 57.227)
14:47:15,723 INFO [javax.enterprise.resource.webcontainer.jsf.config]
(ServerService Thread Pool -- 66) Initializing Mojarra 2.2.13.SP1
20160303-1204 for context '' /wildfly/bin/standalone.sh: line 307: 183
Killed "java" -D"[Standalone]" -server -XX:+UseParallelGC -Xms40m
-Xmx250m -XX:+AggressiveOpts -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dorg.apache.tomcat.util.LOW_MEMORY=true -DOPENSHIFT_APP_UUID= -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djboss.node.name=solvedcaches-5-80fj7 -Djgroups.bind_addr=0.0.0.0 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on "-Dorg.jboss.boot.log.file=/wildfly/standalone/log/server.log"
"-Dlogging.configuration=file:/wildfly/standalone/configuration/logging.properties"
-jar "/wildfly/jboss-modules.jar" -mp "/wildfly/provided_modules:/wildfly/modules" org.jboss.as.standalone
-Djboss.home.dir="/wildfly" -Djboss.server.base.dir="/wildfly/standalone" '-b' '0.0.0.0' '-bmanagement' '0.0.0.0'
The last 2 build failed due to a generic build failture. Strange, the code was hardly changed. It looks like rebuilding takes memory and is competing with the running application and vice versa. The last time I stopped the POD, then deployment was ok.
Thank you #Jiri Fialka for all your help, online / offline.
As you suggested, after configuring the memory over the 2 POD's the application is working fine. Now I use 410 Mb for Mysql and 600 Mb for SpringBoot was WAR on a Wildfly pod. Even SSH was added within minutes!.
I am enthusiastic about the new Openshift v3 facilities. Also the GUI and oc.
I'm on a macos box, trying to get openshift to start.
minishift v1.3.1+a2d3799
CDK v3.1.0-1
minishift start --vm-driver xhyve
or
minishift start --vm-driver virtualbox
always results in this error:
Starting local OpenShift cluster using 'xhyve' hypervisor... E0831
12:08:02.405025 25814 start.go:282] Error starting the VM: Error
attempting to get plugin server address for RPC: Failed to dial the
plugin server in 10s. Retrying.
Both virtualbox and xhyve are installed.
Upgrading minishift to release 1.5 fixed the issue.
I installed sonarqube-6.3.1 in my machine and created a database in mysql db named 'sonarqubedb'. Now when I am making changes in sonar.properties file to use the database, sonarqube is not getting started and throwing error msg, but If I am using the default DB configuration (and NOT mysql), I am able to start.
Could somebody please provide me a solution what is going wrong when I am using mysql db.
My sonar.properties file be like:
sonar.jdbc.username=root
sonar.jdbc.password=
sonar.jdbc.url=jdbc:mysql://localhost:3306/sonarqubedb?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance
and the sonar log file when I try to start service, be like:
--> Wrapper Started as Service
Launching a JVM...
WrapperManager class initialized by thread: main Using classloader:
sun.misc.Launcher$AppClassLoader#4e25154f
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
Loaded native library: wrapper.dll
Calling native initialization method.
Initializing WrapperManager native library.
Java Executable: C:\ProgramData\Oracle\Java\javapath\java.exe
Windows version: 6.1.7600
Java Version : 1.8.0_45-b15 Java HotSpot(TM) 64-Bit Server VM
Java VM Vendor : Oracle Corporation
Control event monitor thread started.
Startup runner thread started.
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp#4f023edb, 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 : 4hhDEyNqmPXAiWpf
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001])
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
2017.04.26 14:54:12 INFO app[][o.s.a.AppFileSystem] Cleaning or creating
temp directory C:\Program Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp
2017.04.26 14:54:12 INFO app[][o.s.p.m.JavaProcessLauncher] Launch
process[es]: C:\Program Files\Java\jre1.8.0_45\bin\java -
Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true -
XX:+UseParNewGC -XX:+UseConcMarkSweepGC -
XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -
XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Program
Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp -javaagent:C:\Program
Files\Java\jre1.8.0_45\lib\management-agent.jar -cp
./lib/common/*;./lib/search/* org.sonar.search.SearchServer C:\Program
Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp\sq-
process3041279828124660880properties
Send a packet START_PENDING : 5000
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 :
Startup runner thread stopped.
Received a packet PING : ping
Send a packet PING : ok
Received a packet PING : ping
Send a packet PING : ok
2017.04.26 14:54:23 INFO app[][o.s.p.m.Monitor] Process[es] is up
2017.04.26 14:54:23 INFO app[][o.s.p.m.JavaProcessLauncher] Launch
process[web]: C:\Program Files\Java\jre1.8.0_45\bin\java -
Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -
XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Program
Files\Sonar\sonarqube-6.3.1\sonarqube-6.3.1\temp -javaagent:C:\Program
Files\Java\jre1.8.0_45\lib\management-agent.jar -cp
./lib/common/*;./lib/server/*;C:\Program Files\Sonar\sonarqube-
6.3.1\sonarqube-6.3.1\lib\jdbc\mysql\mysql-connector-java-5.1.39.jar
org.sonar.server.app.WebServer C:\Program Files\Sonar\sonarqube-
6.3.1\sonarqube-6.3.1\temp\sq-process5745752416531116392properties
Received a packet PING : ping
Send a packet PING : ok
2017.04.26 14:54:28 INFO app[][o.s.p.m.Monitor] Process[es] is stopping
2017.04.26 14:54:28 ERROR app[][o.s.p.m.Monitor] Process[web] failed to
start
2017.04.26 14:54:28 INFO app[][o.s.p.m.Monitor] Process[es] is stopped
Wrapper Manager: ShutdownHook started
WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
Send a packet STOP : 0
Received a packet STOP :
Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
calling listener.stop()
WrapperSimpleApp: stop(0)
returned from listener.stop() -> 0
shutdownJVM(0) Thread:Wrapper-Shutdown-Hook
Send a packet STOPPED : 0
Closing socket.
Server daemon shut down
Wrapper Manager: ShutdownHook complete
<-- Wrapper Stopped
Thanks in Advance :)
Go to your sonarqube/logs directory. You'll find several log files and one of them will contain the detailed error on why sonarqube won't start.(you'll have to scroll all the way down inside the files for the latest information iirc)
Go through this sonar documentation, you will get some help -
https://docs.sonarqube.org/display/SONAR/Installing+the+Server
I had the same issue.
The problem was that my MySQL version didn't meet the minimum requirements.
If I don't connect the MySql database to Sonar, the web UI can load no problem on localhost:9000. If I update the configuration file for MySQL, the web won't start, but I can't see a hint from the log.
sonar.properties:
# User credentials.
# Permissions to create tables, indices and triggers must be granted to JDBC user.
# The schema must be created first.
sonar.jdbc.username=sonarqube
sonar.jdbc.password=password
#----- Embedded Database (default)
# H2 embedded database server listening port, defaults to 9092
# sonar.embeddedDatabase.port=9092
#----- MySQL 5.6 or greater
# Only InnoDB storage engine is supported (not myISAM).
# Only the bundled driver is supported. It can not be changed.
sonar.jdbc.url=jdbc:mysql://localhost:3306/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance&useSSL=false
Log:
--> 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.
2017.01.04 19:38:08 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Program Files (x86)\sonarqube-6.2\temp
2017.01.04 19:38:08 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[es]: C:\Program Files\Java\jre1.8.0_101\bin\java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Program Files (x86)\sonarqube-6.2\temp -javaagent:C:\Program Files\Java\jre1.8.0_101\lib\management-agent.jar -cp ./lib/common/*;./lib/search/* org.sonar.search.SearchServer C:\Program Files (x86)\sonarqube-6.2\temp\sq-process2983841696812955615properties
2017.01.04 19:38:21 INFO app[][o.s.p.m.Monitor] Process[es] is up
2017.01.04 19:38:21 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[web]: C:\Program Files\Java\jre1.8.0_101\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Program Files (x86)\sonarqube-6.2\temp -javaagent:C:\Program Files\Java\jre1.8.0_101\lib\management-agent.jar -cp ./lib/common/*;./lib/server/*;C:\Program Files (x86)\sonarqube-6.2\lib\jdbc\mysql\mysql-connector-java-5.1.39.jar org.sonar.server.app.WebServer C:\Program Files (x86)\sonarqube-6.2\temp\sq-process7994513818856510085properties
2017.01.04 19:38:25 INFO app[][o.s.p.m.Monitor] Process[es] is stopping
2017.01.04 19:38:25 ERROR app[][o.s.p.m.Monitor] Process[web] failed to start
2017.01.04 19:38:26 INFO app[][o.s.p.m.Monitor] Process[es] is stopped
<-- Wrapper Stopped
I was connecting to the wrong schema in the MySQL database. I have set up my user to use the sonarqube schema.
Incorect:
jdbc:mysql://localhost:3306/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance&useSSL=false
Correct:
sonar.jdbc.url=jdbc:mysql://localhost:3306/sonarqube?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance&useSSL=false
I had similar problem with not starting sonarqube-6.7. In background I used 10.1.25-MariaDB-1. The reason why it did not started was in my /opt/sonar/logs/web.log file. There was a message in web.log:
Web server startup failed: Unsupported mysql version: 5.5. Minimal supported version is 5.6.
As i understood this is that MariaDb is not compatible with sonarqube-6.7 although Mariadb seems to be compatible with MySql.
So my solution was to simply switch to another db postgreSQL. And after that sonarqube started successfuly.