On Tue, Apr 9, 2019 at 11:13 AM Tau Makgaile <tau(a)sanren.ac.za> wrote:
I might have forgotten to mention that the hosted-engine vm is not
pin-gable. Its not reachable and i am wondering how an increase in
partition size ended up affecting it.
I'd suggest to
1. enable the global maintenance mode on host side
2. manually start the engine VM with hosted-engine --vm-start
3. double check the boot process over VNC
Maybe something like a failing fsck is preventing the VM from correctly
Thanks in advance
On Tue, Apr 9, 2019 at 10:53 AM Simone Tiraboschi <stirabos(a)redhat.com>
> On Tue, Apr 9, 2019 at 9:59 AM Tau Makgaile <tau(a)sanren.ac.za> wrote:
>> I am currently experiencing a problem with my Hosted-engine.
>> Hosted-engine disconnected after increasing / partition. The increase went
>> well but after some time the hosted-enigine VM disconnected and has since
>> been giving alerts such as* re-initializingFSM*.
>> Though VMs underneth are running, Hosted-engine --vm-status:
>> *"reason": "failed liveliness check", "health":
"bad", "vm": "up",
>> There is no backup to restore at the moment. I am looking for a way to
>> bring it up without redeploying the hosted engine.
> I'd suggest to start connecting to the engine VM via ssh / serial console
> (hosted-engine --console) / VNC (hosted-engine --add-console-password # and
> then point your VNC client to the address shown there).
> Then check the status of ovirt-engine service with
> systemctl status ovirt-engine
>> Thanks in advance for your help.
>> Kind regards,
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> List Archives: