# logrotate allows to use only year, month, day and unix epoch
dateformat -%Y%m%d-%s
But dateext directive from /etc/logrotate.conf is not inherited.
So dateformat doesn't work.
Because of this we still see on some customer's installations errors like these:
error: error creating output file /var/log/remote/10.189.168.10/nailgun-agent.log.1: File exists
error: error creating output file /var/log/remote/10.189.168.19/CRON.log.1: File exists
To avoid it we need to add deteext /etc/logrotate.d/fuel.nodaily both on fuel master and slave nodes:
# logrotate allows to use only year, month, day and unix epoch
dateext
dateformat -%Y%m%d-%s
In /etc/logrotate. d/fuel. nodaily we have this:
# logrotate allows to use only year, month, day and unix epoch
dateformat -%Y%m%d-%s
But dateext directive from /etc/logrotate.conf is not inherited. remote/ 10.189. 168.10/ nailgun- agent.log. 1: File exists remote/ 10.189. 168.19/ CRON.log. 1: File exists
So dateformat doesn't work.
Because of this we still see on some customer's installations errors like these:
error: error creating output file /var/log/
error: error creating output file /var/log/
To avoid it we need to add deteext /etc/logrotate. d/fuel. nodaily both on fuel master and slave nodes:
# logrotate allows to use only year, month, day and unix epoch
dateext
dateformat -%Y%m%d-%s
All versions 6.1-9.0 are affected.