You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/07/11 06:47:48 UTC
[jira] [Updated] (CLOUDSTACK-3459) [Automation] Failed to start
management server in 4.2 fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rayees Namathponnan updated CLOUDSTACK-3459:
--------------------------------------------
Attachment: CLOUDSTACK-3459.rar
> [Automation] Failed to start management server in 4.2 fresh installation
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3459
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3459
> 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: 4.2
> Reporter: Rayees Namathponnan
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3459.rar
>
>
> Create RPM build from 4.2 branch, and install then run setup scripst
> Result
> Management server failed to start with below error
> 2013-07-11 00:28:50,831 ERROR [utils.db.ScriptRunner] (Timer-1:null) com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'size'
> 2013-07-11 00:28:50,835 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:174)
> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:235)
> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
> 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-07-11 00:28:50,843 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-40to410.sql
> at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:183)
> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:235)
> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
> 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)
> Caused by: 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:174)
> ... 6 more
> 2013-07-11 00:28:50,856 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back the transaction: Time = 61 Name = null; called by -Transaction.rollback:890-Transaction.removeUpTo:833
> -Transaction.close:657-DatabaseUpgradeChecker.upgrade:268-DatabaseUpgradeChecker.check:364-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:50-TimerThread.mainLoop:534-T
> imerThread.run:484
> 2013-07-11 00:28:50,857 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup
--
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