Re: Insufficient capacity to restart Virtualrouter
Great Biligual auto correct use. Read at your own risico Op 5-aug.-2015 17:38 schreef "Sam Ceylani" : > i know the feeling :) > > Sent from my iPhone > > > On Aug 5, 2015, at 9:55 AM, Valerio Guaglianone < > v.guaglian...@midhgard.it> wrote: > > > > Yess, > > vlan tag was missing. > > Obviously no power loss before this happened > > > > Fixed :) > > > > > > Il 05/08/2015 15:40, Sam Ceylani ha scritto: > >> Check vlan tag from database for this network, mine was missing once :) > enter it and you should be all set. > >> > >> Have you experienced power loss before this happened? > >> > >> -Original Message- > >> From: Valerio Guaglianone [mailto:v.guaglian...@midhgard.it] > >> Sent: Wednesday, August 05, 2015 9:33 AM > >> To: users@cloudstack.apache.org > >> Subject: Re: Insufficient capacity to restart Virtualrouter > >> > >> Oops, sorry > >> CS 4.1.1 > >> Centos 6.5 > >> KVM > >> > >> Il 05/08/2015 15:32, Daan Hoogland ha scritto: > >>> Valerio, > >>> > >>> can you add some version numbers for us (asc version, ms-host > >>> platform, hypervisor types and version, etc)? > >>> > >>> On Wed, Aug 5, 2015 at 3:23 PM, Valerio Guaglianone < > >>> v.guaglian...@midhgard.it> wrote: > >>> > >>>> Here the rows inside management-server.log at restart about r-252-VM: > >>>> > >>>> 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] > >>>> (Timer-1:null) Startup CloudStack management server... > >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) SimpleInvestigator found > >>>> VM[DomainRouter|r-252-VM]to be alive? null > >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) XenServerInvestigator found > >>>> VM[DomainRouter|r-252-VM]to be alive? null > >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) VMwareInvestigator found > >>>> VM[DomainRouter|r-252-VM]to be alive? null > >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be > >>>> alive? null > >>>> 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be > >>>> alive? null > >>>> 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) Fencer null returned null > >>>> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false > >>>> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null > >>>> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null > >>>> 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] > >>>> (HA-Worker-3:work-168) Rescheduling > >>>> HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 > >>>> 14:29:22 CEST 2015 > >>>> 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] > >>>> (http-44300-6:null) Current user logged in under CET timezone > >>>> 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] > >>>> (http-44300-6:null) Timezone offset from UTC is: 2.0 > >>>> > >>>> > >>>> Il 05/08/2015 15:15, Erik Weber ha scritto: > >>>> > >>>>> On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < > >>>>> v.guaglian...@midhgard.it> wrote: > >>>>> > >>>>> When I restart my CS manager I read this error: > >>>>>> Insufficient capacity to restart VM, name: r-252-VM, id: 252 which > >>>>>> was running on host name: node-2.mydomain.it(id:18), availability > zone: > >>>>>> Z1MDH, pod: P1Z1MDH > >>>>>> > >>>>>> but the Virtualrouter work fine. > >>>>>> > >>>>>> Suggestions? > >>>>>> > >>>>>> > >>>>>> Post some management logs and we might be able to help you hunt it > down. > >>>>> As Daan said, Insufficient capacity exception can mean just about > >>>>> anything.. > >>>> -- > >>>> Valerio Guaglianone > >>>> > >>>> Midhgard S.r.l. > >>>> C/so Svizzera 185 bis > >>>> c/o centro Piero Della Francesca > >>>> 10149 - Torino > >>>> tel: +39-0117575375 Int. 16 > >>>> mobile: +39-3386935328 > >>>> fax: +39-0117768576 > >>>> sito web: http://www.midhgard.it/ > >> -- > >> Valerio Guaglianone > >> > >> Midhgard S.r.l. > >> C/so Svizzera 185 bis > >> c/o centro Piero Della Francesca > >> 10149 - Torino > >> tel: +39-0117575375 Int. 16 > >> mobile: +39-3386935328 > >> fax: +39-0117768576 > >> sito web: http://www.midhgard.it/ > > > > -- > > Valerio Guaglianone > > > > Midhgard S.r.l. > > C/so Svizzera 185 bis > > c/o centro Piero Della Francesca > > 10149 - Torino > > tel: +39-0117575375 Int. 16 > > mobile: +39-3386935328 > > fax: +39-0117768576 > > sito web: http://www.midhgard.it/ > > >
Re: Insufficient capacity to restart Virtualrouter
i know the feeling :) Sent from my iPhone > On Aug 5, 2015, at 9:55 AM, Valerio Guaglianone > wrote: > > Yess, > vlan tag was missing. > Obviously no power loss before this happened > > Fixed :) > > > Il 05/08/2015 15:40, Sam Ceylani ha scritto: >> Check vlan tag from database for this network, mine was missing once :) >> enter it and you should be all set. >> >> Have you experienced power loss before this happened? >> >> -Original Message- >> From: Valerio Guaglianone [mailto:v.guaglian...@midhgard.it] >> Sent: Wednesday, August 05, 2015 9:33 AM >> To: users@cloudstack.apache.org >> Subject: Re: Insufficient capacity to restart Virtualrouter >> >> Oops, sorry >> CS 4.1.1 >> Centos 6.5 >> KVM >> >> Il 05/08/2015 15:32, Daan Hoogland ha scritto: >>> Valerio, >>> >>> can you add some version numbers for us (asc version, ms-host >>> platform, hypervisor types and version, etc)? >>> >>> On Wed, Aug 5, 2015 at 3:23 PM, Valerio Guaglianone < >>> v.guaglian...@midhgard.it> wrote: >>> >>>> Here the rows inside management-server.log at restart about r-252-VM: >>>> >>>> 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] >>>> (Timer-1:null) Startup CloudStack management server... >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) SimpleInvestigator found >>>> VM[DomainRouter|r-252-VM]to be alive? null >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) XenServerInvestigator found >>>> VM[DomainRouter|r-252-VM]to be alive? null >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) VMwareInvestigator found >>>> VM[DomainRouter|r-252-VM]to be alive? null >>>> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be >>>> alive? null >>>> 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be >>>> alive? null >>>> 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) Fencer null returned null >>>> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false >>>> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null >>>> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null >>>> 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] >>>> (HA-Worker-3:work-168) Rescheduling >>>> HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 >>>> 14:29:22 CEST 2015 >>>> 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] >>>> (http-44300-6:null) Current user logged in under CET timezone >>>> 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] >>>> (http-44300-6:null) Timezone offset from UTC is: 2.0 >>>> >>>> >>>> Il 05/08/2015 15:15, Erik Weber ha scritto: >>>> >>>>> On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < >>>>> v.guaglian...@midhgard.it> wrote: >>>>> >>>>> When I restart my CS manager I read this error: >>>>>> Insufficient capacity to restart VM, name: r-252-VM, id: 252 which >>>>>> was running on host name: node-2.mydomain.it(id:18), availability zone: >>>>>> Z1MDH, pod: P1Z1MDH >>>>>> >>>>>> but the Virtualrouter work fine. >>>>>> >>>>>> Suggestions? >>>>>> >>>>>> >>>>>> Post some management logs and we might be able to help you hunt it down. >>>>> As Daan said, Insufficient capacity exception can mean just about >>>>> anything.. >>>> -- >>>> Valerio Guaglianone >>>> >>>> Midhgard S.r.l. >>>> C/so Svizzera 185 bis >>>> c/o centro Piero Della Francesca >>>> 10149 - Torino >>>> tel: +39-0117575375 Int. 16 >>>> mobile: +39-3386935328 >>>> fax: +39-0117768576 >>>> sito web: http://www.midhgard.it/ >> -- >> Valerio Guaglianone >> >> Midhgard S.r.l. >> C/so Svizzera 185 bis >> c/o centro Piero Della Francesca >> 10149 - Torino >> tel: +39-0117575375 Int. 16 >> mobile: +39-3386935328 >> fax: +39-0117768576 >> sito web: http://www.midhgard.it/ > > -- > Valerio Guaglianone > > Midhgard S.r.l. > C/so Svizzera 185 bis > c/o centro Piero Della Francesca > 10149 - Torino > tel: +39-0117575375 Int. 16 > mobile: +39-3386935328 > fax: +39-0117768576 > sito web: http://www.midhgard.it/ >
Re: Insufficient capacity to restart Virtualrouter
Yess, vlan tag was missing. Obviously no power loss before this happened Fixed :) Il 05/08/2015 15:40, Sam Ceylani ha scritto: Check vlan tag from database for this network, mine was missing once :) enter it and you should be all set. Have you experienced power loss before this happened? -Original Message- From: Valerio Guaglianone [mailto:v.guaglian...@midhgard.it] Sent: Wednesday, August 05, 2015 9:33 AM To: users@cloudstack.apache.org Subject: Re: Insufficient capacity to restart Virtualrouter Oops, sorry CS 4.1.1 Centos 6.5 KVM Il 05/08/2015 15:32, Daan Hoogland ha scritto: Valerio, can you add some version numbers for us (asc version, ms-host platform, hypervisor types and version, etc)? On Wed, Aug 5, 2015 at 3:23 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: Here the rows inside management-server.log at restart about r-252-VM: 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] (Timer-1:null) Startup CloudStack management server... 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) SimpleInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) XenServerInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) VMwareInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer null returned null 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Rescheduling HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 14:29:22 CEST 2015 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] (http-44300-6:null) Current user logged in under CET timezone 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] (http-44300-6:null) Timezone offset from UTC is: 2.0 Il 05/08/2015 15:15, Erik Weber ha scritto: On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: When I restart my CS manager I read this error: Insufficient capacity to restart VM, name: r-252-VM, id: 252 which was running on host name: node-2.mydomain.it(id:18), availability zone: Z1MDH, pod: P1Z1MDH but the Virtualrouter work fine. Suggestions? Post some management logs and we might be able to help you hunt it down. As Daan said, Insufficient capacity exception can mean just about anything.. -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/ -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/ -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/
RE: Insufficient capacity to restart Virtualrouter
Check vlan tag from database for this network, mine was missing once :) enter it and you should be all set. Have you experienced power loss before this happened? -Original Message- From: Valerio Guaglianone [mailto:v.guaglian...@midhgard.it] Sent: Wednesday, August 05, 2015 9:33 AM To: users@cloudstack.apache.org Subject: Re: Insufficient capacity to restart Virtualrouter Oops, sorry CS 4.1.1 Centos 6.5 KVM Il 05/08/2015 15:32, Daan Hoogland ha scritto: > Valerio, > > can you add some version numbers for us (asc version, ms-host > platform, hypervisor types and version, etc)? > > On Wed, Aug 5, 2015 at 3:23 PM, Valerio Guaglianone < > v.guaglian...@midhgard.it> wrote: > >> Here the rows inside management-server.log at restart about r-252-VM: >> >> 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] >> (Timer-1:null) Startup CloudStack management server... >> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) SimpleInvestigator found >> VM[DomainRouter|r-252-VM]to be alive? null >> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) XenServerInvestigator found >> VM[DomainRouter|r-252-VM]to be alive? null >> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) VMwareInvestigator found >> VM[DomainRouter|r-252-VM]to be alive? null >> 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be >> alive? null >> 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be >> alive? null >> 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) Fencer null returned null >> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false >> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null >> 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null >> 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] >> (HA-Worker-3:work-168) Rescheduling >> HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 >> 14:29:22 CEST 2015 >> 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] >> (http-44300-6:null) Current user logged in under CET timezone >> 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] >> (http-44300-6:null) Timezone offset from UTC is: 2.0 >> >> >> Il 05/08/2015 15:15, Erik Weber ha scritto: >> >>> On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < >>> v.guaglian...@midhgard.it> wrote: >>> >>> When I restart my CS manager I read this error: >>>> Insufficient capacity to restart VM, name: r-252-VM, id: 252 which >>>> was running on host name: node-2.mydomain.it(id:18), availability zone: >>>> Z1MDH, pod: P1Z1MDH >>>> >>>> but the Virtualrouter work fine. >>>> >>>> Suggestions? >>>> >>>> >>>> Post some management logs and we might be able to help you hunt it down. >>> As Daan said, Insufficient capacity exception can mean just about >>> anything.. >>> >>> >> -- >> Valerio Guaglianone >> >> Midhgard S.r.l. >> C/so Svizzera 185 bis >> c/o centro Piero Della Francesca >> 10149 - Torino >> tel: +39-0117575375 Int. 16 >> mobile: +39-3386935328 >> fax: +39-0117768576 >> sito web: http://www.midhgard.it/ >> >> > -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/
Re: Insufficient capacity to restart Virtualrouter
Oops, sorry CS 4.1.1 Centos 6.5 KVM Il 05/08/2015 15:32, Daan Hoogland ha scritto: Valerio, can you add some version numbers for us (asc version, ms-host platform, hypervisor types and version, etc)? On Wed, Aug 5, 2015 at 3:23 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: Here the rows inside management-server.log at restart about r-252-VM: 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] (Timer-1:null) Startup CloudStack management server... 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) SimpleInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) XenServerInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) VMwareInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer null returned null 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Rescheduling HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 14:29:22 CEST 2015 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] (http-44300-6:null) Current user logged in under CET timezone 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] (http-44300-6:null) Timezone offset from UTC is: 2.0 Il 05/08/2015 15:15, Erik Weber ha scritto: On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: When I restart my CS manager I read this error: Insufficient capacity to restart VM, name: r-252-VM, id: 252 which was running on host name: node-2.mydomain.it(id:18), availability zone: Z1MDH, pod: P1Z1MDH but the Virtualrouter work fine. Suggestions? Post some management logs and we might be able to help you hunt it down. As Daan said, Insufficient capacity exception can mean just about anything.. -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/ -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/
Re: Insufficient capacity to restart Virtualrouter
Valerio, can you add some version numbers for us (asc version, ms-host platform, hypervisor types and version, etc)? On Wed, Aug 5, 2015 at 3:23 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: > Here the rows inside management-server.log at restart about r-252-VM: > > 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] > (Timer-1:null) Startup CloudStack management server... > 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) SimpleInvestigator found VM[DomainRouter|r-252-VM]to > be alive? null > 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) XenServerInvestigator found > VM[DomainRouter|r-252-VM]to be alive? null > 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) VMwareInvestigator found VM[DomainRouter|r-252-VM]to > be alive? null > 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null > 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null > 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) Fencer null returned null > 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false > 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null > 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null > 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:work-168) Rescheduling > HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 > 14:29:22 CEST 2015 > 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] (http-44300-6:null) > Current user logged in under CET timezone > 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] (http-44300-6:null) > Timezone offset from UTC is: 2.0 > > > Il 05/08/2015 15:15, Erik Weber ha scritto: > >> On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < >> v.guaglian...@midhgard.it> wrote: >> >> When I restart my CS manager I read this error: >>> Insufficient capacity to restart VM, name: r-252-VM, id: 252 which was >>> running on host name: node-2.mydomain.it(id:18), availability zone: >>> Z1MDH, pod: P1Z1MDH >>> >>> but the Virtualrouter work fine. >>> >>> Suggestions? >>> >>> >>> Post some management logs and we might be able to help you hunt it down. >> >> As Daan said, Insufficient capacity exception can mean just about >> anything.. >> >> > -- > Valerio Guaglianone > > Midhgard S.r.l. > C/so Svizzera 185 bis > c/o centro Piero Della Francesca > 10149 - Torino > tel: +39-0117575375 Int. 16 > mobile: +39-3386935328 > fax: +39-0117768576 > sito web: http://www.midhgard.it/ > > -- Daan
Re: Insufficient capacity to restart Virtualrouter
Here the rows inside management-server.log at restart about r-252-VM: 2015-08-05 14:19:08,924 INFO [cloud.server.ManagementServerImpl] (Timer-1:null) Startup CloudStack management server... 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) SimpleInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) XenServerInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) VMwareInvestigator found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,970 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) null found VM[DomainRouter|r-252-VM]to be alive? null 2015-08-05 14:19:08,977 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer null returned null 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer KVMFenceBuilder returned false 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer OvmFenceBuilder returned null 2015-08-05 14:19:08,984 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Fencer VMwareFenceBuilder returned null 2015-08-05 14:19:09,326 INFO [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-3:work-168) Rescheduling HAWork[168-HA-252-Running-Investigating] to try again at Wed Aug 05 14:29:22 CEST 2015 2015-08-05 14:19:09,658 INFO [cloud.api.ApiServer] (http-44300-6:null) Current user logged in under CET timezone 2015-08-05 14:19:09,659 INFO [cloud.api.ApiServer] (http-44300-6:null) Timezone offset from UTC is: 2.0 Il 05/08/2015 15:15, Erik Weber ha scritto: On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: When I restart my CS manager I read this error: Insufficient capacity to restart VM, name: r-252-VM, id: 252 which was running on host name: node-2.mydomain.it(id:18), availability zone: Z1MDH, pod: P1Z1MDH but the Virtualrouter work fine. Suggestions? Post some management logs and we might be able to help you hunt it down. As Daan said, Insufficient capacity exception can mean just about anything.. -- Valerio Guaglianone Midhgard S.r.l. C/so Svizzera 185 bis c/o centro Piero Della Francesca 10149 - Torino tel: +39-0117575375 Int. 16 mobile: +39-3386935328 fax: +39-0117768576 sito web: http://www.midhgard.it/
Re: Insufficient capacity to restart Virtualrouter
On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: > When I restart my CS manager I read this error: > Insufficient capacity to restart VM, name: r-252-VM, id: 252 which was > running on host name: node-2.mydomain.it(id:18), availability zone: > Z1MDH, pod: P1Z1MDH > > but the Virtualrouter work fine. > > Suggestions? > > Post some management logs and we might be able to help you hunt it down. As Daan said, Insufficient capacity exception can mean just about anything.. -- Erik
Re: Insufficient capacity to restart Virtualrouter
Insufficient capacity can mean just about anything. For instance I just saw an instance of the error where there was a tag removed from a host and the deploy was using an offering that had this tag. The result that the list of hosts with sufficient capacity that have that tag was empty. The problem was therefore in the offering-host configuration combination and had nothing to do with capacity. happy hunting. On Wed, Aug 5, 2015 at 3:02 PM, Valerio Guaglianone < v.guaglian...@midhgard.it> wrote: > When I restart my CS manager I read this error: > Insufficient capacity to restart VM, name: r-252-VM, id: 252 which was > running on host name: node-2.mydomain.it(id:18), availability zone: > Z1MDH, pod: P1Z1MDH > > but the Virtualrouter work fine. > > Suggestions? > > -- > > -- Daan
