[one-users] a new failure mode

[Tino Vazquez]

Hi Dan,

I completely agree, we need a way to recover this fail state. I've
openend a ticket to keep track of the solution [1].

Regards,

[1] http://dev.opennebula.org/issues/776

--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79



On Wed, Aug 17, 2011 at 11:12 PM, Dan Yocum <yocum at fnal.gov> wrote:
> I manually modified the database (mysql) to place the VMs into the 'running'
> state, thusly:
>
> mysql -B -e "update opennebula.vm_pool set etime='0' where oid='<vmid>'"
> mysql -B -e "update opennebula.vm_pool set lcm_state='3' where oid='<vmid>'"
> mysql -B -e "update opennebula.vm_pool set state='3' where oid='<vmid>'"
>
> where <vmid> is the ID of the VM as determined by using 'onevm list'.
>
>
> The second way to resolve the issue is to again modify the database, but
> place the status of the VM into 'unknown' and then restart the VM:
>
> mysql -B -e "update opennebula.vm_pool set lcm_state='3' where oid='<vmid>'"
> mysql -B -e "update opennebula.vm_pool set state='16' where oid='<vmid>'"
> onevm restart <vmid>