incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Huang <Alex.Hu...@citrix.com>
Subject RE: NEED HELP to fix an instance of this bug: http://bugs.cloud.com/show_bug.cgi?id=13559
Date Fri, 11 Jan 2013 23:40:55 GMT
The admin version of the stop command has a forced flag you can set.  Forced doesn't mean that
CloudStack has some special way to stop the vm but is a way to tell cloudstack that the VM
is actually stopped, just reset and release resources.   

--Alex

> -----Original Message-----
> From: William Clark [mailto:majorgearhead@gmail.com]
> Sent: Friday, January 11, 2013 12:38 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: NEED HELP to fix an instance of this bug:
> http://bugs.cloud.com/show_bug.cgi?id=13559
> 
> For those interested, I found a way around this.
> 
> 1) I made sure that all of the instances that were in an endless stopping
> state were indeed stopped.
> 2) Logged into the mysql db as root and selected the cloud db
> 3) Ran sql: update vm_instance set state = 'Stopped' where id = <INST ID>;
> 4) Went to the MS interface and clicked start
> 
> 
> On Fri, Jan 11, 2013 at 10:25 AM, William Clark
> <majorgearhead@gmail.com>wrote:
> 
> > We are expereinceing the bug detailed in:
> > http://bugs.cloud.com/show_bug.cgi?id=13559.  This is causing an outage
> > of these VM's as I cannot restart them because they are in the eronius
> > stopping state.
> >
> > Any devs working on this, is there a way around this to help me recover
> > quickly.  I see patches mentioned but I am leery of messing with the
> > integrity of my MS.
> >
> > Any help would be appreciated.
> >
> > --
> > Bill Clark
> >
> 
> 
> 
> --
> Bill Clark

Mime
View raw message