Univention Bugzilla – Bug 38140
Logrotate error because of duplicate entry for connector-tracebacks.log
Last modified: 2018-04-11 13:49:38 CEST
When univention-s4-connector and univention-ad-connector are installed at the same time, logrotate produces the following error and sends a daily email message to root:
# logrotate /etc/logrotate.conf
error: univention-s4-connector:11 duplicate log entry for /var/log/univention/connector-tracebacks.log
error: found error in /var/log/univention/connector-tracebacks.log , skipping
This is caused by a duplicate entry for /var/log/univention/connector-tracebacks.log in both connectors.
I was able to reproduce the error with UCS 3.2-5. In UCS 4.0 the very same logrotate configuration is used.
Created attachment 8060 [details]
Patch for logrotate conffiles of univention-ad-connector and univention-s4-connector
Created attachment 8064 [details]
Hmm, where did you get those file names from? I just grepped through the source code for the term "tracebacks" and it turns out that neither univention-ad-connector nor univention-s4-connector write this file "connector-tracebacks.log" any longer. I would propose the attached patch instead. If you agree we should clone this bug to do the same for univention-ad-connector.
The duplicate entry has a much more severe impact than just the error messages in the mail. The whole file `/etc/logrotate.d/univention-s4-connector` is ignored due to that error. The result is that the logs from the S4 connector aren't rotated at all.
I just noticed this on a system where the S4 connector's log file was > 10 GB in size.
18a8f128fb | fix
6591356ac9 | Advisory
56c27621f6 | Advisory version
OK - logrotate
OK - YAML