[ovirt-users] Re: Non-responsive vm's due to crashed host and hosted vm liveliness check fails

Hi,

You could try accessing the engine VM using the VNC. First, set the VNC password using 'hosted-engine --add-console-password', and then connect to the host using a VNC viewer, for example: 'remove-viewer vnc://HOST_IP:5900'

The liveliness check just checks if the web UI is running and reachable. If the VNC works, try checking if the 'ovirt-engine' service is running on the VM and that the network is configured properly.

Andrej

On 30 May 2018 at 18:31, <clam2718(a)gmail.com> wrote: Thank you very much Andrej. When I do as you suggest I am still unable to console in - I receive "Gtk-WARNING **: cannot open display:"

Any other ideas? Thanks, Charles