[ovirt-users] Re: Cannot restart ovirt after massive failure.
Usually this is not the problem.
Start checking:
1. Export FS is mounted
2. NFS server is running (after all this is a single node NFS setup)
3. Check that vdsmd , supervdsmd and sanlock are running
4. If needed, enable debug for the ovirt-ha-{agent,broker} as usually the default log
level won't show the problem.
Best Regards,
Strahil Nikolov
В неделя, 8 август 2021 г., 20:06:46 ч. Гринуич+3, Gilboa Davara <gilboad(a)gmail.com>
написа:
On Sun, Aug 8, 2021 at 7:53 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
Hello all,
During the night, one of my (smaller) setups, a single node self hosted engine (localhost
NFS) crashed due to what-looks-like a massive disk failure (Software RAID6, with 10 drives
+ spare).
After a reboot, I let the RAID resync with a fresh drive) and went on to start oVirt.
However, no such luck.
Two issues:
1. ovirt-ha-broker fails due to broken hosted engine state (log attached).
2. ovirt-ha-agent fails due to network test (tcp) even though both remote-host and DNS
servers are active. (log attached).
Two questions:
1. Can I somehow force the agent to disable the network liveliness test?
2. Can I somehow force the broker to rebuild / fix the hosted engine state?
- Gilboa
FWIW switching agent network test to none (via hosted-engine --set-shared-config
network_test none --type=he_local) doesn't seem to work.
(Unless I'm missing the point and the agent is failing due to broker issues and not
due to a failed network liveliness check).
- Gilboa
_______________________________________________
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/OH4H5K2FZXO...