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 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

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 wrote: > No problem, I'm pleased that you're sorted. > > > Kind regards, > > Paul Angus > > paul.an...@shapeblue.com >

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

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 wrote: > Have you done the same for the virtual routers? > > I'll look at your

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:

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

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

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 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

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

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 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

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

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

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

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 Zolotarjov wrote: > I guess, these are system VMs. > none of my own created instances can start. > IdName State > > 1

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

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

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

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

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

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

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 > > wrote: >

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

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 wrote: > My Host is only 1 machine atm: > Dell PowerEdge610 > OS: CentOS7 (latest) > CPU: 2x12 cores (24 cores in

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

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 I was running cloudstack-4.10 without problems since it was released Your help is appreciated On Fri, Feb 9, 2018 at 3:57 PM, Daan Hoogland

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

Jevgeni, can you describe your environment in more detail? the host[3] that is in the avoid list, is it the host that VM was/is originally running on? Is anything running on it atm? what is it's distribution and version? etc On Fri, Feb 9, 2018 at 2:44 PM, Jevgeni Zolotarjov

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

To follow up: this is what I have in log: 2018-02-09 13:31:48,836 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1) (logid:0afb959d) DeploymentPlanner allocation algorithm: null 2018-02-09 13:31:48,836 DEBUG

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

OK, I pushed through and got management server running. The steps I made: * recovered DB from backup * downgraded everything 4.11->4.10 * installed systemvmtemplates * upgraded 4.10 -> 4.11 THEN!!! To make it run I had to go through all manual DB altering. Meaning, there is definitely something

Re: iso not downloading from local path

Check the ACL on your NFS share – remember your SSVM is using an IP address in the management range of your zone to access NFS, so we sometimes see issues where hypervisors are on the ACL, but not the management IP range. Regards, Dag Sonstebo Cloud Architect ShapeBlue On 09/02/2018, 11:15,

Re: iso not downloading from local path

Hey, I checked accessing nfs server from my ssvm. I tried the following root@s-1-VM:~# rpcinfo -p program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

my host in Centos7. I upgraded just by changing the URL in repository and yum update How do I upgrade systemvm templates now? On Fri, Feb 9, 2018 at 11:49 AM, Daan Hoogland wrote: > ok, this is also an upgrade issue. If all is well you installed them first. > You must

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

ok, this is also an upgrade issue. If all is well you installed them first. You must have downloaded the new systemvm templates and installed them as per the upgrade instructions (didn't read them myself this time so i'd have to check) and the upgrade will then mark them as the current templates

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"

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

I have a backup and noone is accessing the installation during upgrade process Now: I moved 1 bit further. Now I am having this error 2018-02-09 09:38:05,475 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER TABLE cloud.ldap_configuration ADD COLUMN domain_id BIGINT(20) DEFAULT NULL

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: >

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

engine/schema/resources/META-INF/db/schema-41000to41100.sql: From: Jevgeni Zolotarjov 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

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

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

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

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