Re: Unable to start Management server after upgrade from 4.11.2 to 4.11.3

2020-02-16 Thread Richard Lawley 
The error message suggests that the database hasn't been updated, so you
should be able to reinstall 4.11.2 and have it start working again. Then
you can add the system VM image before retrying the upgrade.

Regards,
Richard

On Sun, 16 Feb 2020, 16:08 Pratik Chandrakar, 
wrote:

> Hello,
> We have updated our servers from 4.11.2 to 4.11.3 but accidentally we were
> not able to add SystemVM template before doing so and at the same time
> mariadb server was updated to 10.3.22 from 10.3.10, but after update UI of
> cloudstack management server was not started. Please suggest
>
> Error log
>
> 2020-02-16 17:26:27,786 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: 4.11.3.0KVM SystemVm
> template not found. Cannot upgrade system Vms
> 2020-02-16 17:26:27,791 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> upgrade the database
> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.3.0KVM
> SystemVm template not found. Cannot upgrade system Vms
> 2020-02-16 17:45:16,325 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: 4.11.3.0KVM SystemVm
> template not found. Cannot upgrade system Vms
> 2020-02-16 17:45:16,329 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
> upgrade the database
> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.3.0KVM
> SystemVm template not found. Cannot upgrade system Vms
>
> --
> *Regards,*
> *Pratik *
>

Re: unable to start management server after update 4.11.3 -> 4.13

2019-09-29 Thread Andrija Panic 
Downgrade (simplified) is always as following (assuming an in-place upgrade
was done_:
- delete any resources that might be created with new/upgraded mgmt server
(i.e. if you successfully upgraded, restarted VRs etc or created any
VMs/volumes) - so that your external world (hypervisor/storage) corresponds
to the DB state BEFORE the upgrade.
- stop mgmt server, downgrade packages
- restore full DB from BEFORE the upgrade
- start downgraded mgmt server.

Since upgrade failed for you, skip step 1. and proceed with the downgrade
and DB restore

Andrija

On Sun, 29 Sep 2019 at 20:49, Jevgeni Zolotarjov 
wrote:

> Yes. I have made db backup.
> Whats the correct way to downgrade cloudstack management in centos7?
>
> On Sun, 29 Sep 2019, 20:06 Andrija Panic,  wrote:
>
> > Right... You have probably added  custom guest OS type to the guest_os
> > table before the upgrade, since I'm familiar this id 277 being a
> > "duplicate".
> >
> > Remove from the guest_os table any custom added entries, since 4.13 adds
> a
> > few guest OS types, with entries being created (in this guest_os table
> > specifically) with IDs 277 up to 304 or so.
> >
> > In order to upgrade again, you will need to first restore tthe 4.11.3 db
> > backup (you took right before the upgrade...), then delete from guest_os
> > table anything with ID>275 (275 being the last ID in 4.11.3) and start
> mgmt
> > (4.13) again.
> >
> > If you added  custom entries to other OS type related tables (i.e.
> > hypervisor_guest_os if I remember the name from top of my head...), you
> > might also want to remove those together with guest_os related entries...
> >
> > Ping here if any problems.
> >
> > Andrija
> >
> >
> > On Sun, 29 Sep 2019, 16:11 Jevgeni Zolotarjov, 
> > wrote:
> >
> > > I was running clean installation of 4.11.3
> > >
> > > Now after updating to 4.13 cloudstack-management does not start
> > >
> > > exception from management-server.log
> > > 2019-09-29 14:05:57,058 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> > > (main:null) (logid:) Exception encountered during context
> initialization
> > -
> > > cancelling refresh attempt:
> > > org.springframework.context.ApplicationContextException: Failed to
> start
> > > bean 'cloudStackLifeCycle'; nested exception is
> > > com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> > > database
> > > 2019-09-29 14:05:57,059 WARN  [o.e.j.w.WebAppContext] (main:null)
> > (logid:)
> > > Failed startup of context o.e.j.w.WebAppContext@646be2c3
> > >
> > >
> >
> {/client,file:///usr/share/cloudstack-management/webapp/,UNAVAILABLE}{/usr/share/cloudstack-management/webapp}
> > > org.springframework.context.ApplicationContextException: Failed to
> start
> > > bean 'cloudStackLifeCycle'; nested exception is
> > > com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> > > database
> > > at
> > >
> > >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:186)
> > > at
> > >
> > >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:52)
> > > at
> > >
> > >
> >
> org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:358)
> > > at
> > >
> > >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:159)
> > > at
> > >
> > >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123)
> > > at
> > >
> > >
> >
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:884)
> > > at
> > >
> > >
> >
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
> > > at
> > >
> > >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79)
> > > at
> > >
> > >
> >
>

Re: unable to start management server after update 4.11.3 -> 4.13

2019-09-29 Thread Jevgeni Zolotarjov 
Yes. I have made db backup.
Whats the correct way to downgrade cloudstack management in centos7?

On Sun, 29 Sep 2019, 20:06 Andrija Panic,  wrote:

> Right... You have probably added  custom guest OS type to the guest_os
> table before the upgrade, since I'm familiar this id 277 being a
> "duplicate".
>
> Remove from the guest_os table any custom added entries, since 4.13 adds a
> few guest OS types, with entries being created (in this guest_os table
> specifically) with IDs 277 up to 304 or so.
>
> In order to upgrade again, you will need to first restore tthe 4.11.3 db
> backup (you took right before the upgrade...), then delete from guest_os
> table anything with ID>275 (275 being the last ID in 4.11.3) and start mgmt
> (4.13) again.
>
> If you added  custom entries to other OS type related tables (i.e.
> hypervisor_guest_os if I remember the name from top of my head...), you
> might also want to remove those together with guest_os related entries...
>
> Ping here if any problems.
>
> Andrija
>
>
> On Sun, 29 Sep 2019, 16:11 Jevgeni Zolotarjov, 
> wrote:
>
> > I was running clean installation of 4.11.3
> >
> > Now after updating to 4.13 cloudstack-management does not start
> >
> > exception from management-server.log
> > 2019-09-29 14:05:57,058 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> > (main:null) (logid:) Exception encountered during context initialization
> -
> > cancelling refresh attempt:
> > org.springframework.context.ApplicationContextException: Failed to start
> > bean 'cloudStackLifeCycle'; nested exception is
> > com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> > database
> > 2019-09-29 14:05:57,059 WARN  [o.e.j.w.WebAppContext] (main:null)
> (logid:)
> > Failed startup of context o.e.j.w.WebAppContext@646be2c3
> >
> >
> {/client,file:///usr/share/cloudstack-management/webapp/,UNAVAILABLE}{/usr/share/cloudstack-management/webapp}
> > org.springframework.context.ApplicationContextException: Failed to start
> > bean 'cloudStackLifeCycle'; nested exception is
> > com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> > database
> > at
> >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:186)
> > at
> >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:52)
> > at
> >
> >
> org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:358)
> > at
> >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:159)
> > at
> >
> >
> org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123)
> > at
> >
> >
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:884)
> > at
> >
> >
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
> > at
> >
> >
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79)
> > at
> >
> >
> org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
> > at
> >
> >
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:71)
> > at
> >
> >
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:58)
> > at
> >
> >
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:62)
> > at
> >
> >
> org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
> > at
> >
> >
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:890)
> > at
> >
> >
>

Re: unable to start management server after update 4.11.3 -> 4.13

2019-09-29 Thread Andrija Panic 
Right... You have probably added  custom guest OS type to the guest_os
table before the upgrade, since I'm familiar this id 277 being a
"duplicate".

Remove from the guest_os table any custom added entries, since 4.13 adds a
few guest OS types, with entries being created (in this guest_os table
specifically) with IDs 277 up to 304 or so.

In order to upgrade again, you will need to first restore tthe 4.11.3 db
backup (you took right before the upgrade...), then delete from guest_os
table anything with ID>275 (275 being the last ID in 4.11.3) and start mgmt
(4.13) again.

If you added  custom entries to other OS type related tables (i.e.
hypervisor_guest_os if I remember the name from top of my head...), you
might also want to remove those together with guest_os related entries...

Ping here if any problems.

Andrija


On Sun, 29 Sep 2019, 16:11 Jevgeni Zolotarjov, 
wrote:

> I was running clean installation of 4.11.3
>
> Now after updating to 4.13 cloudstack-management does not start
>
> exception from management-server.log
> 2019-09-29 14:05:57,058 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
> 2019-09-29 14:05:57,059 WARN  [o.e.j.w.WebAppContext] (main:null) (logid:)
> Failed startup of context o.e.j.w.WebAppContext@646be2c3
>
> {/client,file:///usr/share/cloudstack-management/webapp/,UNAVAILABLE}{/usr/share/cloudstack-management/webapp}
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
> at
>
> org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:186)
> at
>
> org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:52)
> at
>
> org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:358)
> at
>
> org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:159)
> at
>
> org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123)
> at
>
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:884)
> at
>
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
> at
>
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79)
> at
>
> org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
> at
>
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:71)
> at
>
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:58)
> at
>
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:62)
> at
>
> org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
> at
>
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:890)
> at
>
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532)
> at
>
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:853)
> at
>
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1515)
> at
>
>

Re: Unable to start management

2016-11-11 Thread Abdul Qayyum Halid 
Thanks all, i just start to deploy with fresh installation and its work

On Fri, Nov 11, 2016 at 5:13 PM, Dag Sonstebo 
wrote:

> +1 for Sergey’s comment - schema-40to410.sql should not run in your
> scenario.
>
> A couple of other things in addition to Sergey’s request:
>
> - Can you send the output of “select * from cloud.version” from your DB.
> - Did you *restart the upgrade after it failed once*? In general if your
> upgrade fails on one of the SQL scripts you have to 1) restore the original
> database, 2) fix the DB issue / upgrade script issue and 3) restart the
> upgrade. In other words you can’t just restart the upgrade again. I have
> seen the “duplicate column” and similar duplication problems before – and
> they can be a result of the same SQL script running and trying the same
> upgrade steps again.
>
> Regards,
> Dag Sonstebo
>
> On 11/11/2016, 04:57, "Abdul Qayyum Halid"  wrote:
>
> i am upgrading from 4.6 to 4.9
>
> On Fri, Nov 11, 2016 at 10:41 AM, Sergey Levitskiy <
> sergey.levits...@autodesk.com> wrote:
>
> > What version are you upgrading from ?
> >
> >
> > On 11/10/16, 6:26 PM, "Abdul Qayyum Halid" 
> wrote:
> >
> > Hi, I am having problem to start CS management. The error show
> unable
> > to
> > upgrade databases. MySQL version 5.7, CS 4.9. Any solution?
> Below are
> > the
> > error.Thank you
> >
> > ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error
> executing:
> > alter
> > table vm_template add size bigint unsigned
> > 2016-11-11 10:18:53,229 ERROR [c.c.u.d.ScriptRunner] (main:null)
> > (logid:)
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Duplicate
> > column
> > name 'size'
> > 2016-11-11 10:18:53,229 ERROR [c.c.u.DatabaseUpgradeChecker]
> > (main:null)
> > (logid:) Unable to execute upgrade script:
> > /usr/share/cloudstack-management/setup/db/schema-40to410.sql
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Duplicate
> > column
> > name 'size'
> > 2016-11-11 10:18:53,233 WARN  [o.a.c.s.m.c.
> ResourceApplicationContext]
> > (main:null) (logid:) Exception encountered during context
> > initialization -
> > cancelling refresh attempt:
> > org.springframework.context.ApplicationContextException: Failed
> to
> > start
> > bean 'cloudStackLifeCycle'; nested exception is
> > com.cloud.utils.exception.CloudRuntimeException: Unable to
> upgrade the
> > database
> >
> >
> >
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: Unable to start management

2016-11-11 Thread Dag Sonstebo 
+1 for Sergey’s comment - schema-40to410.sql should not run in your scenario.

A couple of other things in addition to Sergey’s request:

- Can you send the output of “select * from cloud.version” from your DB.
- Did you *restart the upgrade after it failed once*? In general if your 
upgrade fails on one of the SQL scripts you have to 1) restore the original 
database, 2) fix the DB issue / upgrade script issue and 3) restart the 
upgrade. In other words you can’t just restart the upgrade again. I have seen 
the “duplicate column” and similar duplication problems before – and they can 
be a result of the same SQL script running and trying the same upgrade steps 
again.

Regards,
Dag Sonstebo

On 11/11/2016, 04:57, "Abdul Qayyum Halid"  wrote:

i am upgrading from 4.6 to 4.9

On Fri, Nov 11, 2016 at 10:41 AM, Sergey Levitskiy <
sergey.levits...@autodesk.com> wrote:

> What version are you upgrading from ?
>
>
> On 11/10/16, 6:26 PM, "Abdul Qayyum Halid"  wrote:
>
> Hi, I am having problem to start CS management. The error show unable
> to
> upgrade databases. MySQL version 5.7, CS 4.9. Any solution? Below are
> the
> error.Thank you
>
> ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error executing:
> alter
> table vm_template add size bigint unsigned
> 2016-11-11 10:18:53,229 ERROR [c.c.u.d.ScriptRunner] (main:null)
> (logid:)
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column
> name 'size'
> 2016-11-11 10:18:53,229 ERROR [c.c.u.DatabaseUpgradeChecker]
> (main:null)
> (logid:) Unable to execute upgrade script:
> /usr/share/cloudstack-management/setup/db/schema-40to410.sql
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column
> name 'size'
> 2016-11-11 10:18:53,233 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context
> initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to
> start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
>
>
>



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

Re: Unable to start management

2016-11-10 Thread Sergey Levitskiy 
Can you zip and post full management server log?
Can you run cloudstack-sccs and post the value reported?
Looks like upgrade procedure doesn’t correctly determine your version because 
schema-40to410.sql shouldn’t get executed during upgrade from 4.6 to 4.9

Re: Unable to start management

2016-11-10 Thread Abdul Qayyum Halid 
i am upgrading from 4.6 to 4.9

On Fri, Nov 11, 2016 at 10:41 AM, Sergey Levitskiy <
sergey.levits...@autodesk.com> wrote:

> What version are you upgrading from ?
>
>
> On 11/10/16, 6:26 PM, "Abdul Qayyum Halid"  wrote:
>
> Hi, I am having problem to start CS management. The error show unable
> to
> upgrade databases. MySQL version 5.7, CS 4.9. Any solution? Below are
> the
> error.Thank you
>
> ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error executing:
> alter
> table vm_template add size bigint unsigned
> 2016-11-11 10:18:53,229 ERROR [c.c.u.d.ScriptRunner] (main:null)
> (logid:)
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column
> name 'size'
> 2016-11-11 10:18:53,229 ERROR [c.c.u.DatabaseUpgradeChecker]
> (main:null)
> (logid:) Unable to execute upgrade script:
> /usr/share/cloudstack-management/setup/db/schema-40to410.sql
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column
> name 'size'
> 2016-11-11 10:18:53,233 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context
> initialization -
> cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to
> start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
>
>
>

Re: Unable to start management

2016-11-10 Thread Sergey Levitskiy 
What version are you upgrading from ?


On 11/10/16, 6:26 PM, "Abdul Qayyum Halid"  wrote:

Hi, I am having problem to start CS management. The error show unable to
upgrade databases. MySQL version 5.7, CS 4.9. Any solution? Below are the
error.Thank you

ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error executing: alter
table vm_template add size bigint unsigned
2016-11-11 10:18:53,229 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column
name 'size'
2016-11-11 10:18:53,229 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) Unable to execute upgrade script:
/usr/share/cloudstack-management/setup/db/schema-40to410.sql
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column
name 'size'
2016-11-11 10:18:53,233 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
(main:null) (logid:) Exception encountered during context initialization -
cancelling refresh attempt:
org.springframework.context.ApplicationContextException: Failed to start
bean 'cloudStackLifeCycle'; nested exception is
com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
database