Bug 755548 - VDSM: use standard log location of /var/log/libvirt/libvirtd.log
Summary: VDSM: use standard log location of /var/log/libvirt/libvirtd.log
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Douglas Schilling Landgraf
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 13:00 UTC by Omri Hochman
Modified: 2013-07-28 14:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-28 14:36:37 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 14842 0 None None None Never

Description Omri Hochman 2011-11-21 13:00:20 UTC
VDSM: configure libvirtd.log rotate to /var/log/libvirt/ instead to /var/log/

[root@red-vds3 yum.repos.d]# cat /etc/logrotate.d/libvirtd
# vdsm
/var/log/libvirtd.log {
    rotate 100
    missingok
    copytruncate
    size 15M
    compress
    compresscmd /usr/bin/xz
    uncompresscmd /usr/bin/unxz
    compressext .xz
}
# end vdsm
/var/log/libvirt/libvirtd.log {
        weekly
        missingok
        rotate 4
        compress
        delaycompress
        copytruncate
        minsize 100k
}

root@red-vds3 log]# ls
anaconda.log          dmesg.old                 libvirtd.log-20110314.gz  libvirtd.log.30.xz  libvirtd.log.50.gz  libvirtd.log.61.gz  libvirtd.log.72.gz  libvirtd.log.83.gz  libvirtd.log.95.gz  secure-20111106
anaconda.program.log  dracut.log                libvirtd.log-20110315.gz  libvirtd.log.31.xz  libvirtd.log.50.xz  libvirtd.log.61.xz  libvirtd.log.72.xz  libvirtd.log.83.xz  libvirtd.log.96.gz  secure

Comment 2 Dan Kenigsberg 2011-11-21 13:19:10 UTC
Vdsm currently configures libvirt server to log to /var/log/libvirtd.log.
Recently, libvirt comes out of the box logging to /var/log/libvirt/libvirtd.log. Vdsm should better be using the defaults.


Note You need to log in before you can comment on or make changes to this bug.