[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646742#comment-13646742 ] Prachi Damle commented on CLOUDSTACK-2201: -- 'Duplicate entry' error indicates that you are not running the upgrade on a clean 4.0 database. After the fix, please make sure you do everything from scratch (db should be dropped and recreated) - Step 1 :Install MS from master branch build Step 2 : execute cloudstack-setup-databases cloud:password@localhost --deploy-as=root:password cloudstack-setup-management > 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
[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645855#comment-13645855 ] Rayees Namathponnan commented on CLOUDSTACK-2201: - I got below error in MS log 2013-04-30 12:12:17,868 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 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-04-30 12:12:17,870 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back the transaction: Time = 396 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
[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645840#comment-13645840 ] Srikanteswararao Talluri commented on CLOUDSTACK-2201: -- com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'size' 2013-05-01 05:05:37,930 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-40to410.sql com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'size' 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) > 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
[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645520#comment-13645520 ] ASF subversion and git services commented on CLOUDSTACK-2201: - Commit 34885f63569d64aea0c3df90af6af31b881d0e5b in branch refs/heads/master from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=34885f6 ] CLOUDSTACK-2201: Use DatabaseUpgradeChecker instead of premiumin nonossComponents.xml. Premium checker should be removed altogether > 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
[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644374#comment-13644374 ] Srikanteswararao Talluri commented on CLOUDSTACK-2201: -- Is some one looking at this? > 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 >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
[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642698#comment-13642698 ] Nicolas Lamirault commented on CLOUDSTACK-2201: --- According to this file : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=server/src/com/cloud/upgrade/PremiumDatabaseUpgradeChecker.java;h=bad32536955239d8bc7394e4d78e8184c5d4997b;hb=HEAD new Upgrade410to420() for each database migration are missing. > 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 >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
