Here is the failure and work around by hiding one of the
/etc/logrotate.d/could* files.
# systemctl --state=failed |grep logrotate
● logrotate.service loaded failed failed Rotate log files
# cd /etc/logrotate.d
# ### Hiding the file via the fact that RCS directories are often avoided
# pwd
/etc/logrotate.d
# mkdir RCS
# mv cloud-init-base RCS/cloud-init-base.2025-03-28 # Keep the file date :-)
# ls -l /etc/logrotate.d/{*/,}cloud*
-rw-r--r-- 1 root root 144 Mar 28 2025
/etc/logrotate.d/RCS/cloud-init-base.2025-03-28
-rw-r--r-- 1 root root 144 Apr 5 2024 /etc/logrotate.d/cloud-init
#
# systemctl reset-failed logrotate.service
# systemctl start logrotate.service
# systemctl status logrotate.service # and now shows good :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089790
Title:
Duplicate logrotate configurations cause errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2089790/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs