Re: [libvirt-users] libvirtd hangs

2018-01-17 Thread Ján Tomko
On Thu, Jan 18, 2018 at 11:30:16AM +0700, Artem Likhachev wrote: Hello everybody! We have a cluster of servers managed by VMmanager 5 KVM (by ispsystem). A typical node: # cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) # uname -r 3.10.0-693.11.6.el7.x86_64 # rpm -qa |grep libvir

Re: [libvirt-users] Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats

2018-01-17 Thread Ján Tomko
On Wed, Jan 17, 2018 at 04:45:38PM +0200, Serhii Kharchenko wrote: Hello libvirt-users list, We're catching the same bug since 3.4.0 version (3.3.0 works OK). So, we have process that is permanently connected to libvirtd via socket and it is collecting stats, listening to events and control the

[libvirt-users] libvirtd hangs

2018-01-17 Thread Artem Likhachev
Hello everybody! We have a cluster of servers managed by VMmanager 5 KVM (by ispsystem). A typical node: # cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) # uname -r 3.10.0-693.11.6.el7.x86_64 # rpm -qa |grep libvirt libvirt-daemon-driver-qemu-3.7.0-1.el7.centos.x86_64 libvirt-dae

Re: [libvirt-users] Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats

2018-01-17 Thread Serhii Kharchenko
2018-01-17 18:38 GMT+02:00 Serhii Kharchenko >: 2018-01-17 17:32 GMT+02:00 Michal Privoznik mailto:mpriv...@redhat.com>>: Sounds like qemuConnectGetAllDomainStats() forgot to unset the job on a domain. Can you please attach gdb to libvirtd a

Re: [libvirt-users] Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats

2018-01-17 Thread Serhii Kharchenko
2018-01-17 17:32 GMT+02:00 Michal Privoznik : > Sounds like qemuConnectGetAllDomainStats() forgot to unset the job on a > domain. Can you please attach gdb to libvirtd and run 't a a bt' and > share the output? > > Michal > This is output of gdb 't a a bt' ~5 seconds after that error message app

Re: [libvirt-users] Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats

2018-01-17 Thread Michal Privoznik
On 01/17/2018 03:45 PM, Serhii Kharchenko wrote: > Hello libvirt-users list, > > We're catching the same bug since 3.4.0 version (3.3.0 works OK). > So, we have process that is permanently connected to libvirtd via socket > and it is collecting stats, listening to events and control the VPSes. >

[libvirt-users] Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats

2018-01-17 Thread Serhii Kharchenko
Hello libvirt-users list, We're catching the same bug since 3.4.0 version (3.3.0 works OK). So, we have process that is permanently connected to libvirtd via socket and it is collecting stats, listening to events and control the VPSes. When we try to 'shutdown' a number of VPSes we often catch th