http://bugzilla.novell.com/show_bug.cgi?id=913421 --- Comment #10 from Vitezslav Cizek --- (In reply to Thomas Blume from comment #9)

(In reply to Dirk Weber from comment #8)

...

...

We can use something similar to your solution from comment 1. it works fine for me for months.

Yes, you should use monotonic timers in order to make systemd respecting the machine state (up or down). Otherwise they will just be triggered by the wallclock and if the system is down at this time they won't get startet.

You can find more details about monotonic timers in the systemd.timer manpage at the start of the Options section.

Concerning the question in comment#5, logrotate.service is statically enabled. This means it doesn't have an explicit [Install] section and therefore cannot be enabled manually (or via presets). It should be exclusively started by a timer unit.

Is logrotate correctly startet when you are using monotonic timers in the logrotate.timer unit?

It seems so, at least it's working fine for Dirk. This will solve the problem with systems that often go offline. However the main issue is that the timer is initially disabled. This is how it looks right after the update from 13.1 to 13.2: # systemctl status logrotate.timer logrotate.timer - Daily rotation of log files Loaded: loaded (/usr/lib/systemd/system/logrotate.timer; disabled) Active: inactive (dead) The timer is disabled for some reason. The daily logrotate is not triggered on 0:00. -- You are receiving this mail because: You are on the CC list for the bug.