Why do I see "init: libvirtd respawning too fast, stopped" errors in RHEL based RHEV hosts?
Issue
- After a RHEL based RHEV host has been rebooted the following errors are observed:
init: libvirtd respawning too fast, stopped
- Despite that
libvirtdis up and running and the PID at/var/run/libvirtd.pidmatches the PID of the existinglibvirtdprocess:
# ps -ef|grep -v grep|grep -i libvirt
root 6566 1 0 Aug05 ? 00:00:09 libvirtd --daemon --listen
# ls -al /var/run/lib*
-rw-r--r-- 1 root root 4 Aug 5 15:31 /var/run/libvirtd.pid
/var/run/libvirt:
total 20
drwxr-xr-x. 5 root root 4096 Aug 5 15:31 .
drwxr-xr-x. 23 root root 4096 Aug 5 16:38 ..
srwxrwx--- 1 root kvm 0 Aug 5 15:31 libvirt-sock
srwxrwxrwx 1 root kvm 0 Aug 5 15:31 libvirt-sock-ro
drwxr-xr-x. 2 root root 4096 Jan 10 2013 lxc
drwxr-xr-x. 2 root root 4096 Aug 5 15:31 network
drwx------. 2 root root 4096 Aug 5 09:28 qemu
# cat /var/run/libvirtd.pid
6566
- Shutting down
libvirtdservice succeeds:
# service libvirtd stop
Stopping libvirtd daemon: [ OK ]
# ps -ef|grep -v grep |grep libvirt
# ls -al /var/run/lib*
total 20
drwxr-xr-x. 5 root root 4096 Aug 6 07:56 .
drwxr-xr-x. 23 root root 4096 Aug 6 07:56 ..
drwxr-xr-x. 2 root root 4096 Jan 10 2013 lxc
drwxr-xr-x. 2 root root 4096 Aug 5 15:31 network
drwx------. 2 root root 4096 Aug 5 09:28 qemu
- After starting
libvirtdservice back the error is no longer observed but if the host is rebooted then the error happens again.
Environment
- Red Hat Enterprise Linux as a RHEV host.
libvirtdservice configured to start at boot.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
