cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Peterson <jpeter...@acentek.net>
Subject RE: Recreating SystemVM's
Date Wed, 07 Jun 2017 19:41:35 GMT
Probably agreed.

But I ran toolstack restart on all hypervisors and v-3193 just tried to create and fail along
with s-5398.

The PIF error went away. But VM's are still recreating

https://pastebin.com/4n4xBgMT

New log from this afternoon.

My catalina.out is over 4GB 

Jeremy


-----Original Message-----
From: Makrand [mailto:makrandsanap@gmail.com] 
Sent: Wednesday, June 7, 2017 12:52 AM
To: users@cloudstack.apache.org
Subject: Re: Recreating SystemVM's

Hi there,

Looks more like hypervisor issue.

Just run *xe-toolstack-restart* on hosts where these VMs are trying to start or if you don't
have too many hosts, better run on all members including master. most of i/o related issues
squared off by toolstack bounce.

--
Makrand


On Wed, Jun 7, 2017 at 3:01 AM, Jeremy Peterson <jpeterson@acentek.net>
wrote:

> Ok so I pulled this from Sunday morning.
>
> https://pastebin.com/nCETw1sC
>
>
> errorInfo: [HOST_CANNOT_ATTACH_NETWORK, 
> OpaqueRef:65d0c844-bd70-81e9-4518-8809e1dc0ee7,
> OpaqueRef:0093ac3f-9f3a-37e1-9cdb-581398d27ba2]
>
> XenServer error.
>
> Now this still gets me because all of the other VM's launched just fine.
>
> Going into XenCenter I see an error at the bottom This PIF is a bond 
> slave and cannot be plugged.
>
> ???
>
> If I go to networking on the hosts I see the storage vlans and bonds 
> are all there.
>
> I see my GUEST-PUB bond is there and LACP is setup correct.
>
> Any suggestions ?
>
>
> Jeremy
>
>
> -----Original Message-----
> From: Jeremy Peterson [mailto:jpeterson@acentek.net]
> Sent: Tuesday, June 6, 2017 9:23 AM
> To: users@cloudstack.apache.org
> Subject: RE: Recreating SystemVM's
>
> Thank you all for those responses.
>
> I'll comb through my management-server.log and post a pastebin if I'm 
> scratching my head.
>
> Jeremy
>
> -----Original Message-----
> From: Rajani Karuturi [mailto:rajani@apache.org]
> Sent: Tuesday, June 6, 2017 6:53 AM
> To: users@cloudstack.apache.org
> Subject: Re: Recreating SystemVM's
>
> If the zone is enabled, cloudstack should recreate them automatically.
>
> ~ Rajani
>
> http://cloudplatform.accelerite.com/
>
> On June 6, 2017 at 11:37 AM, Erik Weber (terbolous@gmail.com)
> wrote:
>
> CloudStack should recreate automatically, check the mgmt server logs 
> for hints of why it doesn't happen.
>
> --
> Erik
>
> tir. 6. jun. 2017 kl. 04.29 skrev Jeremy Peterson
> <jpeterson@acentek.net>:
>
> I had an issue Sunday morning with cloudstack 4.9.0 and xenserver 6.5.0.
> My hosts stop sending LACP PDU's and caused a network drop to iSCSI 
> primary storage.
>
> So all my instances recovered via HA enabled.
>
> But my console proxy and secondary storage system VM's got stuck in a 
> boot state that would not power on.
>
> At this time they are expunged and gone.
>
> How do I tell cloudstack-management to recreate system VM's?
>
> I'm drawing a blank since deploying CS two years ago and just keeping 
> things running and adding hosts and more storage everything has been 
> so stable.
>
> Jeremy
>
Mime
View raw message