Thanks!

I managed to get the console through:

hosted-engine --add-console-password
/bin/remote-viewer vnc://localhost:5900

Turns out, there seems to be some corruption on the partition: http://screencast.com/t/6iR0U3QuI

Is there a way to boot from CD, so I can start rescue mode?


Op vr 15 apr. 2016 om 10:58 schreef Martin Sivak <msivak@redhat.com>:
Hi,

you can access the console using vnc or use virsh to get access to the
serial console.

Check the following commands on the host where the VM is currently running:

virsh -r list
virsh -r console HostedEngine
virsh -r vncdisplay HostedEngine

Those should give you enough pointers to connect to the VM.

Regards

Martin Sivak



On Fri, Apr 15, 2016 at 10:14 AM, Paul Groeneweg | Pazion
<paul@pazion.nl> wrote:
>
> Tonight my server with NFS hosted-engine mount crashed.
> Now all is back online ,except the hosted engine. I can't ping  or ssh the
> machine
>
> when I do hosted-engine --vm-status, I get:
>
> ..........
> --== Host 2 status ==--
>
> Status up-to-date                  : True
> Hostname                           : geisha-3.pazion.nl
> Host ID                            : 2
> Engine status                      : {"reason": "failed liveliness check",
> "health": "bad", "vm": "up", "detail": "up"}
> Score                              : 3400
> stopped                            : False
> Local maintenance                  : False
> crc32                              : d71d7c6b
> Host timestamp                     : 4404
> ............
>
> I tried restarting all services/nfs mounts, start hosted engine on other
> hosts, but all the same host up, but liveliness failed and unable to access
> the network/IP.
>
> I imagine it is stuck at the console requiring a fsck check maybe?
> Is there a way to access the boot display directly?
>
> Any help is highly appreciated!
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>