cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjay Tripathi <sanjay.tripa...@citrix.com>
Subject RE: error upgrading from 4.02 to 4.1.1 on Centos 6.4 (similar to CLOUDSTACK-3459 on 4.2))
Date Tue, 27 Aug 2013 11:53:07 GMT
Marco,

Generally, duplicate column issue comes if you run the cloudstack-setup-management twice with
the management server failed to start in the first time due to schema issues.
Can you share the error details when you got this error for the first time, that would help
in identifying the actual problem.

--Sanjay

> -----Original Message-----
> From: marco ughetti [mailto:marco.ughetti@gmail.com]
> Sent: Tuesday, August 27, 2013 4:27 PM
> To: users@cloudstack.apache.org
> Subject: error upgrading from 4.02 to 4.1.1 on Centos 6.4 (similar to
> CLOUDSTACK-3459 on 4.2))
> 
> Hi all, I got this error during the upgrade from 4.02 to 4.1.1 on Centos 6.4
> 
> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:) Database
> upgrade must be performed from 4.0.2.20130420145617 to 4.1.1 ERROR
> [utils.db.ScriptRunner] (Timer-1:) Error executing: alter table vm_template
> add size bigint unsigned ERROR [utils.db.ScriptRunner] (Timer-1:)
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column name 'size'
> ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:) 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(DatabaseUpgradeC
> hecker.java:176)
>     at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeCh
> ecker.java:236)
>     at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChec
> ker.java:361)
>     at
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(Co
> mponentContext.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)
> ERROR [utils.component.ComponentContext] (Timer-1:) System integrity
> check failed. Refuse to startup
> 
> I've looked for an already opened bug on this topic but I have not found
> anything
> 
> Please, anyone can help me?
> 
> Thanks in advance
> 
> Marco

Mime
View raw message