Univention Bugzilla – Bug 56915
duplicate logrotate entry if Microsoft 365 connector is installed
Last modified: 2024-04-25 10:41:48 CEST
When the Microsoft 365 Connector is installed, there are now two entries referring to a specific logfile. Therefore the `logrotate.service` unit fails: Dec 15 00:00:02 callisto systemd[1]: Starting Rotate log files... Dec 15 00:00:02 callisto logrotate[28118]: error: univention-ms-office-async:11 duplicate log entry for /var/log/univention/listener_modules/ms-office-async.log Dec 15 00:00:02 callisto logrotate[28118]: error: found error in file univention-ms-office-async, skipping Dec 15 00:00:03 callisto systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE The conflicting entries are: univention-ms-office-async 11:/var/log/univention/listener_modules/ms-office-async.log { listener-modules 11:/var/log/univention/listener_modules/*.log { [0 root@callisto ~] univention-app info UCS: 5.0-6 errata713 Installed: dhcp-server=12.0 keycloak=22.0.3-ucs1 office365=5.8 self-service=5.0 Upgradable:
And another customer has a failed logrotate service caused by the two logrotate entries for the logfiles of /var/log/univention/listener_modules/ms-office-async.log Please fix.
And another customer with that problem. Please fix. Can lead into full disks as logrotate is completely not working caused by that bug.
The partner has two other customers, who are affected by this issue.
Fixed with v5.9.