Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
ood to hear Jevgeni, good floating.. On Fri, Feb 9, 2018 at 5:42 PM, Jevgeni Zolotarjov <j.zolotar...@gmail.com> wrote: > To finalize, IPs recovered too. I think I started my VMs too early before > router was up. > > Now its all fine. > > On Fri, Feb 9, 2018 at 6:36 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > No problem, I'm pleased that you're sorted. > > > > > > Kind regards, > > > > Paul Angus > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > -Original Message- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 16:34 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > destroyed virtual router > > > > it got recreated. > > On NOW. My VMs start!!! > > > > All IPs got changed, but I can manage with that. > > > > Thank you for your support > > > > On Fri, Feb 9, 2018 at 6:21 PM, Paul Angus <paul.an...@shapeblue.com> > > wrote: > > > > > Have you done the same for the virtual routers? > > > > > > I'll look at your log in the meantime > > > > > > > > > Kind regards, > > > > > > Paul Angus > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > Sent: 09 February 2018 16:19 > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > > 4.11 > > > > > > I destroyed system VMs and they got recreated automatically. > > > They are running. I can verify that by > > > virsh list --all > > > > > > and > > > I can see their console and it sugests that it is Cloudstack 4.11 > > systemVM > > > > > > BUT > > > it didn't solve the problem. None of my own VM is listed by "virsh list > > > -all". They do not start. > > > I tried to create new VM, it does not start either, due to to the same > > > problem - insufficient capacity > > > > > > On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com > > > > > wrote: > > > > > > > listen to Paul, not to me. > > > > He's an operator i'm just impatient > > > > > > > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com > > > > > > wrote: > > > > > > > > > After upgrading the code of the mgmt. server you need upgrade your > > > > > system VMs from the old template to ones using the new templates. > > > > > > > > > > This needs to be done for the SSVM, CPVM and all of your virtual > > > routers. > > > > > > > > > > For the SSVM & CPVM you do this by destroying them and CloudStack > > > > > will recreate them with the new template. > > > > > For the virtual routers, you can go to each of them in turn in the > > > > > UI and there will be a upgrade router button. > > > > > > > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > > > www.shapeblue.com > > > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > > > > > > > > > > > -Original Message- > > > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > > > Sent: 09 February 2018 15:55 > > > > > To: users@cloudstack.apache.org > > > > > Subject: Re: cloudstack-management fails to start after upgrade > 4.10 > > -> > > > > > 4.11 > > > > > > > > > > Destroyed VMs? No. Definitely not. > > > > > > > > > > At least I can see them all under web console Home->Instances. Can > > make > > > > > snapshots even > > > > > > > > &g
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
To finalize, IPs recovered too. I think I started my VMs too early before router was up. Now its all fine. On Fri, Feb 9, 2018 at 6:36 PM, Paul Angus <paul.an...@shapeblue.com> wrote: > No problem, I'm pleased that you're sorted. > > > Kind regards, > > Paul Angus > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > Sent: 09 February 2018 16:34 > To: users@cloudstack.apache.org > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > destroyed virtual router > > it got recreated. > On NOW. My VMs start!!! > > All IPs got changed, but I can manage with that. > > Thank you for your support > > On Fri, Feb 9, 2018 at 6:21 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > Have you done the same for the virtual routers? > > > > I'll look at your log in the meantime > > > > > > Kind regards, > > > > Paul Angus > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > -Original Message- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 16:19 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > I destroyed system VMs and they got recreated automatically. > > They are running. I can verify that by > > virsh list --all > > > > and > > I can see their console and it sugests that it is Cloudstack 4.11 > systemVM > > > > BUT > > it didn't solve the problem. None of my own VM is listed by "virsh list > > -all". They do not start. > > I tried to create new VM, it does not start either, due to to the same > > problem - insufficient capacity > > > > On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > listen to Paul, not to me. > > > He's an operator i'm just impatient > > > > > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> > > > wrote: > > > > > > > After upgrading the code of the mgmt. server you need upgrade your > > > > system VMs from the old template to ones using the new templates. > > > > > > > > This needs to be done for the SSVM, CPVM and all of your virtual > > routers. > > > > > > > > For the SSVM & CPVM you do this by destroying them and CloudStack > > > > will recreate them with the new template. > > > > For the virtual routers, you can go to each of them in turn in the > > > > UI and there will be a upgrade router button. > > > > > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > > www.shapeblue.com > > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > > > > > > -Original Message- > > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > > Sent: 09 February 2018 15:55 > > > > To: users@cloudstack.apache.org > > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 > -> > > > > 4.11 > > > > > > > > Destroyed VMs? No. Definitely not. > > > > > > > > At least I can see them all under web console Home->Instances. Can > make > > > > snapshots even > > > > > > > > My todays management server log https://www.sendspace.com/ > file/nxxgg0 > > > > > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com > > > > > > wrote: > > > > > > > > > Hi Jevgeni, > > > > > > > > > > Can I take you off at a slight tangent... > > > > > > > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > > > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > > > > DeploymentPlanner cannot allocate the VM, returning. > > > > > > > > > > Have you destroyed yo
RE: cloudstack-management fails to start after upgrade 4.10 -> 4.11
No problem, I'm pleased that you're sorted. Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] Sent: 09 February 2018 16:34 To: users@cloudstack.apache.org Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11 destroyed virtual router it got recreated. On NOW. My VMs start!!! All IPs got changed, but I can manage with that. Thank you for your support On Fri, Feb 9, 2018 at 6:21 PM, Paul Angus <paul.an...@shapeblue.com> wrote: > Have you done the same for the virtual routers? > > I'll look at your log in the meantime > > > Kind regards, > > Paul Angus > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > Sent: 09 February 2018 16:19 > To: users@cloudstack.apache.org > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > I destroyed system VMs and they got recreated automatically. > They are running. I can verify that by > virsh list --all > > and > I can see their console and it sugests that it is Cloudstack 4.11 systemVM > > BUT > it didn't solve the problem. None of my own VM is listed by "virsh list > -all". They do not start. > I tried to create new VM, it does not start either, due to to the same > problem - insufficient capacity > > On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > listen to Paul, not to me. > > He's an operator i'm just impatient > > > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> > > wrote: > > > > > After upgrading the code of the mgmt. server you need upgrade your > > > system VMs from the old template to ones using the new templates. > > > > > > This needs to be done for the SSVM, CPVM and all of your virtual > routers. > > > > > > For the SSVM & CPVM you do this by destroying them and CloudStack > > > will recreate them with the new template. > > > For the virtual routers, you can go to each of them in turn in the > > > UI and there will be a upgrade router button. > > > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > Sent: 09 February 2018 15:55 > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > > 4.11 > > > > > > Destroyed VMs? No. Definitely not. > > > > > > At least I can see them all under web console Home->Instances. Can make > > > snapshots even > > > > > > My todays management server log https://www.sendspace.com/file/nxxgg0 > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> > > > wrote: > > > > > > > Hi Jevgeni, > > > > > > > > Can I take you off at a slight tangent... > > > > > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > > > DeploymentPlanner cannot allocate the VM, returning. > > > > > > > > Have you destroyed your system vms so that new 4.11 system vms have > > > > been deployed? > > > > > > > > It may help us if you can paste all of your management log from today > > > > into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > > www.shapeblue.com > > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > > > > > > -Original Message- > > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > &g
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
destroyed virtual router it got recreated. On NOW. My VMs start!!! All IPs got changed, but I can manage with that. Thank you for your support On Fri, Feb 9, 2018 at 6:21 PM, Paul Angus <paul.an...@shapeblue.com> wrote: > Have you done the same for the virtual routers? > > I'll look at your log in the meantime > > > Kind regards, > > Paul Angus > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > Sent: 09 February 2018 16:19 > To: users@cloudstack.apache.org > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > I destroyed system VMs and they got recreated automatically. > They are running. I can verify that by > virsh list --all > > and > I can see their console and it sugests that it is Cloudstack 4.11 systemVM > > BUT > it didn't solve the problem. None of my own VM is listed by "virsh list > -all". They do not start. > I tried to create new VM, it does not start either, due to to the same > problem - insufficient capacity > > On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > listen to Paul, not to me. > > He's an operator i'm just impatient > > > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> > > wrote: > > > > > After upgrading the code of the mgmt. server you need upgrade your > > > system VMs from the old template to ones using the new templates. > > > > > > This needs to be done for the SSVM, CPVM and all of your virtual > routers. > > > > > > For the SSVM & CPVM you do this by destroying them and CloudStack > > > will recreate them with the new template. > > > For the virtual routers, you can go to each of them in turn in the > > > UI and there will be a upgrade router button. > > > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > Sent: 09 February 2018 15:55 > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > > 4.11 > > > > > > Destroyed VMs? No. Definitely not. > > > > > > At least I can see them all under web console Home->Instances. Can make > > > snapshots even > > > > > > My todays management server log https://www.sendspace.com/file/nxxgg0 > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> > > > wrote: > > > > > > > Hi Jevgeni, > > > > > > > > Can I take you off at a slight tangent... > > > > > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > > > DeploymentPlanner cannot allocate the VM, returning. > > > > > > > > Have you destroyed your system vms so that new 4.11 system vms have > > > > been deployed? > > > > > > > > It may help us if you can paste all of your management log from today > > > > into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > > www.shapeblue.com > > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > > > > > > -Original Message- > > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > > Sent: 09 February 2018 15:31 > > > > To: users@cloudstack.apache.org > > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 > -> > > > > 4.11 > > > > > > > > the same result > > > > > > > > [root@mtl1-apphst03 management]# virsh list --all > > > > IdName
RE: cloudstack-management fails to start after upgrade 4.10 -> 4.11
I'm a little confused about what’s working at what isn't, but... 2018-02-09 12:49:16,657 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-10:ctx-a7c0188f job-581/job-793 ctx-babd6f7e) (logid:3bc0581f) The last host of this VM is not UP or is not enabled, host status is: Disconnected, host resource state is: Enabled Your host is disconnected. Did you yum update cloudstack-agent on the kvm host? If you did, can you paste the cloudstack-agent log for us to see? Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Paul Angus [mailto:paul.an...@shapeblue.com] Sent: 09 February 2018 16:21 To: users@cloudstack.apache.org Subject: RE: cloudstack-management fails to start after upgrade 4.10 -> 4.11 Have you done the same for the virtual routers? I'll look at your log in the meantime Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] Sent: 09 February 2018 16:19 To: users@cloudstack.apache.org Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11 I destroyed system VMs and they got recreated automatically. They are running. I can verify that by virsh list --all and I can see their console and it sugests that it is Cloudstack 4.11 systemVM BUT it didn't solve the problem. None of my own VM is listed by "virsh list -all". They do not start. I tried to create new VM, it does not start either, due to to the same problem - insufficient capacity On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > listen to Paul, not to me. > He's an operator i'm just impatient > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > After upgrading the code of the mgmt. server you need upgrade your > > system VMs from the old template to ones using the new templates. > > > > This needs to be done for the SSVM, CPVM and all of your virtual routers. > > > > For the SSVM & CPVM you do this by destroying them and CloudStack > > will recreate them with the new template. > > For the virtual routers, you can go to each of them in turn in the > > UI and there will be a upgrade router button. > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > -Original Message----- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 15:55 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 > > -> > > 4.11 > > > > Destroyed VMs? No. Definitely not. > > > > At least I can see them all under web console Home->Instances. Can > > make snapshots even > > > > My todays management server log > > https://www.sendspace.com/file/nxxgg0 > > > > > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus > > <paul.an...@shapeblue.com> > > wrote: > > > > > Hi Jevgeni, > > > > > > Can I take you off at a slight tangent... > > > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > > DeploymentPlanner cannot allocate the VM, returning. > > > > > > Have you destroyed your system vms so that new 4.11 system vms > > > have been deployed? > > > > > > It may help us if you can paste all of your management log from > > > today into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > Sent: 09 February 2018 15:31 > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade > > > 4.10 -> > > > 4.11 > > > > > > the same result > > > > > > [root@mtl1-app
RE: cloudstack-management fails to start after upgrade 4.10 -> 4.11
Have you done the same for the virtual routers? I'll look at your log in the meantime Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] Sent: 09 February 2018 16:19 To: users@cloudstack.apache.org Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11 I destroyed system VMs and they got recreated automatically. They are running. I can verify that by virsh list --all and I can see their console and it sugests that it is Cloudstack 4.11 systemVM BUT it didn't solve the problem. None of my own VM is listed by "virsh list -all". They do not start. I tried to create new VM, it does not start either, due to to the same problem - insufficient capacity On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > listen to Paul, not to me. > He's an operator i'm just impatient > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > After upgrading the code of the mgmt. server you need upgrade your > > system VMs from the old template to ones using the new templates. > > > > This needs to be done for the SSVM, CPVM and all of your virtual routers. > > > > For the SSVM & CPVM you do this by destroying them and CloudStack > > will recreate them with the new template. > > For the virtual routers, you can go to each of them in turn in the > > UI and there will be a upgrade router button. > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > -Original Message- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 15:55 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > Destroyed VMs? No. Definitely not. > > > > At least I can see them all under web console Home->Instances. Can make > > snapshots even > > > > My todays management server log https://www.sendspace.com/file/nxxgg0 > > > > > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> > > wrote: > > > > > Hi Jevgeni, > > > > > > Can I take you off at a slight tangent... > > > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > > DeploymentPlanner cannot allocate the VM, returning. > > > > > > Have you destroyed your system vms so that new 4.11 system vms have > > > been deployed? > > > > > > It may help us if you can paste all of your management log from today > > > into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > Sent: 09 February 2018 15:31 > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > > 4.11 > > > > > > the same result > > > > > > [root@mtl1-apphst03 management]# virsh list --all > > > IdName State > > > > > > 1 v-1-VM running > > > 2 s-2-VM running > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com > > > > > wrote: > > > > > > > so try > > > > # virsh list --all > > > > > > > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > > > > <j.zolotar...@gmail.com > > > > > > > > > wrote: > > > > > > > > > I guess, these are system VMs. > > > > > none of my own created instances can start. > > > > > IdName
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
I destroyed system VMs and they got recreated automatically. They are running. I can verify that by virsh list --all and I can see their console and it sugests that it is Cloudstack 4.11 systemVM BUT it didn't solve the problem. None of my own VM is listed by "virsh list -all". They do not start. I tried to create new VM, it does not start either, due to to the same problem - insufficient capacity On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > listen to Paul, not to me. > He's an operator i'm just impatient > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > After upgrading the code of the mgmt. server you need upgrade your system > > VMs from the old template to ones using the new templates. > > > > This needs to be done for the SSVM, CPVM and all of your virtual routers. > > > > For the SSVM & CPVM you do this by destroying them and CloudStack will > > recreate them with the new template. > > For the virtual routers, you can go to each of them in turn in the UI and > > there will be a upgrade router button. > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > -Original Message----- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 15:55 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > Destroyed VMs? No. Definitely not. > > > > At least I can see them all under web console Home->Instances. Can make > > snapshots even > > > > My todays management server log https://www.sendspace.com/file/nxxgg0 > > > > > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> > > wrote: > > > > > Hi Jevgeni, > > > > > > Can I take you off at a slight tangent... > > > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > > DeploymentPlanner cannot allocate the VM, returning. > > > > > > Have you destroyed your system vms so that new 4.11 system vms have > > > been deployed? > > > > > > It may help us if you can paste all of your management log from today > > > into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > > Sent: 09 February 2018 15:31 > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > > 4.11 > > > > > > the same result > > > > > > [root@mtl1-apphst03 management]# virsh list --all > > > IdName State > > > > > > 1 v-1-VM running > > > 2 s-2-VM running > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com > > > > > wrote: > > > > > > > so try > > > > # virsh list --all > > > > > > > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > > > > <j.zolotar...@gmail.com > > > > > > > > > wrote: > > > > > > > > > I guess, these are system VMs. > > > > > none of my own created instances can start. > > > > > IdName State > > > > > > > > > > 1 v-1-VM running > > > > > 2 s-2-VM running > > > > > > > > > > virsh start 3> gives error > > > > > error: failed to get domain '8' > > > > > error: Domain not found: no domain with matching name '8' >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
listen to Paul, not to me. He's an operator i'm just impatient On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus <paul.an...@shapeblue.com> wrote: > After upgrading the code of the mgmt. server you need upgrade your system > VMs from the old template to ones using the new templates. > > This needs to be done for the SSVM, CPVM and all of your virtual routers. > > For the SSVM & CPVM you do this by destroying them and CloudStack will > recreate them with the new template. > For the virtual routers, you can go to each of them in turn in the UI and > there will be a upgrade router button. > > You get to these through the infrastructure tab in the UI. > > > > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > Sent: 09 February 2018 15:55 > To: users@cloudstack.apache.org > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > Destroyed VMs? No. Definitely not. > > At least I can see them all under web console Home->Instances. Can make > snapshots even > > My todays management server log https://www.sendspace.com/file/nxxgg0 > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > Hi Jevgeni, > > > > Can I take you off at a slight tangent... > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > DeploymentPlanner cannot allocate the VM, returning. > > > > Have you destroyed your system vms so that new 4.11 system vms have > > been deployed? > > > > It may help us if you can paste all of your management log from today > > into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > > > > > > -Original Message- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 15:31 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > the same result > > > > [root@mtl1-apphst03 management]# virsh list --all > > IdName State > > > > 1 v-1-VM running > > 2 s-2-VM running > > > > > > > > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > so try > > > # virsh list --all > > > > > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > > > <j.zolotar...@gmail.com > > > > > > > wrote: > > > > > > > I guess, these are system VMs. > > > > none of my own created instances can start. > > > > IdName State > > > > > > > > 1 v-1-VM running > > > > 2 s-2-VM running > > > > > > > > virsh start 3> gives error > > > > error: failed to get domain '8' > > > > error: Domain not found: no domain with matching name '8' > > > > > > > > > > > > And yes, cloudstack and mysql - everything locally > > > > > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland > > > > <daan.hoogl...@gmail.com> > > > > wrote: > > > > > > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < > > > > j.zolotar...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > * how to start instance with virsh? > > > > > > > > > > > ah, usually something like > > > > > # virsh start > > > > > or > > > > > # virsh start <number> > > > > > > > > > > > > > > > > * starting in debugger? I would rather not do it :) > > > > > > > > > > > ok, i expected as much. It will slow our solution process > > > unfortunately >
RE: cloudstack-management fails to start after upgrade 4.10 -> 4.11
After upgrading the code of the mgmt. server you need upgrade your system VMs from the old template to ones using the new templates. This needs to be done for the SSVM, CPVM and all of your virtual routers. For the SSVM & CPVM you do this by destroying them and CloudStack will recreate them with the new template. For the virtual routers, you can go to each of them in turn in the UI and there will be a upgrade router button. You get to these through the infrastructure tab in the UI. paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] Sent: 09 February 2018 15:55 To: users@cloudstack.apache.org Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11 Destroyed VMs? No. Definitely not. At least I can see them all under web console Home->Instances. Can make snapshots even My todays management server log https://www.sendspace.com/file/nxxgg0 On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> wrote: > Hi Jevgeni, > > Can I take you off at a slight tangent... > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > DeploymentPlanner cannot allocate the VM, returning. > > Have you destroyed your system vms so that new 4.11 system vms have > been deployed? > > It may help us if you can paste all of your management log from today > into https://pastebin.com (or similar) to share with us. > > > > > > > > > > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > Sent: 09 February 2018 15:31 > To: users@cloudstack.apache.org > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > the same result > > [root@mtl1-apphst03 management]# virsh list --all > IdName State > > 1 v-1-VM running > 2 s-2-VM running > > > > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > so try > > # virsh list --all > > > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > > <j.zolotar...@gmail.com > > > > > wrote: > > > > > I guess, these are system VMs. > > > none of my own created instances can start. > > > IdName State > > > > > > 1 v-1-VM running > > > 2 s-2-VM running > > > > > > virsh start 3> gives error > > > error: failed to get domain '8' > > > error: Domain not found: no domain with matching name '8' > > > > > > > > > And yes, cloudstack and mysql - everything locally > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland > > > <daan.hoogl...@gmail.com> > > > wrote: > > > > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < > > > j.zolotar...@gmail.com > > > > > > > > > wrote: > > > > > > > > > * how to start instance with virsh? > > > > > > > > > ah, usually something like > > > > # virsh start > > > > or > > > > # virsh start <number> > > > > > > > > > > > > > * starting in debugger? I would rather not do it :) > > > > > > > > > ok, i expected as much. It will slow our solution process > > unfortunately > > > > > > > > > > > > In the below at the bottom it says you have two VMs and both are > > > running. > > > > Is that correct? > > > > > > > > > > > > > * this is the log around GetHostStatsAnswer > > > > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) > > > > > HostStatsCollector > > is > > > > > running... > > > > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] > > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq > > > > 3-613896924205940798: > > > > > Received: { Ans: , MgmtId: 264216221068220,
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
or better through cloudstack On Fri, Feb 9, 2018 at 4:59 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > Jevgeni, > > What Paul means is: Those two VMs are probably the old ones base on the > 4.10 systemvm template. These need to be upgraded before you can deploy > anything. The way to do that is to destroy them and let cloudstack recreate > them. They won't allow you to instantiate anything anyway. > > so destroy > v-1-VM and > s-2-VM > > for instance with virsh > > On Fri, Feb 9, 2018 at 4:54 PM, Jevgeni Zolotarjov <j.zolotar...@gmail.com > > wrote: > >> Destroyed VMs? No. Definitely not. >> >> At least I can see them all under web console Home->Instances. Can make >> snapshots even >> >> My todays management server log https://www.sendspace.com/file/nxxgg0 >> >> >> >> On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> >> wrote: >> >> > Hi Jevgeni, >> > >> > Can I take you off at a slight tangent... >> > >> > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) >> > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, >> > DeploymentPlanner cannot allocate the VM, returning. >> > >> > Have you destroyed your system vms so that new 4.11 system vms have been >> > deployed? >> > >> > It may help us if you can paste all of your management log from today >> into >> > https://pastebin.com (or similar) to share with us. >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > paul.an...@shapeblue.com >> > www.shapeblue.com >> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK >> > @shapeblue >> > >> > >> > >> > >> > -Original Message- >> > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] >> > Sent: 09 February 2018 15:31 >> > To: users@cloudstack.apache.org >> > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> >> > 4.11 >> > >> > the same result >> > >> > [root@mtl1-apphst03 management]# virsh list --all >> > IdName State >> > >> > 1 v-1-VM running >> > 2 s-2-VM running >> > >> > >> > >> > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com> >> > wrote: >> > >> > > so try >> > > # virsh list --all >> > > >> > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov >> > > <j.zolotar...@gmail.com >> > > > >> > > wrote: >> > > >> > > > I guess, these are system VMs. >> > > > none of my own created instances can start. >> > > > IdName State >> > > > >> > > > 1 v-1-VM running >> > > > 2 s-2-VM running >> > > > >> > > > virsh start 3> gives error >> > > > error: failed to get domain '8' >> > > > error: Domain not found: no domain with matching name '8' >> > > > >> > > > >> > > > And yes, cloudstack and mysql - everything locally >> > > > >> > > > >> > > > >> > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland >> > > > <daan.hoogl...@gmail.com> >> > > > wrote: >> > > > >> > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < >> > > > j.zolotar...@gmail.com >> > > > > > >> > > > > wrote: >> > > > > >> > > > > > * how to start instance with virsh? >> > > > > > >> > > > > ah, usually something like >> > > > > # virsh start >> > > > > or >> > > > > # virsh start <number> >> > > > > >> > > > > >> > > > > > * starting in debugger? I would rather not do it :) >> > > > > > >> > > > > ok, i expected as much. It will slow our solution process >> > > unfortunately >> > > > > >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
Jevgeni, What Paul means is: Those two VMs are probably the old ones base on the 4.10 systemvm template. These need to be upgraded before you can deploy anything. The way to do that is to destroy them and let cloudstack recreate them. They won't allow you to instantiate anything anyway. so destroy v-1-VM and s-2-VM for instance with virsh On Fri, Feb 9, 2018 at 4:54 PM, Jevgeni Zolotarjov <j.zolotar...@gmail.com> wrote: > Destroyed VMs? No. Definitely not. > > At least I can see them all under web console Home->Instances. Can make > snapshots even > > My todays management server log https://www.sendspace.com/file/nxxgg0 > > > > On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > Hi Jevgeni, > > > > Can I take you off at a slight tangent... > > > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set, > > DeploymentPlanner cannot allocate the VM, returning. > > > > Have you destroyed your system vms so that new 4.11 system vms have been > > deployed? > > > > It may help us if you can paste all of your management log from today > into > > https://pastebin.com (or similar) to share with us. > > > > > > > > > > > > > > > > > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > -Original Message- > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > > Sent: 09 February 2018 15:31 > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > the same result > > > > [root@mtl1-apphst03 management]# virsh list --all > > IdName State > > > > 1 v-1-VM running > > 2 s-2-VM running > > > > > > > > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > so try > > > # virsh list --all > > > > > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > > > <j.zolotar...@gmail.com > > > > > > > wrote: > > > > > > > I guess, these are system VMs. > > > > none of my own created instances can start. > > > > IdName State > > > > > > > > 1 v-1-VM running > > > > 2 s-2-VM running > > > > > > > > virsh start 3> gives error > > > > error: failed to get domain '8' > > > > error: Domain not found: no domain with matching name '8' > > > > > > > > > > > > And yes, cloudstack and mysql - everything locally > > > > > > > > > > > > > > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland > > > > <daan.hoogl...@gmail.com> > > > > wrote: > > > > > > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < > > > > j.zolotar...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > * how to start instance with virsh? > > > > > > > > > > > ah, usually something like > > > > > # virsh start > > > > > or > > > > > # virsh start <number> > > > > > > > > > > > > > > > > * starting in debugger? I would rather not do it :) > > > > > > > > > > > ok, i expected as much. It will slow our solution process > > > unfortunately > > > > > > > > > > > > > > > In the below at the bottom it says you have two VMs and both are > > > > running. > > > > > Is that correct? > > > > > > > > > > > > > > > > * this is the log around GetHostStatsAnswer > > > > > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > > > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) > > > > > > HostStatsCollector > > > is > > > > > > running... > > > > > > 2018-02-09 14:05:30,322 DEBUG [c.c.
RE: cloudstack-management fails to start after upgrade 4.10 -> 4.11
Hi Jevgeni, Can I take you off at a slight tangent... (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) (logid:0afb959d) DataCenter id = '1' provided is in avoid set, DeploymentPlanner cannot allocate the VM, returning. Have you destroyed your system vms so that new 4.11 system vms have been deployed? It may help us if you can paste all of your management log from today into https://pastebin.com (or similar) to share with us. paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] Sent: 09 February 2018 15:31 To: users@cloudstack.apache.org Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11 the same result [root@mtl1-apphst03 management]# virsh list --all IdName State 1 v-1-VM running 2 s-2-VM running On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > so try > # virsh list --all > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > <j.zolotar...@gmail.com > > > wrote: > > > I guess, these are system VMs. > > none of my own created instances can start. > > IdName State > > > > 1 v-1-VM running > > 2 s-2-VM running > > > > virsh start 3> gives error > > error: failed to get domain '8' > > error: Domain not found: no domain with matching name '8' > > > > > > And yes, cloudstack and mysql - everything locally > > > > > > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland > > <daan.hoogl...@gmail.com> > > wrote: > > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < > > j.zolotar...@gmail.com > > > > > > > wrote: > > > > > > > * how to start instance with virsh? > > > > > > > ah, usually something like > > > # virsh start > > > or > > > # virsh start <number> > > > > > > > > > > * starting in debugger? I would rather not do it :) > > > > > > > ok, i expected as much. It will slow our solution process > unfortunately > > > > > > > > > In the below at the bottom it says you have two VMs and both are > > running. > > > Is that correct? > > > > > > > > > > * this is the log around GetHostStatsAnswer > > > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) > > > > HostStatsCollector > is > > > > running... > > > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq > > > 3-613896924205940798: > > > > Received: { Ans: , MgmtId: 264216221068220, via: > > > > 3(mtl1-apphst03), > > Ver: > > > > v1, Flags: 10, { GetHostStatsAnswer } } > > > > 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > > > StorageCollector is running... > > > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > > getCommandHostDelegation: > > > > class com.cloud.agent.api.GetStorageStatsCommand > > > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are > > > > returning > the > > > > default host to execute commands because the command is not of > > > > Copy > > type. > > > > 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > > > > 4-1941614389350105109: > > > > Received: { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), > > > > Ver: v1, > > > > Flags: 10, { GetStorageStatsAnswer } } > > > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > > getCommandHostDelegation: > > > > class com.cloud.agent.api.GetStorageStatsCommand > > > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru] > > > > (StatsCollector-1:ctx-308796ad) (
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
the same result [root@mtl1-apphst03 management]# virsh list --all IdName State 1 v-1-VM running 2 s-2-VM running On Fri, Feb 9, 2018 at 5:28 PM, Daan Hooglandwrote: > so try > # virsh list --all > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov > > wrote: > > > I guess, these are system VMs. > > none of my own created instances can start. > > IdName State > > > > 1 v-1-VM running > > 2 s-2-VM running > > > > virsh start 3> gives error > > error: failed to get domain '8' > > error: Domain not found: no domain with matching name '8' > > > > > > And yes, cloudstack and mysql - everything locally > > > > > > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland > > wrote: > > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < > > j.zolotar...@gmail.com > > > > > > > wrote: > > > > > > > * how to start instance with virsh? > > > > > > > ah, usually something like > > > # virsh start > > > or > > > # virsh start <number> > > > > > > > > > > * starting in debugger? I would rather not do it :) > > > > > > > ok, i expected as much. It will slow our solution process > unfortunately > > > > > > > > > In the below at the bottom it says you have two VMs and both are > > running. > > > Is that correct? > > > > > > > > > > * this is the log around GetHostStatsAnswer > > > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) HostStatsCollector > is > > > > running... > > > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq > > > 3-613896924205940798: > > > > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), > > Ver: > > > > v1, Flags: 10, { GetHostStatsAnswer } } > > > > 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) StorageCollector is > > > > running... > > > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > > getCommandHostDelegation: > > > > class com.cloud.agent.api.GetStorageStatsCommand > > > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning > the > > > > default host to execute commands because the command is not of Copy > > type. > > > > 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > > > > 4-1941614389350105109: > > > > Received: { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), Ver: v1, > > > > Flags: 10, { GetStorageStatsAnswer } } > > > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > > getCommandHostDelegation: > > > > class com.cloud.agent.api.GetStorageStatsCommand > > > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning > the > > > > default host to execute commands because the command is not of Copy > > type. > > > > 2018-02-09 14:05:31,517 DEBUG [c.c.a.t.Request] > > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > > > 3-613896924205940799: > > > > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), > > Ver: > > > > v1, Flags: 10, { GetStorageStatsAnswer } } > > > > 2018-02-09 14:05:34,504 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) Begin > cleanup > > > > expired async-jobs > > > > 2018-02-09 14:05:34,506 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) End cleanup > > > > expired > > > > async-jobs > > > > 2018-02-09 14:05:35,979 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] > > > > (secstorage-1:ctx-e83be1a3) (logid:60b9de64) Zone 1 is ready to > launch > > > > secondary storage VM > > > > 2018-02-09 14:05:36,002 DEBUG [c.c.c.ConsoleProxyManagerImpl] > > > > (consoleproxy-1:ctx-508f06d4) (logid:fea1da44) Zone 1 is ready to > > launch > > > > console proxy > > > > 2018-02-09 14:05:36,697 DEBUG [c.c.a.m.AgentManagerImpl] > > > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Processing Seq > > 5-273: > > > > { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, > > > > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand" > > > > :{"_proxyVmId":1,"_loadInfo":"{\n > > > > \"connections\": []\n}","wait":0}}] } > > > > 2018-02-09 14:05:36,699 DEBUG [c.c.a.m.AgentManagerImpl] > > > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Sending Seq > > 5-273: { > > > > Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
so try # virsh list --all On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjovwrote: > I guess, these are system VMs. > none of my own created instances can start. > IdName State > > 1 v-1-VM running > 2 s-2-VM running > > virsh start 3> gives error > error: failed to get domain '8' > error: Domain not found: no domain with matching name '8' > > > And yes, cloudstack and mysql - everything locally > > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland > wrote: > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com > > > > > wrote: > > > > > * how to start instance with virsh? > > > > > ah, usually something like > > # virsh start > > or > > # virsh start <number> > > > > > > > * starting in debugger? I would rather not do it :) > > > > > ok, i expected as much. It will slow our solution process unfortunately > > > > > > In the below at the bottom it says you have two VMs and both are > running. > > Is that correct? > > > > > > > * this is the log around GetHostStatsAnswer > > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) HostStatsCollector is > > > running... > > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq > > 3-613896924205940798: > > > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), > Ver: > > > v1, Flags: 10, { GetHostStatsAnswer } } > > > 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) StorageCollector is > > > running... > > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > getCommandHostDelegation: > > > class com.cloud.agent.api.GetStorageStatsCommand > > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the > > > default host to execute commands because the command is not of Copy > type. > > > 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > > > 4-1941614389350105109: > > > Received: { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), Ver: v1, > > > Flags: 10, { GetStorageStatsAnswer } } > > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > > getCommandHostDelegation: > > > class com.cloud.agent.api.GetStorageStatsCommand > > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the > > > default host to execute commands because the command is not of Copy > type. > > > 2018-02-09 14:05:31,517 DEBUG [c.c.a.t.Request] > > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > > 3-613896924205940799: > > > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), > Ver: > > > v1, Flags: 10, { GetStorageStatsAnswer } } > > > 2018-02-09 14:05:34,504 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) Begin cleanup > > > expired async-jobs > > > 2018-02-09 14:05:34,506 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) End cleanup > > > expired > > > async-jobs > > > 2018-02-09 14:05:35,979 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] > > > (secstorage-1:ctx-e83be1a3) (logid:60b9de64) Zone 1 is ready to launch > > > secondary storage VM > > > 2018-02-09 14:05:36,002 DEBUG [c.c.c.ConsoleProxyManagerImpl] > > > (consoleproxy-1:ctx-508f06d4) (logid:fea1da44) Zone 1 is ready to > launch > > > console proxy > > > 2018-02-09 14:05:36,697 DEBUG [c.c.a.m.AgentManagerImpl] > > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Processing Seq > 5-273: > > > { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, > > > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand" > > > :{"_proxyVmId":1,"_loadInfo":"{\n > > > \"connections\": []\n}","wait":0}}] } > > > 2018-02-09 14:05:36,699 DEBUG [c.c.a.m.AgentManagerImpl] > > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Sending Seq > 5-273: { > > > Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, > > > [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] > } > > > 2018-02-09 14:05:44,502 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) Begin cleanup > > > expired async-jobs > > > 2018-02-09 14:05:44,505 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > > (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) End cleanup > > > expired > > > async-jobs > > > 2018-02-09 14:05:44,582 DEBUG [c.c.n.r.VirtualNetworkApplianceManager > > Impl] > > > (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
I guess, these are system VMs. none of my own created instances can start. IdName State 1 v-1-VM running 2 s-2-VM running virsh start 3> gives error error: failed to get domain '8' error: Domain not found: no domain with matching name '8' And yes, cloudstack and mysql - everything locally On Fri, Feb 9, 2018 at 5:15 PM, Daan Hooglandwrote: > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov > > wrote: > > > * how to start instance with virsh? > > > ah, usually something like > # virsh start > or > # virsh start <number> > > > > * starting in debugger? I would rather not do it :) > > > ok, i expected as much. It will slow our solution process unfortunately > > > In the below at the bottom it says you have two VMs and both are running. > Is that correct? > > > > * this is the log around GetHostStatsAnswer > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) HostStatsCollector is > > running... > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq > 3-613896924205940798: > > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), Ver: > > v1, Flags: 10, { GetHostStatsAnswer } } > > 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) StorageCollector is > > running... > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > getCommandHostDelegation: > > class com.cloud.agent.api.GetStorageStatsCommand > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the > > default host to execute commands because the command is not of Copy type. > > 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > > 4-1941614389350105109: > > Received: { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), Ver: v1, > > Flags: 10, { GetStorageStatsAnswer } } > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) > getCommandHostDelegation: > > class com.cloud.agent.api.GetStorageStatsCommand > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the > > default host to execute commands because the command is not of Copy type. > > 2018-02-09 14:05:31,517 DEBUG [c.c.a.t.Request] > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > 3-613896924205940799: > > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), Ver: > > v1, Flags: 10, { GetStorageStatsAnswer } } > > 2018-02-09 14:05:34,504 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) Begin cleanup > > expired async-jobs > > 2018-02-09 14:05:34,506 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) End cleanup > > expired > > async-jobs > > 2018-02-09 14:05:35,979 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] > > (secstorage-1:ctx-e83be1a3) (logid:60b9de64) Zone 1 is ready to launch > > secondary storage VM > > 2018-02-09 14:05:36,002 DEBUG [c.c.c.ConsoleProxyManagerImpl] > > (consoleproxy-1:ctx-508f06d4) (logid:fea1da44) Zone 1 is ready to launch > > console proxy > > 2018-02-09 14:05:36,697 DEBUG [c.c.a.m.AgentManagerImpl] > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Processing Seq 5-273: > > { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, > > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand" > > :{"_proxyVmId":1,"_loadInfo":"{\n > > \"connections\": []\n}","wait":0}}] } > > 2018-02-09 14:05:36,699 DEBUG [c.c.a.m.AgentManagerImpl] > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Sending Seq 5-273: { > > Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, > > [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] } > > 2018-02-09 14:05:44,502 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) Begin cleanup > > expired async-jobs > > 2018-02-09 14:05:44,505 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > > (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) End cleanup > > expired > > async-jobs > > 2018-02-09 14:05:44,582 DEBUG [c.c.n.r.VirtualNetworkApplianceManager > Impl] > > (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 routers to > > update status. > > 2018-02-09 14:05:44,583 DEBUG [c.c.n.r.VirtualNetworkApplianceManager > Impl] > > (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 VPC > networks > > to update Redundant State. > > 2018-02-09 14:05:44,584 DEBUG [c.c.n.r.VirtualNetworkApplianceManager > Impl] > >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjovwrote: > * how to start instance with virsh? > ah, usually something like # virsh start or # virsh start <number> > * starting in debugger? I would rather not do it :) > ok, i expected as much. It will slow our solution process unfortunately In the below at the bottom it says you have two VMs and both are running. Is that correct? > * this is the log around GetHostStatsAnswer > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) HostStatsCollector is > running... > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq 3-613896924205940798: > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), Ver: > v1, Flags: 10, { GetHostStatsAnswer } } > 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) StorageCollector is > running... > 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) getCommandHostDelegation: > class com.cloud.agent.api.GetStorageStatsCommand > 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the > default host to execute commands because the command is not of Copy type. > 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq > 4-1941614389350105109: > Received: { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), Ver: v1, > Flags: 10, { GetStorageStatsAnswer } } > 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) getCommandHostDelegation: > class com.cloud.agent.api.GetStorageStatsCommand > 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the > default host to execute commands because the command is not of Copy type. > 2018-02-09 14:05:31,517 DEBUG [c.c.a.t.Request] > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq 3-613896924205940799: > Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), Ver: > v1, Flags: 10, { GetStorageStatsAnswer } } > 2018-02-09 14:05:34,504 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) Begin cleanup > expired async-jobs > 2018-02-09 14:05:34,506 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) End cleanup > expired > async-jobs > 2018-02-09 14:05:35,979 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-e83be1a3) (logid:60b9de64) Zone 1 is ready to launch > secondary storage VM > 2018-02-09 14:05:36,002 DEBUG [c.c.c.ConsoleProxyManagerImpl] > (consoleproxy-1:ctx-508f06d4) (logid:fea1da44) Zone 1 is ready to launch > console proxy > 2018-02-09 14:05:36,697 DEBUG [c.c.a.m.AgentManagerImpl] > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Processing Seq 5-273: > { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand" > :{"_proxyVmId":1,"_loadInfo":"{\n > \"connections\": []\n}","wait":0}}] } > 2018-02-09 14:05:36,699 DEBUG [c.c.a.m.AgentManagerImpl] > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Sending Seq 5-273: { > Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, > [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] } > 2018-02-09 14:05:44,502 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) Begin cleanup > expired async-jobs > 2018-02-09 14:05:44,505 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] > (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) End cleanup > expired > async-jobs > 2018-02-09 14:05:44,582 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 routers to > update status. > 2018-02-09 14:05:44,583 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 VPC networks > to update Redundant State. > 2018-02-09 14:05:44,584 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 networks to > update RvR status. > 2018-02-09 14:05:46,700 DEBUG [c.c.a.m.AgentManagerImpl] > (AgentManager-Handler-15:null) (logid:) SeqA 5-274: Processing Seq 5-274: > { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand" > :{"_proxyVmId":1,"_loadInfo":"{\n > \"connections\": []\n}","wait":0}}] } > 2018-02-09 14:05:46,702 DEBUG [c.c.a.m.AgentManagerImpl] > (AgentManager-Handler-15:null) (logid:) SeqA 5-274: Sending Seq 5-274: { > Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, > [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] } > 2018-02-09 14:05:49,610 DEBUG [c.c.h.d.HostDaoImpl]
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
* how to start instance with virsh? * starting in debugger? I would rather not do it :) * this is the log around GetHostStatsAnswer 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector] (StatsCollector-4:ctx-167407f0) (logid:0c470e95) HostStatsCollector is running... 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request] (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq 3-613896924205940798: Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), Ver: v1, Flags: 10, { GetHostStatsAnswer } } 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) StorageCollector is running... 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the default host to execute commands because the command is not of Copy type. 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq 4-1941614389350105109: Received: { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), Ver: v1, Flags: 10, { GetStorageStatsAnswer } } 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the default host to execute commands because the command is not of Copy type. 2018-02-09 14:05:31,517 DEBUG [c.c.a.t.Request] (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq 3-613896924205940799: Received: { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03), Ver: v1, Flags: 10, { GetStorageStatsAnswer } } 2018-02-09 14:05:34,504 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) Begin cleanup expired async-jobs 2018-02-09 14:05:34,506 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) End cleanup expired async-jobs 2018-02-09 14:05:35,979 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-e83be1a3) (logid:60b9de64) Zone 1 is ready to launch secondary storage VM 2018-02-09 14:05:36,002 DEBUG [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-508f06d4) (logid:fea1da44) Zone 1 is ready to launch console proxy 2018-02-09 14:05:36,697 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Processing Seq 5-273: { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] } 2018-02-09 14:05:36,699 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Sending Seq 5-273: { Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] } 2018-02-09 14:05:44,502 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) Begin cleanup expired async-jobs 2018-02-09 14:05:44,505 INFO [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-61f44674) (logid:94748b08) End cleanup expired async-jobs 2018-02-09 14:05:44,582 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 routers to update status. 2018-02-09 14:05:44,583 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 VPC networks to update Redundant State. 2018-02-09 14:05:44,584 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-9eea60cf) (logid:171472b2) Found 0 networks to update RvR status. 2018-02-09 14:05:46,700 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-15:null) (logid:) SeqA 5-274: Processing Seq 5-274: { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] } 2018-02-09 14:05:46,702 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-15:null) (logid:) SeqA 5-274: Sending Seq 5-274: { Ans: , MgmtId: 264216221068220, via: 5, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] } 2018-02-09 14:05:49,610 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-6233f81e) (logid:42d0cd7b) Resetting hosts suitable for reconnect 2018-02-09 14:05:49,611 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-6233f81e) (logid:42d0cd7b) Completed resetting hosts suitable for reconnect 2018-02-09 14:05:49,611 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-6233f81e) (logid:42d0cd7b) Acquiring hosts for clusters already owned by this management server 2018-02-09 14:05:49,611 DEBUG [c.c.h.d.HostDaoImpl]
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
and with cloudstack (and mysql) running locally, right? So my next step would be to stop cloudstack and see if you can start the image with virsh? Cloudstack thinks for some reason the host is not a suitable target. I have no clue why that is from your log. You can start cloudstack in a debugger but given you are asking on users@, i don't think you are familiar with that kind of work are, you? You might also want to look in the management (and agent) log to see if you can find anything about the capacity reported. Look for GetHostStatsAnswer. On Fri, Feb 9, 2018 at 3:11 PM, Jevgeni Zolotarjovwrote: > Yes, its KVM > > On Fri, Feb 9, 2018 at 4:06 PM, Daan Hoogland > wrote: > > > I am at a loss but really would like to help you. > > is it a KVM with the management server running locally? > > > > On Fri, Feb 9, 2018 at 3:02 PM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com > > > > > wrote: > > > > > My Host is only 1 machine atm: > > > Dell PowerEdge610 > > > OS: CentOS7 (latest) > > > CPU: 2x12 cores (24 cores in total) > > > RAM: 192 GB > > > Storage: 3+ TB > -- Daan
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
ount_id > BIGINT(20) > > > > >>> DEFAULT 0 > > > > >>> > 2018-02-09 09:38:05,478 DEBUG [c.c.u.d.ScriptRunner] > (main:null) > > > > >>> (logid:) > > > > >>> > ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY > > > > >>> > fk_ldap_trust_map__domain_id > > > > >>> > 2018-02-09 09:38:05,481 DEBUG [c.c.u.d.ScriptRunner] > (main:null) > > > > >>> (logid:) > > > > >>> > DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map > > > > >>> > 2018-02-09 09:38:05,482 DEBUG [c.c.u.d.ScriptRunner] > (main:null) > > > > >>> (logid:) > > > > >>> > CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON > > > > ldap_trust_map > > > > >>> > (domain_id, account_id) > > > > >>> > 2018-02-09 09:38:05,488 ERROR [c.c.u.PropertiesUtil] > (main:null) > > > > >>> (logid:) > > > > >>> > Unable to find properties file: commands.properties > > > > >>> > 2018-02-09 09:38:05,489 DEBUG [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) No commands.properties file was found, enabling > dynamic > > > > roles > > > > >>> by > > > > >>> > setting dynamic.apichecker.enabled to true if not already > > enabled. > > > > >>> > 2018-02-09 09:38:05,490 DEBUG [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) Done validating base64 content of user data > > > > >>> > 2018-02-09 09:38:05,490 DEBUG [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) Updating System Vm template IDs > > > > >>> > 2018-02-09 09:38:05,493 DEBUG [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) Updating LXC System Vms > > > > >>> > 2018-02-09 09:38:05,493 WARN [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) 4.11.0.0LXC SystemVm template not found. LXC > hypervisor > > is > > > > not > > > > >>> > used, so not failing upgrade > > > > >>> > 2018-02-09 09:38:05,494 DEBUG [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) Updating Hyperv System Vms > > > > >>> > 2018-02-09 09:38:05,495 WARN [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) 4.11.0.0Hyperv SystemVm template not found. Hyperv > > > > hypervisor > > > > >>> is > > > > >>> > not used, so not failing upgrade > > > > >>> > 2018-02-09 09:38:05,496 DEBUG [c.c.u.d.Upgrade41000to41100] > > > > (main:null) > > > > >>> > (logid:) Updating KVM System Vms > > > > >>> > 2018-02-09 09:38:05,497 ERROR [c.c.u.DatabaseUpgradeChecker] > > > > >>> (main:null) > > > > >>> > (logid:) Unable to upgrade the database > > > > >>> > com.cloud.utils.exception.CloudRuntimeException: 4.11.0.0KVM > > > > SystemVm > > > > >>> > template not found. Cannot upgrade system Vms > > > > >>> > at > > > > >>> > com.cloud.upgrade.dao.Upgrade41000to41100. > > updateSystemVmTemplates( > > > > >>> > Upgrade41000to41100.java:270) > > > > >>> > at > > > > >>> > com.cloud.upgrade.dao.Upgrade41000to41100. > performDataMigration( > > > > >>> > Upgrade41000to41100.java:71) > > > > >>> > at > > > > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( > > > > >>> > DatabaseUpgradeChecker.java:561) > > > > >>> > at > > > > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.check( > > > > >>> > DatabaseUpgradeChecker.java:641) > > > > >>> > at > > > > >>> > org.apache.cloudstack.spring.lifecycle. > > > CloudStackExtendedLifeCycle. > > > > >>> > checkIntegrity(CloudStackExtendedLifeCycle.java:65) > > > > >>> > at > > > > >>> > org.apache.cloudstack.spring.lifecycle.C
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
gt; > >>> > not used, so not failing upgrade > > > >>> > 2018-02-09 09:38:05,496 DEBUG [c.c.u.d.Upgrade41000to41100] > > > (main:null) > > > >>> > (logid:) Updating KVM System Vms > > > >>> > 2018-02-09 09:38:05,497 ERROR [c.c.u.DatabaseUpgradeChecker] > > > >>> (main:null) > > > >>> > (logid:) Unable to upgrade the database > > > >>> > com.cloud.utils.exception.CloudRuntimeException: 4.11.0.0KVM > > > SystemVm > > > >>> > template not found. Cannot upgrade system Vms > > > >>> > at > > > >>> > com.cloud.upgrade.dao.Upgrade41000to41100. > updateSystemVmTemplates( > > > >>> > Upgrade41000to41100.java:270) > > > >>> > at > > > >>> > com.cloud.upgrade.dao.Upgrade41000to41100.performDataMigration( > > > >>> > Upgrade41000to41100.java:71) > > > >>> > at > > > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( > > > >>> > DatabaseUpgradeChecker.java:561) > > > >>> > at > > > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.check( > > > >>> > DatabaseUpgradeChecker.java:641) > > > >>> > at > > > >>> > org.apache.cloudstack.spring.lifecycle. > > CloudStackExtendedLifeCycle. > > > >>> > checkIntegrity(CloudStackExtendedLifeCycle.java:65) > > > >>> > at > > > >>> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif > > > >>> eCycle.start( > > > >>> > CloudStackExtendedLifeCycle.java:55) > > > >>> > at > > > >>> > org.springframework.context.support.DefaultLifecycleProcessor. > > > doStart( > > > >>> > DefaultLifecycleProcessor.java:183) > > > >>> > at > > > >>> > org.springframework.context.support.DefaultLifecycleProcesso > > > >>> r.access$200( > > > >>> > DefaultLifecycleProcessor.java:52) > > > >>> > at > > > >>> > org.springframework.context.support.DefaultLifecycleProcessor$ > > > >>> > LifecycleGroup.start(DefaultLifecycleProcessor.java:358) > > > >>> > at > > > >>> > org.springframework.context.support.DefaultLifecycleProcesso > > > >>> r.startBeans( > > > >>> > DefaultLifecycleProcessor.java:159) > > > >>> > at > > > >>> > org.springframework.context.support.DefaultLifecycleProcesso > > > >>> r.onRefresh( > > > >>> > DefaultLifecycleProcessor.java:123) > > > >>> > at > > > >>> > org.springframework.context.support.AbstractApplicationContext. > > > >>> > finishRefresh(AbstractApplicationContext.java:884) > > > >>> > at > > > >>> > org.springframework.context.support.AbstractApplicationConte > > > >>> xt.refresh( > > > >>> > AbstractApplicationContext.java:552) > > > >>> > at > > > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > > > >>> DefinitionSet. > > > >>> > 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.DefaultModule > > > >>> DefinitionSet. > > > >>> > withModule(DefaultModuleDefinitionSet.java:245) > > > >>> > at > > > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > > > >>> DefinitionSet. > > > >>> > withModule(DefaultModuleDefinitionSet.java:250) > > > >>> > at > > > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > > > >>> DefinitionSet. > > > >>> > withModule(DefaultModuleDefinitionSet.java:233) > > > >>> > at > > > >>> > org.a
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
_map > > >>> > 2018-02-09 09:38:05,482 DEBUG [c.c.u.d.ScriptRunner] (main:null) > > >>> (logid:) > > >>> > CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON > > ldap_trust_map > > >>> > (domain_id, account_id) > > >>> > 2018-02-09 09:38:05,488 ERROR [c.c.u.PropertiesUtil] (main:null) > > >>> (logid:) > > >>> > Unable to find properties file: commands.properties > > >>> > 2018-02-09 09:38:05,489 DEBUG [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) No commands.properties file was found, enabling dynamic > > roles > > >>> by > > >>> > setting dynamic.apichecker.enabled to true if not already enabled. > > >>> > 2018-02-09 09:38:05,490 DEBUG [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) Done validating base64 content of user data > > >>> > 2018-02-09 09:38:05,490 DEBUG [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) Updating System Vm template IDs > > >>> > 2018-02-09 09:38:05,493 DEBUG [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) Updating LXC System Vms > > >>> > 2018-02-09 09:38:05,493 WARN [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) 4.11.0.0LXC SystemVm template not found. LXC hypervisor is > > not > > >>> > used, so not failing upgrade > > >>> > 2018-02-09 09:38:05,494 DEBUG [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) Updating Hyperv System Vms > > >>> > 2018-02-09 09:38:05,495 WARN [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) 4.11.0.0Hyperv SystemVm template not found. Hyperv > > hypervisor > > >>> is > > >>> > not used, so not failing upgrade > > >>> > 2018-02-09 09:38:05,496 DEBUG [c.c.u.d.Upgrade41000to41100] > > (main:null) > > >>> > (logid:) Updating KVM System Vms > > >>> > 2018-02-09 09:38:05,497 ERROR [c.c.u.DatabaseUpgradeChecker] > > >>> (main:null) > > >>> > (logid:) Unable to upgrade the database > > >>> > com.cloud.utils.exception.CloudRuntimeException: 4.11.0.0KVM > > SystemVm > > >>> > template not found. Cannot upgrade system Vms > > >>> > at > > >>> > com.cloud.upgrade.dao.Upgrade41000to41100.updateSystemVmTemplates( > > >>> > Upgrade41000to41100.java:270) > > >>> > at > > >>> > com.cloud.upgrade.dao.Upgrade41000to41100.performDataMigration( > > >>> > Upgrade41000to41100.java:71) > > >>> > at > > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( > > >>> > DatabaseUpgradeChecker.java:561) > > >>> > at > > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.check( > > >>> > DatabaseUpgradeChecker.java:641) > > >>> > at > > >>> > org.apache.cloudstack.spring.lifecycle. > CloudStackExtendedLifeCycle. > > >>> > checkIntegrity(CloudStackExtendedLifeCycle.java:65) > > >>> > at > > >>> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif > > >>> eCycle.start( > > >>> > CloudStackExtendedLifeCycle.java:55) > > >>> > at > > >>> > org.springframework.context.support.DefaultLifecycleProcessor. > > doStart( > > >>> > DefaultLifecycleProcessor.java:183) > > >>> > at > > >>> > org.springframework.context.support.DefaultLifecycleProcesso > > >>> r.access$200( > > >>> > DefaultLifecycleProcessor.java:52) > > >>> > at > > >>> > org.springframework.context.support.DefaultLifecycleProcessor$ > > >>> > LifecycleGroup.start(DefaultLifecycleProcessor.java:358) > > >>> > at > > >>> > org.springframework.context.support.DefaultLifecycleProcesso > > >>> r.startBeans( > > >>> > DefaultLifecycleProcessor.java:159) > > >>> > at > > >>> > org.springframework.context.support.DefaultLifecycleProcesso > > >>> r.onRefresh( > > >>> > DefaultLifecycleProcessor.java:123) > > >>> > at > >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
; > com.cloud.upgrade.dao.Upgrade41000to41100.performDataMigration( > >>> > Upgrade41000to41100.java:71) > >>> > at > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( > >>> > DatabaseUpgradeChecker.java:561) > >>> > at > >>> > com.cloud.upgrade.DatabaseUpgradeChecker.check( > >>> > DatabaseUpgradeChecker.java:641) > >>> > at > >>> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle. > >>> > checkIntegrity(CloudStackExtendedLifeCycle.java:65) > >>> > at > >>> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif > >>> eCycle.start( > >>> > CloudStackExtendedLifeCycle.java:55) > >>> > at > >>> > org.springframework.context.support.DefaultLifecycleProcessor. > doStart( > >>> > DefaultLifecycleProcessor.java:183) > >>> > at > >>> > org.springframework.context.support.DefaultLifecycleProcesso > >>> r.access$200( > >>> > DefaultLifecycleProcessor.java:52) > >>> > at > >>> > org.springframework.context.support.DefaultLifecycleProcessor$ > >>> > LifecycleGroup.start(DefaultLifecycleProcessor.java:358) > >>> > at > >>> > org.springframework.context.support.DefaultLifecycleProcesso > >>> r.startBeans( > >>> > DefaultLifecycleProcessor.java:159) > >>> > at > >>> > org.springframework.context.support.DefaultLifecycleProcesso > >>> r.onRefresh( > >>> > DefaultLifecycleProcessor.java:123) > >>> > at > >>> > org.springframework.context.support.AbstractApplicationContext. > >>> > finishRefresh(AbstractApplicationContext.java:884) > >>> > at > >>> > org.springframework.context.support.AbstractApplicationConte > >>> xt.refresh( > >>> > AbstractApplicationContext.java:552) > >>> > at > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > >>> DefinitionSet. > >>> > 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.DefaultModule > >>> DefinitionSet. > >>> > withModule(DefaultModuleDefinitionSet.java:245) > >>> > at > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > >>> DefinitionSet. > >>> > withModule(DefaultModuleDefinitionSet.java:250) > >>> > at > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > >>> DefinitionSet. > >>> > withModule(DefaultModuleDefinitionSet.java:233) > >>> > at > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > >>> DefinitionSet. > >>> > loadContexts(DefaultModuleDefinitionSet.java:117) > >>> > at > >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule > >>> DefinitionSet. > >>> > load(DefaultModuleDefinitionSet.java:79) > >>> > at > >>> > org.apache.cloudstack.spring.module.factory. > ModuleBasedContextFactory. > >>> > loadModules(ModuleBasedContextFactory.java:37) > >>> > at > >>> > org.apache.cloudstack.spring.module.factory.CloudStackSpring > >>> Context.init( > >>> > CloudStackSpringContext.java:71) > >>> > at > >>> > org.apache.cloudstack.spring.module.factory.CloudStackSpring > >>> Context. > >>> > (CloudStackSpringContext.java:58) > >>> > at > >>> > org.apache.cloudstack.spring.module.factory.CloudStackSpring > >>> Context. > >>> > (CloudStackSpringContext.java:62) > >>> > at > >>> > org.apache.cloudstack.spring.module.web. > CloudStackContextLoaderListene > >>> > r.contextInitialized(CloudStackContextLoaderListener.java:52) > >>> > at > >>> > org.eclipse.jetty.server.handler.ContextHandler.callContextI > >>> nitialized( > >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
DefinitionSet. >>> > withModule(DefaultModuleDefinitionSet.java:250) >>> > at >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >>> DefinitionSet. >>> > withModule(DefaultModuleDefinitionSet.java:233) >>> > at >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >>> DefinitionSet. >>> > loadContexts(DefaultModuleDefinitionSet.java:117) >>> > at >>> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >>> DefinitionSet. >>> > load(DefaultModuleDefinitionSet.java:79) >>> > at >>> > org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory. >>> > loadModules(ModuleBasedContextFactory.java:37) >>> > at >>> > org.apache.cloudstack.spring.module.factory.CloudStackSpring >>> Context.init( >>> > CloudStackSpringContext.java:71) >>> > at >>> > org.apache.cloudstack.spring.module.factory.CloudStackSpring >>> Context. >>> > (CloudStackSpringContext.java:58) >>> > at >>> > org.apache.cloudstack.spring.module.factory.CloudStackSpring >>> Context. >>> > (CloudStackSpringContext.java:62) >>> > at >>> > org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListene >>> > r.contextInitialized(CloudStackContextLoaderListener.java:52) >>> > at >>> > org.eclipse.jetty.server.handler.ContextHandler.callContextI >>> nitialized( >>> > ContextHandler.java:890) >>> > at >>> > org.eclipse.jetty.servlet.ServletContextHandler.callContextI >>> nitialized( >>> > 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 >>> > org.eclipse.jetty.webapp.WebAppContext.startContext( >>> > WebAppContext.java:1477) >>> > at >>> > org.eclipse.jetty.server.handler.ContextHandler. >>> > doStart(ContextHandler.java:785) >>> > >>> > >>> > >>> > On Fri, Feb 9, 2018 at 11:42 AM, Daan Hoogland < >>> daan.hoogl...@gmail.com> >>> > wrote: >>> > >>> > > before you continue Jevgeni, >>> > > >>> > > Do you have a good backup and is no-one able to access this >>> installation >>> > > with UI or API, when you roll back? >>> > > >>> > > On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg < >>> > > ernie.jvrensb...@shapeblue.com> wrote: >>> > > >>> > > > engine/schema/resources/META-INF/db/schema-41000to41100.sql: >>> > > > >>> > > > >>> > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> >>> > > > Sent: Friday, February 9, 2018 10:59:27 AM >>> > > > To: users@cloudstack.apache.org >>> > > > Subject: Re: cloudstack-management fails to start after upgrade >>> 4.10 -> >>> > > > 4.11 >>> > > > >>> > > > I dropped the column. But then another error like this appeared >>> > > > >>> > > > Please advise, where are the DB update script located? so I can >>> > manually >>> > > > inspect that. >>> > > > >>> > > > On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < >>> > > > ernie.jvrensb...@shapeblue.com> wrote: >>> > > > >>> > > > > Hi Jevgeni >>> > > > > >>> > > > > >>> > > > > It looks like there was a database error during the upgrade >>> process. >>> > > > > >>> > > > > >>> > > > > A SQL script that is trying to add a column 'for_vpc' to the >>> TABLE >>> > > > > 'cloud.network_offerings' but the column already exists, for some >>> > > reason, >>> > > > > so it fails because mysql does not allow 2 columns with the same
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
00to41100] (main:null) >> > (logid:) Updating KVM System Vms >> > 2018-02-09 09:38:05,497 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) >> > (logid:) Unable to upgrade the database >> > com.cloud.utils.exception.CloudRuntimeException: 4.11.0.0KVM SystemVm >> > template not found. Cannot upgrade system Vms >> > at >> > com.cloud.upgrade.dao.Upgrade41000to41100.updateSystemVmTemplates( >> > Upgrade41000to41100.java:270) >> > at >> > com.cloud.upgrade.dao.Upgrade41000to41100.performDataMigration( >> > Upgrade41000to41100.java:71) >> > at >> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( >> > DatabaseUpgradeChecker.java:561) >> > at >> > com.cloud.upgrade.DatabaseUpgradeChecker.check( >> > DatabaseUpgradeChecker.java:641) >> > at >> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle. >> > checkIntegrity(CloudStackExtendedLifeCycle.java:65) >> > at >> > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif >> eCycle.start( >> > CloudStackExtendedLifeCycle.java:55) >> > at >> > org.springframework.context.support.DefaultLifecycleProcessor.doStart( >> > DefaultLifecycleProcessor.java:183) >> > at >> > org.springframework.context.support.DefaultLifecycleProcesso >> r.access$200( >> > DefaultLifecycleProcessor.java:52) >> > at >> > org.springframework.context.support.DefaultLifecycleProcessor$ >> > LifecycleGroup.start(DefaultLifecycleProcessor.java:358) >> > at >> > org.springframework.context.support.DefaultLifecycleProcesso >> r.startBeans( >> > DefaultLifecycleProcessor.java:159) >> > at >> > org.springframework.context.support.DefaultLifecycleProcesso >> r.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.DefaultModule >> DefinitionSet. >> > 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.DefaultModule >> DefinitionSet. >> > withModule(DefaultModuleDefinitionSet.java:245) >> > at >> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet. >> > withModule(DefaultModuleDefinitionSet.java:250) >> > at >> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet. >> > withModule(DefaultModuleDefinitionSet.java:233) >> > at >> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet. >> > loadContexts(DefaultModuleDefinitionSet.java:117) >> > at >> > org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet. >> > load(DefaultModuleDefinitionSet.java:79) >> > at >> > org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory. >> > loadModules(ModuleBasedContextFactory.java:37) >> > at >> > org.apache.cloudstack.spring.module.factory.CloudStackSpring >> Context.init( >> > CloudStackSpringContext.java:71) >> > at >> > org.apache.cloudstack.spring.module.factory.CloudStackSpring >> Context. >> > (CloudStackSpringContext.java:58) >> > at >> > org.apache.cloudstack.spring.module.factory.CloudStackSpring >> Context. >> > (CloudStackSpringContext.java:62) >> > at >> > org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListene >> > r.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. &g
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
gt; 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.CloudStackContextLoaderListene > > r.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 > > org.eclipse.jetty.webapp.WebAppContext.startContext( > > WebAppContext.java:1477) > > at > > org.eclipse.jetty.server.handler.ContextHandler. > > doStart(ContextHandler.java:785) > > > > > > > > On Fri, Feb 9, 2018 at 11:42 AM, Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > before you continue Jevgeni, > > > > > > Do you have a good backup and is no-one able to access this > installation > > > with UI or API, when you roll back? > > > > > > On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg < > > > ernie.jvrensb...@shapeblue.com> wrote: > > > > > > > engine/schema/resources/META-INF/db/schema-41000to41100.sql: > > > > > > > > > > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > > > > Sent: Friday, February 9, 2018 10:59:27 AM > > > > To: users@cloudstack.apache.org > > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 > -> > > > > 4.11 > > > > > > > > I dropped the column. But then another error like this appeared > > > > > > > > Please advise, where are the DB update script located? so I can > > manually > > > > inspect that. > > > > > > > > On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < > > > > ernie.jvrensb...@shapeblue.com> wrote: > > > > > > > > > Hi Jevgeni > > > > > > > > > > > > > > > It looks like there was a database error during the upgrade > process. > > > > > > &
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
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.CloudStackContextLoaderListene > r.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 > org.eclipse.jetty.webapp.WebAppContext.startContext( > WebAppContext.java:1477) > at > org.eclipse.jetty.server.handler.ContextHandler. > doStart(ContextHandler.java:785) > > > > On Fri, Feb 9, 2018 at 11:42 AM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > before you continue Jevgeni, > > > > Do you have a good backup and is no-one able to access this installation > > with UI or API, when you roll back? > > > > On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg < > > ernie.jvrensb...@shapeblue.com> wrote: > > > > > engine/schema/resources/META-INF/db/schema-41000to41100.sql: > > > > > > > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > > > Sent: Friday, February 9, 2018 10:59:27 AM > > > To: users@cloudstack.apache.org > > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > > 4.11 > > > > > > I dropped the column. But then another error like this appeared > > > > > > Please advise, where are the DB update script located? so I can > manually > > > inspect that. > > > > > > On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < > > > ernie.jvrensb...@shapeblue.com> wrote: > > > > > > > Hi Jevgeni > > > > > > > > > > > > It looks like there was a database error during the upgrade process. > > > > > > > > > > > > A SQL script that is trying to add a column 'for_vpc' to the TABLE > > > > 'cloud.network_offerings' but the column already exists, for some > > reason, > > > > so it fails because mysql does not allow 2 columns with the same name > > in > > > > the same table. > > > > > > > > > > > > The column might have already existed from a previous upgrade or from > > > > running the 4.11 upgrade more than once, and perhaps the SQL script > is > > > not > > > > idempotent. > > > > > > > > > > > > I suggest to manually drop the column on the table and run the 4.11 > > > > upgrade process again. > > > > > > > > > > > > Regards > > > > > > > > > > > > Ernie > > > > > > > > > > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > > > > Sent: Friday, February 9, 2018 10:10:59 AM > > > > To: users@cloudstack.apache.org > > > > Subject: cloudstack-management fails
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
Jevgeni, the error shows that the MS is not able to find the 4.11 system template. Did you seed the 4.11 KVM system template? Best, Raja Engineering, Accelerite, 2055, Laurelwood Road, Santa Clara, CA, 95054 www.accelerite.com On 2/9/18, 3:15 PM, "Jevgeni Zolotarjov"wrote: Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: 4.11.0.0KVM SystemVm template not found. Cannot upgrade system Vms DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Accelerite, a Persistent Systems business. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent Systems business does not accept any liability for virus infected mails.
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
) 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 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1477) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:785) On Fri, Feb 9, 2018 at 11:42 AM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > before you continue Jevgeni, > > Do you have a good backup and is no-one able to access this installation > with UI or API, when you roll back? > > On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg < > ernie.jvrensb...@shapeblue.com> wrote: > > > engine/schema/resources/META-INF/db/schema-41000to41100.sql: > > > > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > > Sent: Friday, February 9, 2018 10:59:27 AM > > To: users@cloudstack.apache.org > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > > 4.11 > > > > I dropped the column. But then another error like this appeared > > > > Please advise, where are the DB update script located? so I can manually > > inspect that. > > > > On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < > > ernie.jvrensb...@shapeblue.com> wrote: > > > > > Hi Jevgeni > > > > > > > > > It looks like there was a database error during the upgrade process. > > > > > > > > > A SQL script that is trying to add a column 'for_vpc' to the TABLE > > > 'cloud.network_offerings' but the column already exists, for some > reason, > > > so it fails because mysql does not allow 2 columns with the same name > in > > > the same table. > > > > > > > > > The column might have already existed from a previous upgrade or from > > > running the 4.11 upgrade more than once, and perhaps the SQL script is > > not > > > idempotent. > > > > > > > > > I suggest to manually drop the column on the table and run the 4.11 > > > upgrade process again. > > > > > > > > > Regards > > > > > > > > > Ernie > > > > > > > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > > > Sent: Friday, February 9, 2018 10:10:59 AM > > > To: users@cloudstack.apache.org > > > Subject: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > > > > > cloudstack-management fails to start after upgrade from 4.10 to 4.11 > > > > > > management-server.log: > > > 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] > (main:null) > > > (logid:) Running upgrade Upgrade41000to41100 to upgrade from > > > 4.10.0.0-4.11.0.0 to 4.11.0.0 > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > > > -- Licensed to the Apache Software Foundation (ASF) under one > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > > > -- or more contributor license agreements. See the NOTICE file > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > > > -- distributed with this work for additional information > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > > > -- regarding copyright ownership. The ASF licenses this file > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > > > -- to you under the Apache License, Version 2.0 (the > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > > > -- "License"); you may not use this file except in compliance > > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) > (logid:) > >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
before you continue Jevgeni, Do you have a good backup and is no-one able to access this installation with UI or API, when you roll back? On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg < ernie.jvrensb...@shapeblue.com> wrote: > engine/schema/resources/META-INF/db/schema-41000to41100.sql: > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > Sent: Friday, February 9, 2018 10:59:27 AM > To: users@cloudstack.apache.org > Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> > 4.11 > > I dropped the column. But then another error like this appeared > > Please advise, where are the DB update script located? so I can manually > inspect that. > > On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < > ernie.jvrensb...@shapeblue.com> wrote: > > > Hi Jevgeni > > > > > > It looks like there was a database error during the upgrade process. > > > > > > A SQL script that is trying to add a column 'for_vpc' to the TABLE > > 'cloud.network_offerings' but the column already exists, for some reason, > > so it fails because mysql does not allow 2 columns with the same name in > > the same table. > > > > > > The column might have already existed from a previous upgrade or from > > running the 4.11 upgrade more than once, and perhaps the SQL script is > not > > idempotent. > > > > > > I suggest to manually drop the column on the table and run the 4.11 > > upgrade process again. > > > > > > Regards > > > > > > Ernie > > > > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > > Sent: Friday, February 9, 2018 10:10:59 AM > > To: users@cloudstack.apache.org > > Subject: cloudstack-management fails to start after upgrade 4.10 -> 4.11 > > > > cloudstack-management fails to start after upgrade from 4.10 to 4.11 > > > > management-server.log: > > 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) > > (logid:) Running upgrade Upgrade41000to41100 to upgrade from > > 4.10.0.0-4.11.0.0 to 4.11.0.0 > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- Licensed to the Apache Software Foundation (ASF) under one > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- or more contributor license agreements. See the NOTICE file > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- distributed with this work for additional information > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- regarding copyright ownership. The ASF licenses this file > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- to you under the Apache License, Version 2.0 (the > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- "License"); you may not use this file except in compliance > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- with the License. You may obtain a copy of the License at > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- http://www.apache.org/licenses/LICENSE-2.0 > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- Unless required by applicable law or agreed to in writing, > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- software distributed under the License is distributed on an > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- KIND, either express or implied. See the License for the > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- specific language governing permissions and limitations > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- under the License. > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > --; > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > > -- Schema upgrade from 4.10.0.0 to 4.11.0.0 > > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (ma
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
engine/schema/resources/META-INF/db/schema-41000to41100.sql: From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> Sent: Friday, February 9, 2018 10:59:27 AM To: users@cloudstack.apache.org Subject: Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11 I dropped the column. But then another error like this appeared Please advise, where are the DB update script located? so I can manually inspect that. On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < ernie.jvrensb...@shapeblue.com> wrote: > Hi Jevgeni > > > It looks like there was a database error during the upgrade process. > > > A SQL script that is trying to add a column 'for_vpc' to the TABLE > 'cloud.network_offerings' but the column already exists, for some reason, > so it fails because mysql does not allow 2 columns with the same name in > the same table. > > > The column might have already existed from a previous upgrade or from > running the 4.11 upgrade more than once, and perhaps the SQL script is not > idempotent. > > > I suggest to manually drop the column on the table and run the 4.11 > upgrade process again. > > > Regards > > > Ernie > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > Sent: Friday, February 9, 2018 10:10:59 AM > To: users@cloudstack.apache.org > Subject: cloudstack-management fails to start after upgrade 4.10 -> 4.11 > > cloudstack-management fails to start after upgrade from 4.10 to 4.11 > > management-server.log: > 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) > (logid:) Running upgrade Upgrade41000to41100 to upgrade from > 4.10.0.0-4.11.0.0 to 4.11.0.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Licensed to the Apache Software Foundation (ASF) under one > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- or more contributor license agreements. See the NOTICE file > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- distributed with this work for additional information > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- regarding copyright ownership. The ASF licenses this file > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- to you under the Apache License, Version 2.0 (the > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- "License"); you may not use this file except in compliance > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- with the License. You may obtain a copy of the License at > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- http://www.apache.org/licenses/LICENSE-2.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Unless required by applicable law or agreed to in writing, > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- software distributed under the License is distributed on an > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- KIND, either express or implied. See the License for the > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- specific language governing permissions and limitations > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- under the License. > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > --; > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Schema upgrade from 4.10.0.0 to 4.11.0.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > --; > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Add For VPC flag > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL > DEFAULT 0 > 2018-02-09 07:49:50,847 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc > INT(1) NOT NULL DEFAULT 0 > 2018-02-09 07:49:50,848 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate > column > name 'for_vpc' > 2018-02-09 07:49:50,849 ERROR [c.c.u.D
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
I dropped the column. But then another error like this appeared Please advise, where are the DB update script located? so I can manually inspect that. On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg < ernie.jvrensb...@shapeblue.com> wrote: > Hi Jevgeni > > > It looks like there was a database error during the upgrade process. > > > A SQL script that is trying to add a column 'for_vpc' to the TABLE > 'cloud.network_offerings' but the column already exists, for some reason, > so it fails because mysql does not allow 2 columns with the same name in > the same table. > > > The column might have already existed from a previous upgrade or from > running the 4.11 upgrade more than once, and perhaps the SQL script is not > idempotent. > > > I suggest to manually drop the column on the table and run the 4.11 > upgrade process again. > > > Regards > > > Ernie > > > From: Jevgeni Zolotarjov> Sent: Friday, February 9, 2018 10:10:59 AM > To: users@cloudstack.apache.org > Subject: cloudstack-management fails to start after upgrade 4.10 -> 4.11 > > cloudstack-management fails to start after upgrade from 4.10 to 4.11 > > management-server.log: > 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) > (logid:) Running upgrade Upgrade41000to41100 to upgrade from > 4.10.0.0-4.11.0.0 to 4.11.0.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Licensed to the Apache Software Foundation (ASF) under one > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- or more contributor license agreements. See the NOTICE file > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- distributed with this work for additional information > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- regarding copyright ownership. The ASF licenses this file > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- to you under the Apache License, Version 2.0 (the > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- "License"); you may not use this file except in compliance > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- with the License. You may obtain a copy of the License at > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- http://www.apache.org/licenses/LICENSE-2.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Unless required by applicable law or agreed to in writing, > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- software distributed under the License is distributed on an > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- KIND, either express or implied. See the License for the > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- specific language governing permissions and limitations > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- under the License. > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > --; > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Schema upgrade from 4.10.0.0 to 4.11.0.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > --; > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Add For VPC flag > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL > DEFAULT 0 > 2018-02-09 07:49:50,847 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc > INT(1) NOT NULL DEFAULT 0 > 2018-02-09 07:49:50,848 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate > column > name 'for_vpc' > 2018-02-09 07:49:50,849 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) > (logid:) Unable to execute upgrade script > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate > column > name 'for_vpc' > at com.cloud.utils.db.ScriptRunner.runScript( > ScriptRunner.java:185) > at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87) > at > com.cloud.upgrade.DatabaseUpgradeChecker.runScript( > DatabaseUpgradeChecker.java:459) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( > DatabaseUpgradeChecker.java:557) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check( >
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
Hi Jevgeni It looks like there was a database error during the upgrade process. A SQL script that is trying to add a column 'for_vpc' to the TABLE 'cloud.network_offerings' but the column already exists, for some reason, so it fails because mysql does not allow 2 columns with the same name in the same table. The column might have already existed from a previous upgrade or from running the 4.11 upgrade more than once, and perhaps the SQL script is not idempotent. I suggest to manually drop the column on the table and run the 4.11 upgrade process again. Regards Ernie From: Jevgeni ZolotarjovSent: Friday, February 9, 2018 10:10:59 AM To: users@cloudstack.apache.org Subject: cloudstack-management fails to start after upgrade 4.10 -> 4.11 cloudstack-management fails to start after upgrade from 4.10 to 4.11 management-server.log: 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Running upgrade Upgrade41000to41100 to upgrade from 4.10.0.0-4.11.0.0 to 4.11.0.0 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Licensed to the Apache Software Foundation (ASF) under one 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- or more contributor license agreements. See the NOTICE file 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- distributed with this work for additional information 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- regarding copyright ownership. The ASF licenses this file 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- to you under the Apache License, Version 2.0 (the 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- "License"); you may not use this file except in compliance 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- with the License. You may obtain a copy of the License at 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- http://www.apache.org/licenses/LICENSE-2.0 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Unless required by applicable law or agreed to in writing, 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- software distributed under the License is distributed on an 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- KIND, either express or implied. See the License for the 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- specific language governing permissions and limitations 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- under the License. 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --; 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Schema upgrade from 4.10.0.0 to 4.11.0.0 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --; 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- Add For VPC flag 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL DEFAULT 0 2018-02-09 07:49:50,847 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL DEFAULT 0 2018-02-09 07:49:50,848 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'for_vpc' 2018-02-09 07:49:50,849 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Unable to execute upgrade script com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'for_vpc' at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185) at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87) at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:459) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:557) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:641) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:183) at
Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11
Jevgeni, It looks like the db upgrade went wrong. You'll have to restore a backup, or be very savvy about what you do next. For some reason the new column, 'for_vpc' was already defined. The management server saw that the db was version 4.10 and self is 4.11. It then starts the run the required upgrade scripts. In this case just one set, 4.10.0.0 -> 4.11.0.0. You can restore the db and retrieve the db scripts from the jar or from github. The you can either 1. check what needs to be done for an upgrade and make sure there are no conflicts and restat themanagement server or 2. just run the required steps by hand including the entry in the version table. I have no doubt you have further question if you are new to this, feel free regards, On Fri, Feb 9, 2018 at 9:10 AM, Jevgeni Zolotarjovwrote: > cloudstack-management fails to start after upgrade from 4.10 to 4.11 > > management-server.log: > 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) > (logid:) Running upgrade Upgrade41000to41100 to upgrade from > 4.10.0.0-4.11.0.0 to 4.11.0.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Licensed to the Apache Software Foundation (ASF) under one > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- or more contributor license agreements. See the NOTICE file > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- distributed with this work for additional information > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- regarding copyright ownership. The ASF licenses this file > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- to you under the Apache License, Version 2.0 (the > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- "License"); you may not use this file except in compliance > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- with the License. You may obtain a copy of the License at > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- http://www.apache.org/licenses/LICENSE-2.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Unless required by applicable law or agreed to in writing, > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- software distributed under the License is distributed on an > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- KIND, either express or implied. See the License for the > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- specific language governing permissions and limitations > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- under the License. > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > --; > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Schema upgrade from 4.10.0.0 to 4.11.0.0 > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > --; > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > -- Add For VPC flag > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) > ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL > DEFAULT 0 > 2018-02-09 07:49:50,847 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc > INT(1) NOT NULL DEFAULT 0 > 2018-02-09 07:49:50,848 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate > column > name 'for_vpc' > 2018-02-09 07:49:50,849 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) > (logid:) Unable to execute upgrade script > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate > column > name 'for_vpc' > at com.cloud.utils.db.ScriptRunner.runScript( > ScriptRunner.java:185) > at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87) > at > com.cloud.upgrade.DatabaseUpgradeChecker.runScript( > DatabaseUpgradeChecker.java:459) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade( > DatabaseUpgradeChecker.java:557) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check( > DatabaseUpgradeChecker.java:641) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle. > checkIntegrity(CloudStackExtendedLifeCycle.java:65) > at > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start( > CloudStackExtendedLifeCycle.java:55) > at