Description of problem: "/etc/logrotate.d/libvirtd" file is having multiple entries of "/var/log/libvirt/libvirtd.log" after upgrading the host to "rhev-hypervisor6-6.5-20140603.2" version. # cat /etc/logrotate.d/libvirtd ## beginning of configuration section by vdsm /var/log/libvirt/libvirtd.log { rotate 100 missingok copytruncate size 15M compress compresscmd /usr/bin/xz uncompresscmd /usr/bin/unxz compressext .xz } ## end of configuration section by vdsm /var/log/libvirt/libvirtd.log { weekly missingok rotate 4 compress delaycompress copytruncate minsize 100k } Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20140603.2 How reproducible: 100% Steps to Reproduce: 1. Upgrade the host to rhev-hypervisor6-6.5-20140603.2 version 2. Then open "/etc/logrotate.d/libvirtd" file to see the multiple similar entries. Actual results: Multiple similar entries are available under "/etc/logrotate.d/libvirtd" file after the host upgrade to rhev-hypervisor6-6.5-20140603.2 version. Expected results: Multiple entries should not be there.
Hi Udayendu, Please update the knowledge base that we must keep the below configuration the other should be commented. ## beginning of configuration section by vdsm /var/log/libvirt/libvirtd.log { rotate 100 missingok copytruncate size 15M compress compresscmd /usr/bin/xz uncompresscmd /usr/bin/unxz compressext .xz } Thanks!
*** Bug 1115357 has been marked as a duplicate of this bug. ***
Created attachment 916715 [details] libvirtd.conf from host1
Created attachment 916716 [details] libvirtd.conf from host2
*** Bug 1080107 has been marked as a duplicate of this bug. ***
Same problems after update from: RHEV-H 6.5 20140407.0.el6ev to: RHEV-H 6.5 20140624.0.el6ev Problems: 1. Multiple entries of libvirtd.log in logrotate config 2. Bad location of libvird.log (which is in /var/log, but logrotate's destination is /var/log/libvirtd/ after update). I think second problem is not related to this BZ and it was commented in BZ#1080107 (marked as duplicate of this BZ). Info from old (20140407.0.el6ev) version: [root@lbch-02 ~]# 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@lbch-02 ~]# cat /etc/libvirt/libvirtd.conf |grep log_outputs # log_outputs="3:syslog:libvirtd" log_outputs="1:file:/var/log/libvirtd.log" Info from new (20140624.0.el6ev) version: [root@lbch-01 ~]# cat /etc/logrotate.d/libvirtd ## beginning of configuration section by vdsm /var/log/libvirt/libvirtd.log { rotate 100 missingok copytruncate size 15M compress compresscmd /usr/bin/xz uncompresscmd /usr/bin/unxz compressext .xz } ## end of configuration section by vdsm ## beginning of configuration section by vdsm /var/log/libvirt/libvirtd.log { rotate 100 missingok copytruncate size 15M compress compresscmd /usr/bin/xz uncompresscmd /usr/bin/unxz compressext .xz } ## end of configuration section by vdsm /var/log/libvirt/libvirtd.log { weekly missingok rotate 4 compress delaycompress copytruncate minsize 100k } [root@lbch-01 ~]# cat /etc/libvirt/libvirtd.conf |grep log_outputs # log_outputs="3:syslog:libvirtd" log_outputs="1:file:/var/log/libvirtd.log" On updated host (lbch-01, version 20140624.0.el6ev) libvirtd.log is not rotated and /var/log partition was completely filled in 3 days after update...
tried to verify when upgrading from rhevh-6.5-20140603.2 to rhev-hypervisor6-6.5-20140821.1.el6ev.noarch.rpm and i still have 2 same vdsm entries in /etc/logrotate.d/libvirtd i will attach all the logs and confs in case you need something more than libvirtd.conf
Created attachment 930575 [details] logs
Created attachment 930576 [details] etc
sorry, i didn't realize upgrade actually failed, now that upgrade passed config is correct
(In reply to movciari from comment #15) > sorry, i didn't realize upgrade actually failed, now that upgrade passed > config is correct Ok, nice!
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. http://rhn.redhat.com/errata/RHBA-2014-1152.html