You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by marco ughetti <ma...@gmail.com> on 2013/08/27 12:57:28 UTC
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(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)
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
Re: error upgrading from 4.02 to 4.1.1 on Centos 6.4 (similar to
CLOUDSTACK-3459 on 4.2))
Posted by marco ughetti <ma...@gmail.com>.
Ok. I solved the issue restarting the server after having restored the
original 4.0.2 database
It seems to work well but I have a question left
Is it correct that the file componentContext.xml can be found in
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes instead of
/etc/cloudstack/management
Now in /etc/cloudstack/management I have only 24 files while in 4.0.2 they
were 38
Someone can confirm that this is not a problem?
Thanks
On Tue, Aug 27, 2013 at 3:11 PM, marco ughetti <ma...@gmail.com>wrote:
> Thanks for the reply.
> I have just upgraded a working instance if cloudstack 4.02. Actually I
> have cloned the vm where cloudstack is running to be safe
> After having upgraded the cloudstack packages in the new vm and in one of
> my kvm hosts in order to try thr new release I got the error during the
> first run of the manager
> Well, to be honest the first time I forgot to change the ip address of the
> manager in db.properties and the server did not start but it was also not
> able to do anyrhing with the database, I guess.
> Anyway I attach the relevant logs, hoping it will be useful
>
> Marco
>
>
>
>
> On Tue, Aug 27, 2013 at 1:53 PM, Sanjay Tripathi <
> sanjay.tripathi@citrix.com> wrote:
>
>> 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
>>
>
>
Re: error upgrading from 4.02 to 4.1.1 on Centos 6.4 (similar to
CLOUDSTACK-3459 on 4.2))
Posted by marco ughetti <ma...@gmail.com>.
Thanks for the reply.
I have just upgraded a working instance if cloudstack 4.02. Actually I have
cloned the vm where cloudstack is running to be safe
After having upgraded the cloudstack packages in the new vm and in one of
my kvm hosts in order to try thr new release I got the error during the
first run of the manager
Well, to be honest the first time I forgot to change the ip address of the
manager in db.properties and the server did not start but it was also not
able to do anyrhing with the database, I guess.
Anyway I attach the relevant logs, hoping it will be useful
Marco
On Tue, Aug 27, 2013 at 1:53 PM, Sanjay Tripathi <sanjay.tripathi@citrix.com
> wrote:
> 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
>
RE: error upgrading from 4.02 to 4.1.1 on Centos 6.4 (similar to
CLOUDSTACK-3459 on 4.2))
Posted by Sanjay Tripathi <sa...@citrix.com>.
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
Re: error upgrading from 4.02 to 4.1.1 on Centos 6.4 (similar to
CLOUDSTACK-3459 on 4.2))
Posted by Venkata SwamyBabu Budumuru <ve...@citrix.com>.
Is this something related to
https://issues.apache.org/jira/browse/CLOUDSTACK-3459
On 27/08/13 4:27 PM, "marco ughetti" <ma...@gmail.com> wrote:
>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(DatabaseUpgradeChecker.
>java:176)
> at
>com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.ja
>va:236)
> at
>com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java
>:361)
> at
>com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(Compone
>ntContext.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