Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
/etc/logrotate.d/libvirtd on some hosts contains the same section multiple times, which means that the output of "logrotate /etc/logrotate.d/libvirtd" looks like this:
[root@north-06 ~]# logrotate /etc/logrotate.d/libvirtd
error: /etc/logrotate.d/libvirtd:14 duplicate log entry for /var/log/libvirtd.log
error: found error in /var/log/libvirtd.log , skipping
This means that every time cron runs logrotate (every 15 minutes), it sends an e-mail to root with the error it receives from logrotate.
Contents of /etc/logrotate.d/libvirtd:
[root@north-06 ~]# 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
# 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
}
/etc/logrotate.d/libvirtd is a file owned by libvirt package:
[root@test ~]# rpm -qf /etc/logrotate.d/libvirtd
libvirt-0.9.4-12.el6.x86_64
[root@test ~]# rpm -V libvirt
.M....... /var/cache/libvirt/qemu
[root@test ~]# cat /etc/logrotate.d/libvirtd
/var/log/libvirt/libvirtd.log {
weekly
missingok
rotate 4
compress
delaycompress
copytruncate
minsize 100k
}
[root@test ~]#
But as you can see its content contains only one entry and no comment about vdsm.
My guess is that the extra definitions are added by vdsm in some ways, and
the bug should be retargetted at this component,
Daniel
Didn't find a way to reproduce yet, but I have this issue on all my hosts.
yum remove vdsm / yum install vdsm makes /etc/logrotate.d/libvirtd go back to normal.
(In reply to comment #7)
> How do we test this?
try install/upgrade/uninstall ov vdsm and make sure that never ever do you get multiple "vdsm" stanzas in logrotate.d/libvirtd, and that no nagging email is sent due to vdsm installation.
(In reply to comment #8)
> (In reply to comment #7)
> > How do we test this?
>
> try install/upgrade/uninstall ov vdsm and make sure that never ever do you get
> multiple "vdsm" stanzas in logrotate.d/libvirtd, and that no nagging email is
> sent due to vdsm installation.
What about hosts that already have this problem? Does it fix it retroactively?
Either way, it is a bit too late to handle these minor details. If vdsm does not add multiple stanzas, that's good enough for 3.0. I wish I could take back my comment 10.
Upgraded from 106 to 107.
service vdsmd reconfigure does help. The file now looks like this and logrotate doesn't have any output.
[root@orange-vdsf ~]# 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
}
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/RHEA-2011-1782.html
/etc/logrotate.d/libvirtd on some hosts contains the same section multiple times, which means that the output of "logrotate /etc/logrotate.d/libvirtd" looks like this: [root@north-06 ~]# logrotate /etc/logrotate.d/libvirtd error: /etc/logrotate.d/libvirtd:14 duplicate log entry for /var/log/libvirtd.log error: found error in /var/log/libvirtd.log , skipping This means that every time cron runs logrotate (every 15 minutes), it sends an e-mail to root with the error it receives from logrotate. Contents of /etc/logrotate.d/libvirtd: [root@north-06 ~]# 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 # 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 }