You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Srikanteswararao Talluri (JIRA)" <ji...@apache.org> on 2013/04/30 20:56:15 UTC
[jira] [Reopened] (CLOUDSTACK-2201) Failed to start MS after fresh
installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srikanteswararao Talluri reopened CLOUDSTACK-2201:
--------------------------------------------------
It is failing here after fix
) Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-410to420.sql
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '165' for key 'PRIMARY'
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:176)
at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:236)
at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:361)
at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
2013-05-01 04:50:13,602 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back the transaction: Time = 293 Name = null; called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-DatabaseUpgradeChecker.upgrade:266-DatabaseUpgradeChecker.check:361-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:50-TimerThread.mainLoop:534-TimerThread.run:484
> Failed to start MS after fresh installation
> --------------------------------------------
>
> Key: CLOUDSTACK-2201
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2201
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Environment: CentOS 6.3 build
> Branch master
> Reporter: Rayees Namathponnan
> Assignee: Kishan Kavala
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2201.rar
>
>
> Step 1 :Install MS from master branch build
> Step 2 : execute
> cloudstack-setup-databases cloud:password@localhost --deploy-as=root:password
> cloudstack-setup-management
> Actual result
> Failed to management server, with below error in MS log
> 2013-04-25 22:01:06,030 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 4.0.0 Code Version = 4.2.0-SNAPSHOT
> 2013-04-25 22:01:06,030 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 4.0.0 to 4.2.0-SNAPSHOT
> 2013-04-25 22:01:06,030 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) The end upgrade version is actually at 4.1.0 but our management server code version is at 4.2.0-SNAPSHOT
> 2013-04-25 22:01:06,036 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup
> Is it happening due to below check-in ?
> Commit 099677a1244cd55fb98d3c40ee7881223dd9ac7c by chip.childers
> CLOUDSTACK-2172: adding database upgrade to 4.1.0 in PremiumDatabaseUpgradeChecker
> Add migration to 4.1.0 in the PremiumDatabaseUpgradeChecker, like in the
> DatabaseUpgradeChecker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira