Hi Rohit, 

many thanks for your reply! 

it was my error i was too hasty! After upgrade and starting the management 
server I not had waiting and restart the server after few minutes. 
When you upgarde you must wait! and look in the management-server.log till the 
database upgrade 4.0to4.1 is finished. this can take some minutes. 
I think it that the Web Interface are crashed and restart hasty the server. 
I reset the database to the previous dump and i try it again with positive 
result :-) 
now it works fine :-) 

Regards Andreas 



----- Ursprüngliche Mail -----

Von: "Rohit Yadav" <bhais...@apache.org> 
An: users@cloudstack.apache.org 
Gesendet: Freitag, 12. Juli 2013 20:35:22 
Betreff: Re: Error at upgrade from 4.0.2 to 4.1 

On Fri, Jul 12, 2013 at 5:23 PM, Andreas Huser <ahu...@7five-edv.de> wrote: 

> Hi at all, 
> I have an database issue with upgrade Cloudstack from 4.0.2 to 4.1. 
> The management Server running on rhel-6.4 
> 
> can someone help me? 
> 

Hi Andreas, 

>From the log looks like the 402 to 4.1.0 sql migration script does not 
check whether there were existing column in the db table. Looks like this 
upgrade case went unnoticed and surely it's a bug. If it was a production 
system you were trying to upgrade (even though it says it rolled back the 
transaction) I think a custom sql upgrade will have to be run which is ugly 
in most cases. 

Let's hear from our database ninjas on how to fix it. Can you please open a 
bug with the error log and other details on Apache CloudStack's JIRA? 

Cheers. 


> many thanks from germany 
> Regards Andreas 
> 
> 
> 2013-07-12 13:43:18,355 DEBUG [utils.db.ScriptRunner] (Timer-1:null) use 
> cloud 
> 2013-07-12 13:43:18,356 DEBUG [utils.db.ScriptRunner] (Timer-1:null) SET 
> foreign_key_checks = 0 
> 2013-07-12 13:43:18,356 DEBUG [utils.db.ScriptRunner] (Timer-1:null) alter 
> table vm_template add size bigint unsigned 
> 2013-07-12 13:43:18,359 ERROR [utils.db.ScriptRunner] (Timer-1:null) Error 
> executing: alter table vm_template add size bigint unsigned 
> 2013-07-12 13:43:18,360 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column 
> name 'size' 
> 2013-07-12 13:43:18,365 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:173)
>  
> at 
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:233)
>  
> at 
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:358)
>  
> 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-12 13:43:18,371 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
> Rolling back the transaction: Time = 39 Name = Upgrade; called by 
> -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-DatabaseUpgradeChecker.upgrade:263-DatabaseUpgradeChecker.check:358-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:50-TimerThread.mainLoop:534-TimerThread.run:484
>  
> 
> 
> 
> 
> 
> 
> Mit freundlichen Grüßen 
> 
> Andreas Huser 
> Geschäftsführer 
> System Engineer / Consultant 
> (Cisco Certified Solaris, Linux) 
> 
> --------------------------------------- 
> Zellerstraße 28 - 77654 Offenburg 
> Tel: +49(781) 1278689 0 
> Mobil: +49(176) 10308549 
> ahu...@7five-edv.de 
> 
> 
> 
> 
> 

Reply via email to