Red Hat Bugzilla – Bug 968062
No libvirtd log file
Last modified: 2013-06-12 15:38:28 EDT
Description of problem:
Installed Fedora 19 beta from DVD. Tried to use virsh and got an error. Went to debug and found there is no libvirtd.log file.
# virsh iface-bridge enp0s25 br0 --no-stp
error: An error occurred, but the cause is unknown
# ls /var/log/libvirt
libxl lxc qemu uml
I tried restarting libvirtd.
I removed libvirt and reinstalled it. Nothing helps.
Version-Release number of selected component (if applicable):
It only happened once. This didn't happen on my other F19 Beta system. But that was installed with fedup from F18. Not from the DVD.
I asked eblake for advice and confirmed this happened to him too.
I confirmed that libvirtd is running.
# systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Tue 2013-05-28 18:55:13 EDT; 18s ago
Main PID: 6058 (libvirtd)
├─1173 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
May 28 18:55:13 dhcp-185-41.bos.redhat.com systemd: Starting Virtualization daemon...
May 28 18:55:13 dhcp-185-41.bos.redhat.com systemd: Started Virtualization daemon.
May 28 18:55:16 dhcp-185-41.bos.redhat.com dnsmasq: read /etc/hosts - 2 addresses
May 28 18:55:16 dhcp-185-41.bos.redhat.com dnsmasq: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
May 28 18:55:16 dhcp-185-41.bos.redhat.com dnsmasq-dhcp: read /var/lib/libvirt/dnsmasq/default.hostsfile
Steps to Reproduce:
1. Install Fedora 19
2. service libvirtd start
3. find /var -name libvirtd
No file found
[root@dhcp-185-41 /]# find /var -name libvirtd
Able to debug by looking in libvirtd.log file.
> How reproducible:
> It only happened once. This didn't happen on my other F19 Beta system. But
> that was installed with fedup from F18. Not from the DVD.
This statement is incorrect. My other system has no libvirtd.log file either.
[root@virtlab213 ~]# rpm -q libvirt
[root@virtlab213 ~]# ls /var/log/libvirt
libxl lxc qemu uml
[root@virtlab213 ~]# find / -name libvirtd*
[root@virtlab213 ~]# ls -lad /var
drwxr-xr-x. 18 root root 4096 May 28 12:51 /var
[root@virtlab213 ~]# ls -lad /var/log
drwxr-xr-x. 11 root root 4096 May 28 13:23 /var/log
[root@virtlab213 ~]# ls -lad /var/log/libvirt
drwx------ 6 root root 4096 May 3 14:04 /var/log/libvirt
[root@virtlab213 ~]# ls -lad /var/log/libvirt/*
drwx------ 2 root root 4096 May 28 13:23 /var/log/libvirt/libxl
drwx------ 2 root root 4096 May 3 14:04 /var/log/libvirt/lxc
drwx------ 2 root root 4096 May 28 14:09 /var/log/libvirt/qemu
drwx------ 2 root root 4096 May 3 14:04 /var/log/libvirt/uml
Is this just a case of systemd redirecting the log to somewhere else, instead of its traditional location?
On my rawhide system libvirt messages are ending up in /var/log/messages
AFAIK libvirtd logs just warnings and errors through syslog (and perhaps journald on systemd-based systems). Logging to /var/log/libvirtd.log needs to be configured manually if desired.
(In reply to Jiri Denemark from comment #4)
> AFAIK libvirtd logs just warnings and errors through syslog (and perhaps
> journald on systemd-based systems). Logging to /var/log/libvirtd.log needs
> to be configured manually if desired.
That's my understanding as well, I didn't know there was supposed to be a /var/log/libvirtd.log
Closing as NOTABUG, someone reopen if I'm wrong.
At some time in the past this config change was apparently present in the libvirtd.conf distributed with Fedora, as I recall having systems where it worked that way, and *don't* remember messing with libvirtd.conf to make it happen. (I should go back and look at that F13 disk before I recycle it...)
At any rate, I have no problem with this being NOTABUG.