Hi all, After some week of test with no major issue, we have pass our OpenNebula in production this week end. We have 36 VM on 3 hosts. Today, we have problems: Each host was detected by one as done but OS is correctly running and be accessible by ssh. We have this error in syslog Aug 22 22:13…

The image corruption seems due because the one monitoring system detect the host as done, but VM are always running on it. So One restart VM on another hosts, but image disk are already in use… I think a fencing method must be use on host monitoring failure to avoid this kind of failure.

I try to apply this [image] Polkitd traps general protection ip in libmozjs-17.0.so Community Support no one? It seems to be related to polkitd. I suspect polkit doesn’t like the user oneadmin to run VM? This is how the opennebula-kvm-node package configure KVM [root] # …

a feature is already open to be able to fence a device on host hook : http://dev.opennebula.org/issues/4659

Hi Yannick, I’ve extracted the fencing part of the FT host-hook in our addon to the following patch: host_error.rb.patch (1.4 KB) It is adding additional argument ‘-s’ to the host_hook.rb: host_error.rb <other-args> -s /usr/sbin/myfencing-script.sh Then on host failure event and if there are VM’…

Hi, could you explain how to apply this patch ? In addition, $FT_HOSTNAME is the host name that failed, is it correct ? So, I can use it to manage (with case instruction) different fence method. Thanks, Yannick

Hi Yannick, [image] Yannick_MOLINET: could you explain how to apply this patch ? To apply the patch use the following (adjust thepath if they differ from defaults) cd /var/lib/one/remotes/hooks/ft cp host_error.rb host_error.rb.orig patch -p0 < /path/to/host_hook.rb.patch [image] Yannic…

I think there is additional patch to be sure that host_hook is not missing an failed node # If the host came back, exit! avoid duplicated VMs exit 0 if host.state != 3 change to # If the host came back, exit! avoid duplicated VMs exit 0 if host.state != 3 and host.state != 5 where host.state = 5…

I can not test this on my production servers so we must wait to add new servers in the cluster (in the next month). I think to dev a bash script, with: an array with server hostname as key and fencing command as value. a request on the array to execute the correct command. some log message and te…

This error is back. it’s a monitoring problem. I have disable host error hook, so VM are always running on the host and they works as fine. The change do in /etc/libvrt/libvirt.conf on my debian 8 don’t solved the issue. any help to fix this issue is welcome. Thansk, Yannick

I’m wrong. I don’t have apply the setting in the correct files :frowning: I’m have apply this in /etc/libvirt/libvirt.conf and not in /etc/libvirt/libvirtd.conf

Major issue: error from service: CheckAuthorization

Product Support

Yannick_MOLINET (Yannick Molinet) August 23, 2016, 7:35am 3

I try to apply this

Topic		Replies	Views
Host error hook not working (5.4.13) Product Support	6	1633	July 12, 2018
Hosts entering the ERROR state Product Support	10	5742	February 4, 2019
Cannot monitor VM status and Host with error Product Support	1	1900	February 5, 2018
VM HA not working after update to 5.2 Product Support	11	1653	February 20, 2017
HOST failure HOOK execution failed Product Support	17	1952	October 24, 2019

Major issue: error from service: CheckAuthorization

Related topics