search for: virkeepalivetimerinternal

Hi, i have a two-node cluster with several domains as resources. During testing i tried several times to migrate some domains concurrently. Usually it suceeded, but rarely it failed. I found one clue in the log: Dec 03 16:03:02 ha-idg-1 libvirtd[3252]: 2018-12-03 15:03:02.758+0000: 3252: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout The domains are configured similar: primitive vm_geneious VirtualDomain \ params config="/mnt/san/share/config.xml" \ params hypervisor="qemu:///system" \ params migration_transport=ssh \...

...luster with several domains as resources. During testing i > tried several times to migrate some domains concurrently. > Usually it suceeded, but rarely it failed. I found one clue in the log: > > Dec 03 16:03:02 ha-idg-1 libvirtd[3252]: 2018-12-03 15:03:02.758+0000: 3252: > error : virKeepAliveTimerInternal:143 : internal error: connection closed due > to keepalive timeout > > The domains are configured similar: > primitive vm_geneious VirtualDomain \ > params config="/mnt/san/share/config.xml" \ > params hypervisor="qemu:///system" \ > pa...

...domains as resources. During testing i >> tried several times to migrate some domains concurrently. >> Usually it suceeded, but rarely it failed. I found one clue in the log: >> >> Dec 03 16:03:02 ha-idg-1 libvirtd[3252]: 2018-12-03 15:03:02.758+0000: 3252: >> error : virKeepAliveTimerInternal:143 : internal error: connection closed due >> to keepalive timeout >> >> The domains are configured similar: >> primitive vm_geneious VirtualDomain \ >> params config="/mnt/san/share/config.xml" \ >> params hypervisor="qemu:///syst...

...:609 : stream aborted at client request 2017-02-17 06:22:11.020+0000: 5052: error :daemonStreamHandleAbort:609 : stream aborted at client request 2017-02-17 06:22:26.012+0000: 5052: error :daemonStreamHandleAbort:609 : stream aborted at client request 2017-02-18 01:53:36.308+0000: 5052: warning :virKeepAliveTimerInternal:156 : No response from client 0xe14160 after 5keepalive messages in 30 seconds 2017-02-18 01:53:47.346+0000: 5052: warning :virKeepAliveTimerInternal:156 : No response from client 0xe14c70 after 5 keepalivemessages in 30 seconds /var/log/libvirt/libvirtd.log What could be the problem. I am runni...

...eAbort:609 : stream abortedat client request 2017-02-1706:22:11.020+0000: 5052: error : daemonStreamHandleAbort:609 : stream abortedat client request 2017-02-1706:22:26.012+0000: 5052: error : daemonStreamHandleAbort:609 : stream abortedat client request 2017-02-1801:53:36.308+0000: 5052: warning : virKeepAliveTimerInternal:156 : No responsefrom client 0xe14160 after 5 keepalive messages in 30 seconds 2017-02-1801:53:47.346+0000: 5052: warning : virKeepAliveTimerInternal:156 : No responsefrom client 0xe14c70 after 5 keepalive messages in 30 seconds/var/log/libvirt/libvirtd.log   What could be theproblem. I am running...

...9 : stream aborted at client request 2017-02-17 06:22:11.020+0000: 5052: error : daemonStreamHandleAbort:609 : stream aborted at client request 2017-02-17 06:22:26.012+0000: 5052: error : daemonStreamHandleAbort:609 : stream aborted at client request 2017-02-18 01:53:36.308+0000: 5052: warning : virKeepAliveTimerInternal:156 : No response from client 0xe14160 after 5 keepalive messages in 30 seconds 2017-02-18 01:53:47.346+0000: 5052: warning : virKeepAliveTimerInternal:156 : No response from client 0xe14c70 after 5 keepalive messages in 30 seconds /var/log/libvirt/libvirtd.log What could be the problem. I am...

...9 : stream aborted at client request 2017-02-17 06:22:11.020+0000: 5052: error : daemonStreamHandleAbort:609 : stream aborted at client request 2017-02-17 06:22:26.012+0000: 5052: error : daemonStreamHandleAbort:609 : stream aborted at client request 2017-02-18 01:53:36.308+0000: 5052: warning : virKeepAliveTimerInternal:156 : No response from client 0xe14160 after 5 keepalive messages in 30 seconds 2017-02-18 01:53:47.346+0000: 5052: warning : virKeepAliveTimerInternal:156 : No response from client 0xe14c70 after 5 keepalive messages in 30 seconds /var/log/libvirt/libvirtd.log What could be the problem. I am...

...ae0, Begin I think is my program problem, But when I use virsh domstats cmd , The cmd block too. In my program, I set timeout event for virConnectPtr. But my program blocked all the time. I find my system log, I find some libvirtd error: libvirtd: 2018-03-08 04:25:13.144+0000: 1289: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout Mar 7 23:33:05 localhost libvirtd: 2018-03-08 04:33:05.738+0000: 1289: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error Mar 7 23:33:14 localhost libvirtd: 2018-03-08 04:33:14.253+0000: 1289: err...

...moved the CentOS 7 hosts. The CentOS 6 VM runs fine on the host, and can do non-live migrations without any issues, however when attempting to live migrate the VM it fails. The VM itself is CentOS 7. Live migration does work when using VMs created using CentOS 7. Error message: "libvirtd virKeepAliveTimerInternal connection closed due to keep alive timeout. Cannot acquire state change lock (held by remoteDispatchDomainMigratePrepare3params)" Surrounding error messages here: Origin Host: https://pastebin.com/fLN6DRiq Recipient Host: https://pastebin.com/xR6mnaW2 The command being run is: V...

...0000: 14487: error : virNetSocketReadWire:1613 : End of file while reading data: Input/output error 2016-03-03 19:23:29.247+0000: 14486: error : virConnectUnregisterCloseCallback:1282 : Requested operation is not valid: A different callback was requested 2016-03-03 19:24:49.521+0000: 14487: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout 2016-03-03 19:25:17.043+0000: 14486: error : virConnectUnregisterCloseCallback:1282 : Requested operation is not valid: A different callback was requested 2016-03-03 19:25:47.110+0000: 14487: error : virNetSocketReadWire:1613 : End of...

...become a zombie. At that state, libvirtd reports the instance to be running and I can't restart the VM because libvirtd fails to kill the qemu-kvm process. Finding the root cause of that is a topic for another day. I also see this line in logs: Jun 15 13:36:57 d12566 libvirtd: 10424: warning : virKeepAliveTimerInternal:156 : No response from client 0x1600420 after 5 keepalive messages in 31 seconds Is it possible to monitor the keepAlive thing via command-line ? (as a nagios check). I know that I can poll for that line in the logs but is there a better way? I couldn't find any option in virsh to do a KeepAli...

...7: error : virNetSocketReadWire:1613 : End of file while reading data: Input/output error > 2016-03-03 19:23:29.247+0000: 14486: error : virConnectUnregisterCloseCallback:1282 : Requested operation is not valid: A different callback was requested > 2016-03-03 19:24:49.521+0000: 14487: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout > 2016-03-03 19:25:17.043+0000: 14486: error : virConnectUnregisterCloseCallback:1282 : Requested operation is not valid: A different callback was requested > 2016-03-03 19:25:47.110+0000: 14487: error : virNetSocketReadWire:161...

...virEventPollDispatchTimeouts:432 : Dispatch 2 2018-11-13 14:21:39.942+0000: 95205: info : virEventPollDispatchTimeouts:455 : EVENT_POLL_DISPATCH_TIMEOUT: timer=2 2018-11-13 14:21:39.942+0000: 95205: info : virObjectRef:296 : OBJECT_REF: obj=0x561dca9e7b60 2018-11-13 14:21:39.942+0000: 95205: info : virKeepAliveTimerInternal:136 : RPC_KEEPALIVE_TIMEOUT: ka=0x561dca9e7b60 client=0x561dca9e6e60 countToDeath=5 idle=5 2018-11-13 14:21:39.942+0000: 95205: debug : virNetMessageNew:46 : msg=0x561dca9e2880 tracked=0 2018-11-13 14:21:39.942+0000: 95205: debug : virNetMessageEncodePayloadEmpty:492 : Encode length as 28 2018-11-1...