Sonarqube app crashes after the upgrade

[kalyan...@gmail.com]

I upgraded the sonarqube version to a 6.3 . Everything works well but when I update the sonar.properties file to include the JDBC connection string values , the app crashes . Until otherwise the app works fine but it uses the embedded database . Any help is greatly appreciated.

[Eric Hartmann]

Hi,

Did you have a look at the log files that will explain you where the issue is ? If you don't find the issue, please post them here.

Cheers,

On Tue, May 23, 2017 at 10:51 PM <kalyan...@gmail.com> wrote:

I upgraded the sonarqube version to a 6.3 . Everything works well but when I update the sonar.properties file to include the JDBC connection string values , the app crashes . Until otherwise the app works fine but it uses the embedded database . Any help is greatly appreciated.

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/cfc9202c-b7b5-43bc-84bd-b66c8afc4dd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Eric HARTMANN | SonarSource

http://sonarsource.com

[kalyan...@gmail.com]

Launching a JVM...

Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org

  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

2017.05.23 20:26:34 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube_upgrade/sonarqube-6.3.1/temp

2017.05.23 20:26:34 INFO  app[][o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/java/jdk1.8.0_101/jre/bin/java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Duser.timezone=America/Chicago -Djava.io.tmpdir=/opt/sonarqube_upgrade/sonarqube-6.3.1/temp -javaagent:/usr/java/jdk1.8.0_101/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /opt/sonarqube_upgrade/sonarqube-6.3.1/temp/sq-process603646605943289830properties

2017.05.23 20:26:41 INFO  app[][o.s.p.m.Monitor] Process[es] is up

2017.05.23 20:26:41 INFO  app[][o.s.p.m.JavaProcessLauncher] Launch process[web]: /usr/java/jdk1.8.0_101/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/opt/sonarqube_upgrade/sonarqube-6.3.1/temp -javaagent:/usr/java/jdk1.8.0_101/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:/opt/sonarqube_upgrade/sonarqube-6.3.1/lib/jdbc/mssql/sqljdbc4.jar org.sonar.server.app.WebServer /opt/sonarqube_upgrade/sonarqube-6.3.1/temp/sq-process8441354933557958450properties

2017.05.23 20:27:05 INFO  app[][o.s.p.m.Monitor] Process[es] is stopping

2017.05.23 20:27:05 ERROR app[][o.s.p.m.Monitor] Process[web] failed to start

2017.05.23 20:27:06 INFO  app[][o.s.p.m.Monitor] Process[es] is stopped

<-- Wrapper Stopped

--> Wrapper Started as Daemon

 

This is what I see in the logs , not much info for me 

[Eric Hartmann]

Hi,

Please note that standard courtesy are really appreciated here.

Have a look at logs/web.log where you'll find the reason of the failure.

Cheers,

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7a02df24-8a9a-4a6b-9d67-a85d4ab50f00%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[kalyan...@gmail.com]

Hey sorry I didnt mean to show no courtesy , i greatly appreciate your help to me for this . Just that I happen to be in a rush and send this . I cant thank you all community for trying to help me with this . Sorry again !!!

BTW , this is what I find in the web.log , any thought is greatly appreciated .....

2017.05.24 16:00:28 ERROR web[][o.a.c.c.C.[.[.[/]] Exception sending context initialized event to listener instance of class org.sonar.server.platform.web.PlatformServletContextListener

org.sonar.api.utils.MessageException: Database collation must be case-sensitive and accent-sensitive. It is SQL_Latin1_General_CP1_CI_AS but should be SQL_Latin1_General_CP1_CS_AS.

2017.05.24 16:00:28 ERROR web[][o.a.c.c.StandardContext] One or more listeners failed to start. Full details will be found in the appropriate container log file

2017.05.24 16:00:29 INFO  web[][o.a.c.u.SessionIdGeneratorBase] Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [829] milliseconds.

2017.05.24 16:00:29 ERROR web[][o.a.c.c.StandardContext] Context [] startup failed due to previous errors

2017.05.24 16:00:29 INFO  web[][o.s.s.a.TomcatAccessLog] Web server is started

2017.05.24 16:00:29 INFO  web[][o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000

2017.05.24 16:00:29 WARN  web[][o.s.p.ProcessEntryPoint] Fail to start web

java.lang.IllegalStateException: Webapp did not start

        at org.sonar.server.app.EmbeddedTomcat.isUp(EmbeddedTomcat.java:83)

        at org.sonar.server.app.WebServer.isUp(WebServer.java:46)

        at org.sonar.process.ProcessEntryPoint.launch(ProcessEntryPoint.java:105)

        at org.sonar.server.app.WebServer.main(WebServer.java:67)

2017.05.24 16:00:29 INFO  web[][o.s.s.a.TomcatAccessLog] Web server is stopped

[Eric Hartmann]

Hi,

Your issue is due to incorrect configuration of your Microsoft SQL Server. The current collation is SQL_Latin1_General_CP1_CI_AS instead of SQL_Latin1_General_CP1_CS_AS.

So in order to start correctly Sonarqube you must change the MsSQL collation of your database, you will find the command there : https://docs.microsoft.com/en-us/sql/relational-databases/collations/set-or-change-the-database-collation

Cheers,

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/c02bd269-d5c1-40a0-af2b-9a1ff7014ae0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.