Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.11.1
-
Fix Version/s: 2.0
-
Component/s: None
-
Labels:None
-
Environment:Host: Linux 2.6.9-34.ELsmp
MySql db
-
Number of attachments :
Description
When upgrading from 1.8 to 1.11.1 the upgrade would fail. This was tracked down to users performing analysis while the upgrade was in progress.
The following steps were used as a workaround:
• Stop your old sonar
• Install your new sonar version
• Edit the sonar.properties file in order to listen to a new unused HTTP port (like 81 instead of 80)
• Start your new sonar version
• Browse http://yoursonar:81/ and launch the DB migration
• Once the migration is done, stop your new sonar version
• Edit the sonar.properties file on order to listen to your classical port (for instance 80)
• Start your sonar
We could imagine to add a new property (for instance sonar.automaticUpgradeAtStartup) in the sonar.properties file. The default value is 'false' and starting Sonar on an old version of the DB isn't possible (explicit error message must be displayed in the console). In that case, the property value must be set to 'true', and restarting Sonar will launch the migration phase before listening to the http port.