ONE version: 5.2.1
The VMs are running as usual.
Just the state is in UNKNOWN state.
Whenever I recover -> success the VMs, it shown RUNNING but changed back to UNKNOWN after a while.
Below is the error message from oned.log
Tue Mar 28 09:16:41 2017 [Z0][InM][I]: Command execution fail: 'if [ -x “/var/tmp/one/im/run_probes” ]; then /var/tmp/one/im/run_probes kvm /var/lib/one//datastores 4124 20 1 supermicro-01; else exit 42; fi’
Tue Mar 28 09:16:41 2017 [Z0][InM][I]: error: failed to connect to the hypervisor
Tue Mar 28 09:16:41 2017 [Z0][InM][I]: error: error from service: CheckAuthorization: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Tue Mar 28 09:16:41 2017 [Z0][InM][E]: Error executing kvm.rb
Tue Mar 28 09:16:41 2017 [Z0][InM][E]: Error executing collectd-client_control.sh
Tue Mar 28 09:16:41 2017 [Z0][InM][I]: ExitCode: 255
I know it is an old thread but very helpful, If somebody have the same problem.
all VMS state unknown
the host showing " Error executing kvm.rb", as such impossible to manage the VMs from opennebula anymore.
no networking issues between opennebula and the host
all VMs are still online on the host
Restarting libvirtd service on the host as stated in the previous posts did fix the issue. sudo systemctl restart libvirtd
In my case I was able to see the errors on the host by using sudo systemctl status libvirtd
May 18 04:12:44 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:12:44.484+0000: 1286: error : virDBusCall:1570 : error from service: CheckAuthorization: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeou
May 18 04:12:44 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:12:44.484+0000: 1280: error : virNetSocketReadWire:1801 : End of file while reading data: Input/output error
May 18 04:12:59 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:12:59.675+0000: 1290: error : virDBusCall:1570 : error from service: CheckAuthorization: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeou
May 18 04:12:59 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:12:59.676+0000: 1280: error : virNetSocketReadWire:1801 : End of file while reading data: Input/output error
May 18 04:13:25 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:13:25.740+0000: 1288: error : virDBusCall:1570 : error from service: CheckAuthorization: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeou
May 18 04:13:25 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:13:25.740+0000: 1280: error : virNetSocketReadWire:1801 : End of file while reading data: Input/output error
May 18 04:16:40 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:16:40.919+0000: 1289: error : virDBusCall:1570 : error from service: CheckAuthorization: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeou
May 18 04:16:40 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:16:40.920+0000: 1280: error : virNetSocketReadWire:1801 : End of file while reading data: Input/output error
May 18 04:17:14 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:17:14.003+0000: 1285: error : virDBusCall:1570 : error from service: CheckAuthorization: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeou
May 18 04:17:14 sg.mydomain.com libvirtd[1280]: 2019-05-18 04:17:14.003+0000: 1280: error : virNetSocketReadWire:1801 : End of file while reading data: Input/output error