Univention Bugzilla – Bug 33529
cron.daily mails harmless logrotate errors to admin
Last modified: 2013-12-12 11:29:51 CET
After upgrading my 3.1 UCS test server to 3.2, I'm getting messages with the following content in my mailbox: /etc/cron.daily/logrotate: error: univention-samba4:38 duplicate log entry for /var/log/samba/log.smbd error: found error in /var/log/samba/log.smbd , skipping error: univention-samba4:49 duplicate log entry for /var/log/samba/log.nmbd error: found error in /var/log/samba/log.nmbd , skipping error: winbind:1 duplicate log entry for /var/log/samba/log.winbindd error: found error in /var/log/samba/log.winbindd , skipping I think this is caused by /var/log/samba/log.smbd, /var/log/samba/log.nmbd and /var/log/samba/log.winbindd being configured to be logrotated in two files: /etc/logrotate.d/samba and /etc/logrotate.d/univention-samba4 (for log.smbd and log.nmbd), and /etc/logrotate.d/winbindd and /etc/logrotate.d/univention-samba4 (for log.winbindd). I suppose the bug can be solved by removing one of the logrotate configurations for each file.
I can confirm that, the very same error mail on a UCS DC Master installed with UCS 3.1/Samba4 and updated to UCS 3.2.
/etc/logrotate.d/samba and /etc/logrotate.d/winbind are config templates of univention-samba4 with the appropriate settings. -> logrotate -f /etc/logrotate.conf runs fine after the Update YAML: errata/2013-11-20-univention-samba4.yaml univention-samba4: 3.0.39-6.562.201312021513
Ok: * logrotate.d subfiles shipped by samba are now diverted and replaced by UCR templates * Advisory is ok.
http://errata.univention.de/ucs/3.2/6.html