Bug#811473: systemd: timer with WakeSystem=yes doesn't always start the service it's supposed to trigger

[Michael Biebl]

Am 19.01.2016 um 10:36 schrieb Christian Pernegger:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
> 
> 
> Hello,
> 
> I'm trying to do the following:
> 1) wake up the system every night at 3 am (using a timer unit with WakeSystem=yes)
> 2) pull in backups (using a service triggered by the timer unit)
> 3) send it to sleep again (via logind idle timeout)
> 
> See attached files backup.timer and backup.service.
> 
> Now, step 1 works, it'll always wake up at 3 am, and sometimes
> backup.service will then run as it should, sometimes it won't.
> 
> (For completeness' sake: starting backup.service manually always
> works, as does running it on a timer when the machine is already
> up. Same goes for suspend on idle.)
> 
> It might be some kind of timing issue but frankly I've no idea where
> to look. The journal doesn't show anything about the timer unit in any
> case, the service unit does get mentioned only because a sudo session
> is opened for it (only when it actually runs).
> 


Christian, can you show me the output of
systemctl status backup.service
after such a wakeup and failed attempt to start the service?
What would probably useful as well is to increase the log level of
systemd (systemd-analyze set-log-level debug) and get a journal log from
after the wakeup.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171108/293bed34/attachment-0002.sig>