Upsource 2.5 fails to start with data and conf copied from old instance with Error while starting JetBrains Upsource 2.5: Not allowed exit code -1 from process: bin/upsource-cluster-init start

Hi,
we upgraded to Upsource 2.5 and followed the documentation:
* Stopped Upsource Service
* renamed upsource to upsource.old
* deinstalled service (recommendation in another thread here)
* copied new upsource installation
* deleted conf from new installation
* copied conf & data from old installation to new installation
* Install Service
* Start Service

Following error occurs:


[2016-01-08 11:21:13,503] console                           [Info] * Starting Upsource Cluster Initialize Service
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Starting Upsource Cluster Initialize Service...
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Writing logs to C:\Upsource\logs\upsource-cluster-init
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: [Upsource Cluster Initialize Service Error] [2016-01-08 11:21:33,412] WARN  APP-WRAPPER] Proxy 1                 datastax.driver.core.NettyUtil - Found Netty's native epoll transport, but not running on linux-based operating system. Using NIO instead.
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: [Upsource Cluster Initialize Service Error] Core version mismatch. Database update not possible
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Upsource Cluster Initialize Service failed to start
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Using logs configuration from C:\Upsource\conf\upsource-cluster-init\log4j.xml.dist
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Loading Upsource properties file: C:\Upsource\conf\upsource-cluster-init\upsource.properties
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Upsource properties file C:\Upsource\conf\upsource.user.properties not found!
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Upsource Cluster Initialize Service process finished
[2016-01-08 11:21:41,266] console                           [Info] upsource-cluster-init: Launcher is exiting
[2016-01-08 11:21:41,266] console                           [Info] * Error while starting JetBrains Upsource 2.5: Not allowed exit code -1 from process: bin/upsource-cluster-init start
[2016-01-08 11:21:41,266] console                           [Info] [Upsource Error] [2016-01-08 11:21:41,203]  ERROR -                 bundle.startup - Error while starting JetBrains Upsource 2.5: Not allowed exit code -1 from process: bin/upsource-cluster-init start
[2016-01-08 11:21:41,266] console                           [Info] * Stopping Upsource Frontend
[2016-01-08 11:21:43,828] ServiceEventHandlerCollection    [Debug] Processing service event 4 with SERVICE_CONTROL_INTERROGATE
[2016-01-08 11:21:43,844] ServiceEventHandlerCollection    [Debug] Processing service event 4 with SERVICE_CONTROL_INTERROGATE
[2016-01-08 11:21:44,250] console                           [Info] upsource-frontend: Upsource Frontend is not running
[2016-01-08 11:21:44,250] console                           [Info] * Stopping Upsource Monitoring
[2016-01-08 11:21:46,766] console                           [Info] upsource-monitoring: Upsource Monitoring is not running
[2016-01-08 11:21:46,766] console                           [Info] * Stopping Upsource Analyzer
[2016-01-08 11:21:49,281] console                           [Info] upsource-analyzer: Upsource Analyzer is not running
[2016-01-08 11:21:49,281] console                           [Info] * Stopping Upsource Cluster Initialize Service
[2016-01-08 11:21:51,906] console                           [Info] upsource-cluster-init: Upsource Cluster Initialize Service is not running
[2016-01-08 11:21:51,906] console                           [Info] * Stopping Apache Cassandra
[2016-01-08 11:21:57,384] console                           [Info] cassandra: Apache Cassandra has shut down
[2016-01-08 11:21:57,384] console                           [Info] * Stopping Bundle Hub Configurator
[2016-01-08 11:21:57,384] console                           [Info] * Stopping Hub



Logs attached.

What am i doing wrong?


Attachment(s):
logs.zip
3 comments
Comment actions Permalink

When I start with the bat file
C:\Upsource\bin>upsource.bat start
Starting Upsource...
* JetBrains Upsource 2.5 is running in upgrade mode
* Configuring JetBrains Upsource 2.5
* Loading logging configuration from C:\Upsource\lib\ext\log4j.xml
* Redirecting JetBrains Upsource 2.5 logging to C:\Upsource\logs\internal\services\bundleProcess
* Configuring Service-Container[bundleProcess]
* Configuring Starting Page Service
* Configuring Upsource Configurator
* Configuring Hub
* Configuring Bundle Hub Configurator
* Configuring Apache Cassandra
* Configuring Upsource Cluster Initialize Service
* Configuring Upsource Analyzer
* Configuring Upsource Monitoring
* Configuring Upsource Frontend
* Starting Service-Container[bundleProcess]
* Starting Starting Page Service
* JetBrains Upsource 2.5 will be available on [http://at-upsource.int.rubicon-it.com:8080/bundle/starting] after start
* Starting Upsource Configurator
Upsource is running

It tells me that nothing went wrong, however, I still can not access the website, because it failed to load.

0
Comment actions Permalink

Hi Andrea,

Major/minor version upgrade is only possible through backup/restore procedure as described here -

https://upsource-support.jetbrains.com/hc/en-us/articles/207242085-How-to-upgrade-your-Upsource-installation-

Long story short, instead of copying data&conf folders from the root of Upsource.old directory, you have to copy data&conf folders from \Upsource.old\backups\<date_of_backup>\

Errors reporting as well as upgrade procedure will be improved in one of the nearest releases. Please upvote corresponding issue here - https://youtrack.jetbrains.com/issue/UP-5122

Sorry for that inconvinience.

0
Comment actions Permalink

Oh.. Thanks a million. :)

0

Please sign in to leave a comment.