openstack team mailing list archive

[Narayan Desai <narayan.desai@xxxxxxxxx>]

And if a nova reboot fails, you can always fall back to issuing virsh
commands on the node behind nova's back.
 -nld

On Mon, Apr 8, 2013 at 8:28 PM, Blair Bethwaite
<blair.bethwaite@xxxxxxxxx> wrote:
> Dave,
>
> Have you tried rebooting it (via OpenStack dashboard/CLI/API)? Obviously
> you'll lose memory state, but the VM will boot from the same (current)
> virtual disks, so if those disks are ok the instance will have all
> previously saved/altered data.
>
>
> On 8 April 2013 19:09, Dave Pigott <dave.pigott@xxxxxxxxxx> wrote:
>>
>> Hi all,
>>
>> I've got an instance that's been running for several months now, and
>> suddenly we can not ping or telnet to it. It shows up in the list as Active
>> and Running, but just isn't responding. We earlier had a disk full problem
>> on that node, but this happened before that occurred, so I don't think
>> that's responsible (but I could be wrong). The instance is used extensively
>> so I'd prefer to fix it rather than have to kill it and spin up another
>> instance. FYI all other instances in the cloud are fine and we can ssh and
>> ping them.
>>
>> Any ideas what I can do to get this instance active again?
>>
>> Thanks
>>
>> Dave
>> Lava Lab Lead
>> Linaro Ltd
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> --
> Cheers,
> ~Blairo
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>