Upgrade to 5.6.1 - Still waiting for WebServer

[Hugo]

Hello,

I'm trying to upgrade from sonar qube 5.6 to 5.6.1.
i've been following the documentation on how to do this.

But when I start, sonar won't start complety and get stuck when trying to start the Webserver, here is the sonar.log file :


2016.08.30 12:02:35 INFO  app[o.s.a.AppFileSystem] Cleaning or creating temp directory /applis/sonarqube-5.6.1/temp
2016.08.30 12:02:35 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[es]: /applis/app/java/jdk_1.8.0_66/jre/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=/applis/sonarqube-5.6.1/temp -javaagent:/applis/app/java/jdk_1.8.0_66/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /applis/sonarqube-5.6.1/temp/sq-process3919213409624636441properties
2016.08.30 12:02:35 INFO   es[o.s.p.ProcessEntryPoint]  Starting es
2016.08.30 12:02:35 INFO   es[o.s.s.EsSettings]  Elasticsearch listening on 127.0.0.1:9001
2016.08.30 12:02:35 INFO   es[o.elasticsearch.node]  [sonar-1472551354910] version[1.7.5], pid[82099], build[00f95f4/2016-02-02T09:55:30Z]
2016.08.30 12:02:35 INFO   es[o.elasticsearch.node]  [sonar-1472551354910] initializing ...
2016.08.30 12:02:36 INFO   es[o.e.plugins]  [sonar-1472551354910] loaded [], sites []
2016.08.30 12:02:36 INFO   es[o.elasticsearch.env]  [sonar-1472551354910] using [1] data paths, mounts [[/applis (/dev/mapper/vg0-LV--Applis)]], net usable_space [2.2gb], net total_space [3.7gb], types [ext4]
2016.08.30 12:02:37 WARN   es[o.e.bootstrap]  JNA not found. native methods will be disabled.
2016.08.30 12:02:38 INFO   es[o.elasticsearch.node]  [sonar-1472551354910] initialized
2016.08.30 12:02:38 INFO   es[o.elasticsearch.node]  [sonar-1472551354910] starting ...
2016.08.30 12:02:38 INFO   es[o.e.transport]  [sonar-1472551354910] bound_address {inet[/127.0.0.1:9001]}, publish_address {inet[/127.0.0.1:9001]}
2016.08.30 12:02:38 INFO   es[o.e.discovery]  [sonar-1472551354910] sonarqube/-8XCm7A0TCKmWcmiaoxfoA
2016.08.30 12:02:41 INFO   es[o.e.cluster.service]  [sonar-1472551354910] new_master [sonar-1472551354910][-8XCm7A0TCKmWcmiaoxfoA][rasonar.recette.local][inet[/127.0.0.1:9001]]{rack_id=sonar-1472551354910}, reason: zen-disco-join (elected_as_master)
2016.08.30 12:02:41 INFO   es[o.elasticsearch.node]  [sonar-1472551354910] started
2016.08.30 12:02:42 INFO   es[o.e.gateway]  [sonar-1472551354910] recovered [0] indices into cluster_state
2016.08.30 12:02:42 INFO  app[o.s.p.m.Monitor] Process[es] is up
2016.08.30 12:02:42 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[web]: /applis/app/java/jdk_1.8.0_66/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/applis/sonarqube-5.6.1/temp -javaagent:/applis/app/java/jdk_1.8.0_66/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:/applis/sonarqube-5.6.1/lib/jdbc/mysql/mysql-connector-java-5.1.35.jar org.sonar.server.app.WebServer /applis/sonarqube-5.6.1/temp/sq-process7101996451630613394properties
2016.08.30 12:02:42 INFO  web[o.s.p.ProcessEntryPoint] Starting web
2016.08.30 12:02:43 INFO  web[o.s.s.a.TomcatContexts] Webapp directory: /applis/sonarqube-5.6.1/web
2016.08.30 12:02:43 INFO  web[o.a.c.h.Http11NioProtocol] Initializing ProtocolHandler ["http-nio-0.0.0.0-8080"]
2016.08.30 12:02:43 INFO  web[o.a.t.u.n.NioSelectorPool] Using a shared selector for servlet write/read
2016.08.30 12:02:44 INFO  web[o.s.s.p.ServerImpl] SonarQube Server / 5.6.1 / 07c82b2477ac69126115671fe56d53c2ff47d5f5
2016.08.30 12:02:44 INFO  web[o.sonar.db.Database] Create JDBC data source for jdbc:mysql://localhost:3306/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance
2016.08.30 12:02:46 WARN  web[o.s.s.p.DatabaseServerCompatibility] Database must be upgraded. Please backup database and browse /setup
2016.08.30 12:02:46 INFO  web[o.s.s.p.DefaultServerFileSystem] SonarQube home: /applis/sonarqube-5.6.1
2016.08.30 12:02:46 INFO  web[o.e.plugins] [sonar-1472551354910] loaded [], sites []
2016.08.30 12:02:48 INFO  web[o.s.s.p.RailsAppsDeployer] Deploying Ruby on Rails applications
2016.08.30 12:02:48 INFO  web[o.s.s.p.Platform] DB needs migration, entering safe mode
2016.08.30 12:02:48 INFO  web[jruby.rack] jruby 1.7.9 (ruby-1.8.7p370) 2013-12-06 87b108a on Java HotSpot(TM) 64-Bit Server VM 1.8.0_66-b17 [linux-amd64]
2016.08.30 12:02:48 INFO  web[jruby.rack] using a shared (threadsafe!) runtime
2016.08.30 12:03:00 INFO  web[jruby.rack] keeping custom (config.logger) Rails logger instance
2016.08.30 12:03:00 INFO  web[o.a.c.h.Http11NioProtocol] Starting ProtocolHandler ["http-nio-0.0.0.0-8080"]
2016.08.30 12:03:01 INFO  web[o.s.s.a.TomcatAccessLog] Web server is started
2016.08.30 12:03:01 INFO  web[o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 8080
2016.08.30 12:03:01 INFO  app[o.s.p.m.Monitor] Process[web] is up
2016.08.30 12:03:01 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[ce]: /applis/app/java/jdk_1.8.0_66/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/applis/sonarqube-5.6.1/temp -javaagent:/applis/app/java/jdk_1.8.0_66/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/applis/sonarqube-5.6.1/lib/jdbc/mysql/mysql-connector-java-5.1.35.jar org.sonar.ce.app.CeServer /applis/sonarqube-5.6.1/temp/sq-process7128586203009610425properties
2016.08.30 12:03:02 INFO  ce[o.s.p.ProcessEntryPoint] Starting ce
2016.08.30 12:03:02 INFO  ce[o.s.c.a.WebServerWatcherImpl] Waiting for Web Server to be operational...
2016.08.30 12:03:03 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 12:03:05 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 12:03:10 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 12:03:23 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 12:03:57 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 12:05:31 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 12:09:46 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...



I'm stuck at this step. When doing roll back to 5.6 everything is fine.
Note that I'm using sonar user to run sonarqube.

Any tips on how to troubleshoot this ?

Thank you !

[Hugo]

Ok, I'll answer to my question as I found the solution, simply go to :

https://URL_OF_SONAR/update

and there an upgrade sonarqube interface is waiting for running sql script.

[Sebastien Lesaint]

Hello,

As stated in the following line extracted from the logs you provided, you must upgrade the database by going to the "/setup" URL on your server:

2016.08.30 12:02:46 WARN  web[o.s.s.p.DatabaseServerCompatibility] Database must be upgraded. Please backup database and browse /setup

This is clearly documented as step 6 of the migration documentation.

Cheers,

Sébastien LESAINT | SonarSource
Platform Developer

http://sonarsource.com

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/78bcdf89-f8de-43df-9d88-2320d9bf669e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[nicolas...@sonarsource.com]

Hi Hugo,

The URL to browse is actually /setup , as mentioned in the Upgrade Guide: http://docs.sonarqube.org/display/SONARQUBE56/Upgrading .

Best regards,

Nicolas

[darren...@gmail.com]

Hi,

I'm trying to upgrade from 5.1 to 5.6.1 and am also stuck.

I'm following these instructions http://docs.sonarqube.org/display/SONARQUBE56/Upgrading,
there were PostgreSQL database connections and some locking activity so I assumed that
the long running schema updates were happening. At the time and now 12 hours later
http://<server>:9000/setup is unresponsive and provides no instructions to follow.

There are my last log entries

2016.08.30 18:12:28 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[ce]: /opt/COTS/jdk1.8.0_45/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/home/ci_ltsa/sonar/sonarqube-5.6.1/temp -javaagent:/opt/COTS/jdk1.8.0_45/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/home/ci_ltsa/sonar/sonarqube-5.6.1/lib/jdbc/postgresql/postgresql-9.3-1102-jdbc41.jar org.sonar.ce.app.CeServer /home/ci_ltsa/sonar/sonarqube-5.6.1/temp/sq-process8441188086957488085properties
2016.08.30 18:12:28 INFO  ce[o.s.p.ProcessEntryPoint] Starting ce
2016.08.30 18:12:28 INFO  ce[o.s.c.a.WebServerWatcherImpl] Waiting for Web Server to be operational...
2016.08.30 18:12:29 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 18:12:31 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 18:12:36 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...
2016.08.30 18:12:49 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...


Is there any way to turn up debugging so I can see what is going on?
Are there some checks I can perform to see if the schema upgrade completed correctly?
Will I have more chance of success if I throw away my sonarqube database and do a new fresh install?

Thanks,
Darren

[Simon Brandhof]

Hi Darren,

According to your logs database upgrade has not been triggered. Did you browse to /setup and submit the form ?

If yes, then could you please send the full logs ?

Thanks

--

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/a720f376-ed25-479e-84be-8c02c20767d8%40googlegroups.com.

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

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[darren...@gmail.com]

Hi,

I have Apache in front of Tomcat using mod_proxy and had set

sonar.web.context=/sonarqube

I needed to update the database using http://<server>:9000/sonarqube/setup.
It has successfully updated and is now working.

(Simon, thanks for taking the time to respond.)

[prof...@gmail.com]

Hi,

I have the same problem but in my case here's the full log from a start:

2016.12.07 16:17:18 INFO  app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-5.6.3/temp

2016.12.07 16:17:18 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/lib/jvm/java-8-oracle/jre/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=/opt/sonarqube-5.6.3/temp -javaagent:/usr/lib/jvm/java-8-oracle/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /opt/sonarqube-5.6.3/temp/sq-process2514923939970753949properties

2016.12.07 16:17:19 INFO   es[o.s.p.ProcessEntryPoint]  Starting es

2016.12.07 16:17:19 INFO   es[o.s.s.EsSettings]  Elasticsearch listening on 127.0.0.1:9001

2016.12.07 16:17:19 INFO   es[o.elasticsearch.node]  [sonar-1481123838165] version[1.7.5], pid[25896], build[00f95f4/2016-02-02T09:55:30Z]

2016.12.07 16:17:19 INFO   es[o.elasticsearch.node]  [sonar-1481123838165] initializing ...

2016.12.07 16:17:19 INFO   es[o.e.plugins]  [sonar-1481123838165] loaded [], sites []

2016.12.07 16:17:19 INFO   es[o.elasticsearch.env]  [sonar-1481123838165] using [1] data paths, mounts [[/ (/dev/sda1)]], net usable_space [14.3gb], net total_space [19.5gb], types [ext4]

2016.12.07 16:17:22 WARN   es[o.e.bootstrap]  JNA not found. native methods will be disabled.

2016.12.07 16:17:23 INFO   es[o.elasticsearch.node]  [sonar-1481123838165] initialized

2016.12.07 16:17:23 INFO   es[o.elasticsearch.node]  [sonar-1481123838165] starting ...

2016.12.07 16:17:23 INFO   es[o.e.transport]  [sonar-1481123838165] bound_address {inet[/127.0.0.1:9001]}, publish_address {inet[/127.0.0.1:9001]}

2016.12.07 16:17:23 INFO   es[o.e.discovery]  [sonar-1481123838165] sonarqube/lK5KExRWTcep7ThVUBl_KA

2016.12.07 16:17:26 INFO   es[o.e.cluster.service]  [sonar-1481123838165] new_master [sonar-1481123838165][lK5KExRWTcep7ThVUBl_KA][sonar.cloud.mdc.hu][inet[/127.0.0.1:9001]]{rack_id=sonar-1481123838165}, reason: zen-disco-join (elected_as_master)

2016.12.07 16:17:26 INFO   es[o.elasticsearch.node]  [sonar-1481123838165] started

2016.12.07 16:17:26 INFO   es[o.e.gateway]  [sonar-1481123838165] recovered [0] indices into cluster_state

2016.12.07 16:17:27 INFO  app[o.s.p.m.Monitor] Process[es] is up

2016.12.07 16:17:27 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[web]: /usr/lib/jvm/java-8-oracle/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/opt/sonarqube-5.6.3/temp -javaagent:/usr/lib/jvm/java-8-oracle/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:/opt/sonarqube-5.6.3/extensions/jdbc-driver/oracle/ojdbc5.jar org.sonar.server.app.WebServer /opt/sonarqube-5.6.3/temp/sq-process3494146962219639118properties

2016.12.07 16:17:28 INFO  web[o.s.p.ProcessEntryPoint] Starting web

2016.12.07 16:17:28 INFO  web[o.s.s.a.TomcatContexts] Webapp directory: /opt/sonarqube-5.6.3/web

2016.12.07 16:17:29 INFO  web[o.a.c.h.Http11NioProtocol] Initializing ProtocolHandler ["http-nio-0.0.0.0-9090"]

2016.12.07 16:17:29 INFO  web[o.a.t.u.n.NioSelectorPool] Using a shared selector for servlet write/read

2016.12.07 16:17:29 INFO  web[o.a.c.h.Http11NioProtocol] Starting ProtocolHandler ["http-nio-0.0.0.0-9090"]

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

2016.12.07 16:17:29 INFO  web[o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9090

2016.12.07 16:17:30 INFO  app[o.s.p.m.Monitor] Process[web] is up

2016.12.07 16:17:30 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[ce]: /usr/lib/jvm/java-8-oracle/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.3/temp -javaagent:/usr/lib/jvm/java-8-oracle/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/opt/sonarqube-5.6.3/extensions/jdbc-driver/oracle/ojdbc5.jar org.sonar.ce.app.CeServer /opt/sonarqube-5.6.3/temp/sq-process8233389130721694213properties

2016.12.07 16:17:31 INFO  ce[o.s.p.ProcessEntryPoint] Starting ce

2016.12.07 16:17:31 INFO  ce[o.s.c.a.WebServerWatcherImpl] Waiting for Web Server to be operational...

2016.12.07 16:17:32 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2016.12.07 16:17:34 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2016.12.07 16:17:39 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2016.12.07 16:17:52 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2016.12.07 16:18:26 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2016.12.07 16:20:00 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2016.12.07 16:24:15 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

I can't see that sonarqube tries to create a jdbc connection.

Because of this, I'm trying to hit SONAR/setup in vain - nothing happens.

My goal is to upgrade to the latest, 6.1 version from 5.1. If I start 6.1 it tells that I have to upgrade to a LTS version before upgrading to 6.1.

Thanks,

Endre

[prof...@gmail.com]

Hi,

I have the same problem but in my case here's the full log from a start:

2016.12.07 16:17:18 INFO  app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-5.6.3/temp

2016.12.07 16:17:18 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/lib/jvm/java-8-oracle/jre/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=/opt/sonarqube-5.6.3/temp -javaagent:/usr/lib/jvm/java-8-oracle/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /opt/sonarqube-5.6.3/temp/sq-process2514923939970753949properties

2016.12.07 16:17:19 INFO   es[o.s.p.ProcessEntryPoint]  Starting es

2016.12.07 16:17:19 INFO   es[o.s.s.EsSettings]  Elasticsearch listening on 127.0.0.1:9001

[Simon Brandhof]

Hi,

Did you unzip SonarQube in a fresh directory then touch only conf/sonar.properties ? This strange behaviour seems to relate to a change in internal web.xml.

Thanks

--

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/1431d618-01e0-4eae-a629-54527fc536c0%40googlegroups.com.

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

[Endre Deak]

Dear Simon,

Thanks for your reply, yes, I'm working on a totally fresh and separated directory.

Thanks,

Endre

To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/1431d618-01e0-4eae-a629-54527fc536c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Simon Brandhof]

Did you try to start server with the default embedded database, without touching configuration ?

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/1431d618-01e0-4eae-a629-54527fc536c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[Endre Deak]

I give it a try now and reply immediately.

On Wed, Dec 7, 2016 at 5:25 PM, Simon Brandhof <simon.b...@sonarsource.com> wrote:

Did you try to start server with the default embedded database, without touching configuration ?

On Wed, 7 Dec 2016 at 17:22 Endre Deak <prof...@gmail.com> wrote:

Dear Simon,

Thanks for your reply, yes, I'm working on a totally fresh and separated directory.

Thanks,

Endre

To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/1431d618-01e0-4eae-a629-54527fc536c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[Endre Deak]

I started the whole process from the beginning. 

Now it works with the default database (untouched config).

And it works with the modified config.

Something I messed up... 

Thanks!

On Wed, Dec 7, 2016 at 5:26 PM, Endre Deak <prof...@gmail.com> wrote:

I give it a try now and reply immediately.

On Wed, Dec 7, 2016 at 5:25 PM, Simon Brandhof <simon.brandhof@sonarsource.com> wrote:

Did you try to start server with the default embedded database, without touching configuration ?

On Wed, 7 Dec 2016 at 17:22 Endre Deak <prof...@gmail.com> wrote:

Dear Simon,

Thanks for your reply, yes, I'm working on a totally fresh and separated directory.

Thanks,

Endre

[Simon Brandhof]

Great, but I'm not sure that it's a good news !

Do you remember which settings did you set in the initial configuration ?

On Wed, 7 Dec 2016 at 17:40 Endre Deak <prof...@gmail.com> wrote:

I started the whole process from the beginning. 

Now it works with the default database (untouched config).

And it works with the modified config.

Something I messed up... 

Thanks!

On Wed, Dec 7, 2016 at 5:26 PM, Endre Deak <prof...@gmail.com> wrote:

I give it a try now and reply immediately.

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/1431d618-01e0-4eae-a629-54527fc536c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[Endre Deak]

I changed the port number, and the following:

sonar.jdbc.url,

sonar.jdbc.username,

sonar.jdbc.password,

and the jdbc connection related settings (max idle, etc) was uncommented.

On Wed, Dec 7, 2016 at 5:43 PM, Simon Brandhof <simon.b...@sonarsource.com> wrote:

Great, but I'm not sure that it's a good news !

Do you remember which settings did you set in the initial configuration ?

On Wed, 7 Dec 2016 at 17:40 Endre Deak <prof...@gmail.com> wrote:

I started the whole process from the beginning. 

Now it works with the default database (untouched config).

And it works with the modified config.

Something I messed up... 

Thanks!

On Wed, Dec 7, 2016 at 5:26 PM, Endre Deak <prof...@gmail.com> wrote:

I give it a try now and reply immediately.

To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/1431d618-01e0-4eae-a629-54527fc536c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[a.kor...@mephix.com]

I know this is an old thread, but I am currently running into a similar issue.

I am trying to upgrade from 5.6 to 5.6.4

After unzipping SonarQube 5.6.4 and setting everything up in sonar.properties and wrapper.conf the same as it was in 5.6, I am presented with the /maintance page. So I went to /setup and hit the Upgrade database button, but the only thing it seems to do, is redirect me to /maintenance

In the access logs I then see a request for /api/status or something every 5 seconds, which is the maintenance page trying to find out if the upgrade has completed.

In the sonar.log I just see this line being repeated:

ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

It just seems like the Upgrade button on /setup page doesnt do anything and from the logs I cant figure out why. Even setting log.level to DEBUG doesn't provide much more helpful details.

Any help would be greatly appreciated.

[nor...@gmail.com]

I'm having this same exact issue, upgrading from 5.4 to 5.6.4.

Unzipped into fresh directory.  Updated sonar.properties DB connection string and user/pass, as well as http/s proxy settings and authorization settings (we use LDAP).  Start it up, browse to .../setup, click the Upgrade button.

Upgrade button doesn't seem to do anything, other than trigger load of maintenance page.  Left it overnight and found it in the same state in the morning.

In my case this is Windows, and I used the Uninstall... bat script to uninstall the old Services entry, then the Install... bat script from the new version to setup the new Services entry (windows-x86-64).

I reverted back to 5.4 - without restoring my DB - and it starts up and runs just fine.  So it seems like the DB upgrade just isn't running at all. 

If I get a chance I'll set trace log level and send the resulting log.

[nicolas...@sonarsource.com]

Hi,

Couple of sanity checks:

• use your browser's inspector and see if there's any error raised when hitting the Upgrade button
  
• also attach the sonar.properties config file used when attempting the upgrade, to see which properties are effective (could give a hint on the underlying potential issue)
  

Best regards,

Nicolas

[a.kor...@mephix.com]

Hi Nicolas,

Sorry for the late response, I was on leave for the last two weeks.

I again tried to upgrade SonarQube from version 5.6 to 5.6.4 and ran into the same issue that the database doesn't seem to be updated.

This time I watched the browser and here's what happens:

Upon clicking the Upgrade button on /setup page, a request is sent to /sessions/new?return_to=%2Fsetup

The server responds with a 302 status en redirects to /maintenance

From there the page starts ajax polling to /api/system/status which receives a 200 response with a body like {"id":"20170111092644","version":"5.6.4","status":"DB_MIGRATION_NEEDED"}

No errors (JS or otherwise) occur.

This seems normal behavior to me, except that the database in fact doesn't get updated and thus the ajax call always gets the same response (migration needed). Clicking the Upgrade button again gives the same results.

 After removing all commented lines from sonar.properties, the file looks like this:

sonar.security.realm=LDAP
sonar.forceAuthentication=true

ldap.realm=<customer domain>
sonar.jdbc.url=jdbc:sqlserver://localhost;databaseName=Sonar;integratedSecurity=true

sonar.web.port=80
sonar.log.level=INFO
sonar.path.logs=logs
sonar.log.rollingPolicy=time:yyyy-MM-dd
sonar.log.maxFiles=7
sonar.web.accessLogs.enable=true
sonar.web.accessLogs.pattern=%i{X-Forwarded-For} %l %u [%t] "%r" %s %b "%i{Referer}" "%i{User-Agent}"
sonar.web.accessLogs.pattern=combined

SonarQube runs on a Windows 2012 R2 server, with MS SQL 2014 installed locally.

[nicolas...@sonarsource.com]

Hi,

Problem could come from the fact that you manually set sonar.forceAuthentication in sonar.properties (rather than managing it in the admin settings). Remove it from there, restart your SonarQube and try the upgrade once again.

Later on you can re-activate sonar.forceAuthentication , however this time do it in the admin settings (under General Settings - Security). Doing this from the settings interface means that this property will be properly persisted and managed in database. That way you do not have to manually maintain it in a config file and most importantly the property will be gracefully handled during version upgrades.

Best regards,

Nicolas

[a.kor...@mephix.com]

Hi Nicolas,

Thank you for your support, this indeed fixed the issue for our environment.

After removing the forceAuthentication setting from sonar.properties, the database got updated to 5.6.4 and everything is running fine now.

Regards,

Arjen

[nicolas...@sonarsource.com]

Perfect ! Thanks for the update. And from now on do manage Forced Authentication as an Admin setting in the UI (under General Settings - Security).

Best regards,

Nicolas

[rjl...@hotmail.com]

Greetings,

I have also run into this issue when trying to upgrade from 5.6 to 5.6.5.  I downloaded 5.6.5 and extracted to a new folder.  I was able to start Sonar with the default sonar.properties and wrapper.conf, but when I loaded my own settings, I got "Waiting for Web Server to be operational..." and the DB was never migrated.  Here's the whole 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.02.13 06:50:50 INFO  app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sw\sonarqube-5.6.5\temp

2017.02.13 06:50:50 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[es]: C:\sw\jdk180_45\jre\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:\sw\sonarqube-5.6.5\temp -javaagent:C:\sw\jdk180_45\jre\lib\management-agent.jar -cp ./lib/common/*;./lib/search/* org.sonar.search.SearchServer C:\sw\sonarqube-5.6.5\temp\sq-process7581056885185163211properties

2017.02.13 06:50:51 INFO   es[o.s.p.ProcessEntryPoint]  Starting es

2017.02.13 06:50:51 INFO   es[o.s.s.EsSettings]  Elasticsearch listening on 127.0.0.1:9001

2017.02.13 06:50:51 INFO   es[o.elasticsearch.node]  [sonar-1486990250599] version[1.7.5], pid[4768], build[00f95f4/2016-02-02T09:55:30Z]

2017.02.13 06:50:51 INFO   es[o.elasticsearch.node]  [sonar-1486990250599] initializing ...

2017.02.13 06:50:51 INFO   es[o.e.plugins]  [sonar-1486990250599] loaded [], sites []

2017.02.13 06:50:52 INFO   es[o.elasticsearch.env]  [sonar-1486990250599] using [1] data paths, mounts [[(C:)]], net usable_space [32.2gb], net total_space [59.9gb], types [NTFS]

2017.02.13 06:50:54 WARN   es[o.e.bootstrap]  JNA not found. native methods will be disabled.

2017.02.13 06:50:54 INFO   es[o.elasticsearch.node]  [sonar-1486990250599] initialized

2017.02.13 06:50:54 INFO   es[o.elasticsearch.node]  [sonar-1486990250599] starting ...

2017.02.13 06:50:54 INFO   es[o.e.transport]  [sonar-1486990250599] bound_address {inet[/127.0.0.1:9001]}, publish_address {inet[/127.0.0.1:9001]}

2017.02.13 06:50:54 INFO   es[o.e.discovery]  [sonar-1486990250599] sonarqube/er7KHeu0QnKlPvNQiIFMiQ

2017.02.13 06:50:57 INFO   es[o.e.cluster.service]  [sonar-1486990250599] new_master [sonar-1486990250599][er7KHeu0QnKlPvNQiIFMiQ][JBVDEVD12A][inet[/127.0.0.1:9001]]{rack_id=sonar-1486990250599}, reason: zen-disco-join (elected_as_master)

2017.02.13 06:50:57 INFO   es[o.elasticsearch.node]  [sonar-1486990250599] started

2017.02.13 06:50:57 INFO   es[o.e.gateway]  [sonar-1486990250599] recovered [6] indices into cluster_state

2017.02.13 06:50:59 INFO  app[o.s.p.m.Monitor] Process[es] is up

2017.02.13 06:50:59 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[web]: C:\sw\jdk180_45\jre\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=C:\sw\sonarqube-5.6.5\temp -javaagent:C:\sw\jdk180_45\jre\lib\management-agent.jar -cp ./lib/common/*;./lib/server/*;C:\sw\sonarqube-5.6.5\lib\jdbc\mssql\sqljdbc42.jar org.sonar.server.app.WebServer C:\sw\sonarqube-5.6.5\temp\sq-process8935084210641874614properties

2017.02.13 06:51:00 INFO  web[o.s.p.ProcessEntryPoint] Starting web

2017.02.13 06:51:00 INFO  web[o.s.s.a.TomcatContexts] Webapp directory: C:\sw\sonarqube-5.6.5\web

2017.02.13 06:51:00 INFO  web[o.a.c.h.Http11NioProtocol] Initializing ProtocolHandler ["http-nio-0.0.0.0-9000"]

2017.02.13 06:51:00 INFO  web[o.a.t.u.n.NioSelectorPool] Using a shared selector for servlet write/read

2017.02.13 06:51:01 INFO  web[o.s.s.p.ServerImpl] SonarQube Server / 5.6.5 / 29a8d73d1b3fb39fd35c777bf07be40873391517

2017.02.13 06:51:01 INFO  web[o.sonar.db.Database] Create JDBC data source for jdbc:sqlserver://sonarqubedev;databaseName=SONARQUBEDEV

2017.02.13 06:51:02 WARN  web[o.s.s.p.DatabaseServerCompatibility] Database must be upgraded. Please backup database and browse /setup

2017.02.13 06:51:02 INFO  web[o.s.s.p.DefaultServerFileSystem] SonarQube home: C:\sw\sonarqube-5.6.5

2017.02.13 06:51:02 INFO  web[o.e.plugins] [sonar-1486990250599] loaded [], sites []

2017.02.13 06:51:03 INFO  web[o.s.s.p.ServerPluginRepository] Deploy plugin C# / 5.7.0.612 / 6c7d5830a41c62429eade2ead6e3fdf12a388856

2017.02.13 06:51:03 INFO  web[o.s.s.p.ServerPluginRepository] Deploy plugin Git / 1.2 / a713dd64daf8719ba4e7f551f9a1966c62690c17

2017.02.13 06:51:03 INFO  web[o.s.s.p.ServerPluginRepository] Deploy plugin Java / 4.5.0.8398 / f5a869c42a13d27735d57da1691ca167093a885b

2017.02.13 06:51:03 INFO  web[o.s.s.p.ServerPluginRepository] Deploy plugin SVN / 1.4.0.522 / 1309b92a587d1c8fd55a2981c69ceadc1f79e79c

2017.02.13 06:51:03 INFO  web[o.s.s.p.ServerPluginRepository] Deploy plugin SonarJS / 2.20.0.4207 / d65285af4c43250613fa9d176207aeda9176d20a

2017.02.13 06:51:04 INFO  web[o.s.s.p.RailsAppsDeployer] Deploying Ruby on Rails applications

2017.02.13 06:51:04 INFO  web[o.s.s.p.Platform] DB needs migration, entering safe mode

2017.02.13 06:51:04 INFO  web[jruby.rack] jruby 1.7.9 (ruby-1.8.7p370) 2013-12-06 87b108a on Java HotSpot(TM) 64-Bit Server VM 1.8.0_45-b15 [Windows Server 2012 R2-amd64]

2017.02.13 06:51:04 INFO  web[jruby.rack] using a shared (threadsafe!) runtime

2017.02.13 06:51:13 INFO  web[jruby.rack] keeping custom (config.logger) Rails logger instance

2017.02.13 06:51:13 INFO  web[o.a.c.h.Http11NioProtocol] Starting ProtocolHandler ["http-nio-0.0.0.0-9000"]

2017.02.13 06:51:13 INFO  web[o.s.s.a.TomcatAccessLog] Web server is started

2017.02.13 06:51:13 INFO  web[o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000

2017.02.13 06:51:14 INFO  app[o.s.p.m.Monitor] Process[web] is up

2017.02.13 06:51:14 INFO  app[o.s.p.m.JavaProcessLauncher] Launch process[ce]: C:\sw\jdk180_45\jre\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=C:\sw\sonarqube-5.6.5\temp -javaagent:C:\sw\jdk180_45\jre\lib\management-agent.jar -cp ./lib/common/*;./lib/server/*;./lib/ce/*;C:\sw\sonarqube-5.6.5\lib\jdbc\mssql\sqljdbc42.jar org.sonar.ce.app.CeServer C:\sw\sonarqube-5.6.5\temp\sq-process9079631834527442157properties

2017.02.13 06:51:15 INFO  ce[o.s.p.ProcessEntryPoint] Starting ce

2017.02.13 06:51:15 INFO  ce[o.s.c.a.WebServerWatcherImpl] Waiting for Web Server to be operational...

2017.02.13 06:51:16 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.13 06:51:18 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.13 06:51:23 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.13 06:51:36 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.13 06:52:10 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.13 06:53:46 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

Here are my settings from sonar.properties:

sonar.security.realm=LDAP

sonar.authenticator.createUsers=true

sonar.security.savePassword=true

ldap.url=ldap://prdldap.jbhunt.com:389 

ldap.bindDn=CN=pidhdarc,OU=Internal_Users,OU=Active,OU=Authentication,DC=jbhunt,DC=com

ldap.bindPassword=cia35021

ldap.user.baseDn=OU=Internal_Users,OU=Active,OU=Authentication,DC=jbhunt,DC=com

ldap.user.request=(&(objectClass=user)(sAMAccountName={login}))

sonar.jdbc.username=PIDSONR1

sonar.jdbc.password=xxxxxx

sonar.jdbc.url=jdbc:sqlserver://sonarqubedev;databaseName=SONARQUBEDEV;SelectMethod=Cursor

sonar.jdbc.maxActive=20

sonar.jdbc.maxIdle=5

sonar.jdbc.minIdle=2

sonar.jdbc.maxWait=5000

sonar.jdbc.minEvictableIdleTimeMillis=600000

sonar.jdbc.timeBetweenEvictionRunsMillis=30000

sonar.web.port=80

Here are my settings from wrapper.conf:

wrapper.java.additional.1=-Djava.awt.headless=true

wrapper.java.additional.2=-XX:MaxPermSize=128m

wrapper.java.initmemory=256

wrapper.java.maxmemory=512

wrapper.java.command=C:\sw\jdk180_45\bin\java

 

I did try the whole process with no changes to the wrapper.conf and only the JDBC changes to sonar.properties, and I got the same result.  I think I even tried with only the JDBC username, password, and url, and I was really surprised when that didn't work.

Thanks for any help you can provide.

Bob

[Julien Lancelot]

Hi,

Having a look at the log, you'll see : 

2017.02.13 06:51:02 WARN  web[o.s.s.p.DatabaseServerCompatibility] Database must be upgraded. Please backup database and browse /setup

You need to backup your database and browse /setup.

Regards,

--
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/df6d029b-6990-4a93-8552-b3d9fbad52e5%40googlegroups.com.

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

--

Julien LANCELOT | SonarSource

http://sonarsource.com

[rjl...@hotmail.com]

Hi Julien,

I apologize for not mentioning that I had already done that.  I browsed to /setup, and it ran for over 24 hours and just filled the log with these sorts of lines:

2017.02.12 17:58:38 INFO  ce[o.s.c.a.WebServerWatcherImpl] Waiting for Web Server to be operational...

2017.02.12 17:58:39 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 17:58:41 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 17:58:46 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 17:58:59 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 17:59:34 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 18:01:09 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 18:03:51 INFO  web[o.s.s.d.m.PlatformDatabaseMigration] Starting DB Migration

2017.02.12 18:03:52 INFO  web[DbMigration] ==  CleanUsurperRootComponents: migrating =====================================

2017.02.12 18:03:52 INFO  web[DbMigration] -- index_exists?("project_measures", "project_id", {:name=>"tmp_measures_project_id"})

2017.02.12 18:03:52 INFO  web[DbMigration]    -> 0.0180s

2017.02.12 18:03:52 INFO  web[DbMigration] -- add_index("project_measures", "project_id", {:name=>"tmp_measures_project_id"})

2017.02.12 18:03:53 INFO  web[DbMigration]    -> 1.1220s

2017.02.12 18:03:53 INFO  web[DbMigration]    -> 0 rows

2017.02.12 18:03:53 INFO  web[o.s.d.v.MassUpdate] 0 developers with incorrect project_uuid processed (0 items/sec)

2017.02.12 18:03:53 INFO  web[o.s.d.v.MassUpdate] 0 snapshots with inconsistent scope or qualifier processed (0 items/sec)

2017.02.12 18:04:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:05:28 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 18:05:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:06:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:07:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:08:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:09:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:10:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:11:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:12:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:13:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:14:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:15:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:16:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:17:12 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 18:17:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:18:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:19:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:20:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:21:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:22:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:23:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:24:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:25:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:26:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:27:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:28:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:29:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:30:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:31:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:32:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:33:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:34:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:35:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:36:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:37:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:38:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:39:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:40:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:41:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:42:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:43:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:44:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:45:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:46:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:47:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:48:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:49:05 INFO  ce[o.s.c.a.WebServerWatcherImpl] Still waiting for WebServer...

2017.02.12 18:49:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:50:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:51:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:52:53 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:53:54 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

2017.02.12 18:54:54 INFO  web[o.s.d.v.MassUpdate] 41 usurper root components processed (0 items/sec)

Thanks,

Bob

[Julien Lancelot]

This is a known issue, it will be fixed in 5.6.6 => https://jira.sonarsource.com/browse/SONAR-8728

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/bb1146c9-703c-4927-88bc-23b482285595%40googlegroups.com.

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

[rjl...@hotmail.com]

Thank you, Julien.

[indra...@gmail.com]

I am also having an issue not in upgrade , but just to start the server . 

the version is 5.6 

Can someone pls suggest  

[vishy]

Thanks, I faced the same issue while upgrading from SonarQube 5.2 to 5.6.7. Commenting sonar.forceAuthentication in sonar.properties allowed me to move a step forward. 

Database upgrade commenced when initiated from the setup page. However it failed in the middle since 'ldap.url' was not specified in my properties file. After providing a LDAP URL I could successfully complete the DB upgrade and was able to use 5.6.7.

Thanks again!