Starting libvirtd with a configuration file containing an unterminated string for log_outputs causes libvirtd to exit silently.
After adding the following to libvirtd.conf
libvirtd, even when started from the commandline with -v, exited silently; nothing in the logs, nothing on stdout to indicate what was wrong.
Verified PASS with libvirt-0.9.4-5.el6, reproduced this bug with libvirt-0.9.4.4.el6.
# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: 05:10:16.742: 11484: info : libvirt version: 0.9.4, package: 5.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2011-08-22-12:26:05, x86-009.build.bos.redhat.com)
05:10:16.742: 11484: error : main:1394 : Can't load config file '/etc/libvirt/libvirtd.conf'
05:10:35.896: 11488: info : libvirt version: 0.9.4, package: 5.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2011-08-22-12:26:05, x86-009.build.bos.redhat.com)
05:10:35.896: 11488: error : main:1394 : Can't load config file '/etc/libvirt/libvirtd.conf'
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Error checks on early libvirtd startup did not report errors verbosely.
Broken configuration file or other early errors while libvirtd was starting up caused the daemon to exit silently only setting the process return value to indicate error.
This confused the users, as no message was printed and the process return code has to be checked manualy.
Error handling messages were added to the early start phases of libvirtd.
Errors during start are now printed and logged.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.