On April 8, 2020 7:47:20 PM GMT+03:00, "Maton, Brett"
<matonb(a)ltresources.co.uk> wrote:
On the host you tried to restart the engine on:
Add an alias to virsh (authenticates with virsh_auth.conf)
alias virsh='virsh -c
qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf'
Then run virsh:
virsh
virsh # list
Id Name State
----------------------------------------------------
xx HostedEngine Paused
xx ********** running
...
xx ********** running
HostedEngine should be in the list, try and resume the engine:
virsh # resume HostedEngine
On Wed, 8 Apr 2020 at 17:28, Shareef Jalloq <shareef(a)jalloq.co.uk>
wrote:
> Thanks!
>
> The status hangs due to, I guess, the VM being down....
>
> [root@ovirt-node-01 ~]# hosted-engine --vm-start
> VM exists and is down, cleaning up and restarting
> VM in WaitForLaunch
>
> but this doesn't seem to do anything. OK, after a while I get a
status of
> it being barfed...
>
> --== Host
ovirt-node-00.phoelex.com (id: 1) status ==--
>
> conf_on_shared_storage : True
> Status up-to-date : False
> Hostname :
ovirt-node-00.phoelex.com
> Host ID : 1
> Engine status : unknown stale-data
> Score : 3400
> stopped : False
> Local maintenance : False
> crc32 : 9c4a034b
> local_conf_timestamp : 523362
> Host timestamp : 523608
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=523608 (Wed Apr 8 16:17:11 2020)
> host-id=1
> score=3400
> vm_conf_refresh_time=523362 (Wed Apr 8 16:13:06 2020)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineDown
> stopped=False
>
>
> --== Host
ovirt-node-01.phoelex.com (id: 2) status ==--
>
> conf_on_shared_storage : True
> Status up-to-date : True
> Hostname :
ovirt-node-01.phoelex.com
> Host ID : 2
> Engine status : {"reason": "bad vm status",
"health":
> "bad", "vm": "down_unexpected", "detail":
"Down"}
> Score : 0
> stopped : False
> Local maintenance : False
> crc32 : 5045f2eb
> local_conf_timestamp : 1737037
> Host timestamp : 1737283
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=1737283 (Wed Apr 8 16:16:17 2020)
> host-id=2
> score=0
> vm_conf_refresh_time=1737037 (Wed Apr 8 16:12:11 2020)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineUnexpectedlyDown
> stopped=False
>
> On Wed, Apr 8, 2020 at 5:09 PM Maton, Brett
<matonb(a)ltresources.co.uk>
> wrote:
>
>> First steps, on one of your hosts as root:
>>
>> To get information:
>> hosted-engine --vm-status
>>
>> To start the engine:
>> hosted-engine --vm-start
>>
>>
>> On Wed, 8 Apr 2020 at 17:00, Shareef Jalloq <shareef(a)jalloq.co.uk>
wrote:
>>
>>> So my engine has gone down and I can't ssh into it either. If I
try to
>>> log into the web-ui of the node it is running on, I get redirected
because
>>> the node can't reach the engine.
>>>
>>> What are my next steps?
>>>
>>> Shareef.
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>>
https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/W7BP57OCIRS...
>>>
>>
This has to be resolved:
Engine status : unknown stale-data
Run again 'hosted-engine --vm-status'. If it remains the same, restart
ovirt-ha-broker.service & ovirt-ha-agent.service
Verify that the engine's storage is available. Then monitor the broker & agent
logs in /var/log/ovirt-hosted-engine-ha
Best Regards,
Strahil Nikolov