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.

I've tried those example unit files (with v235) and got the following
error on wakeup:
Nov 08 22:43:15 pluto systemd[1]: backup.service: Main process exited,
code=exited, status=1/FAILURE
Nov 08 22:43:15 pluto systemd-inhibit[3709]: Failed to inhibit: The
operation inhibition has been requested for is already running
Nov 08 22:43:15 pluto systemd[1]: backup.service: Failed with result
'exit-code'.

I wonder if your problem is related to the usage of systemd-inhibit.

Can you try and run the shell script directly?

Btw, for a script/use case like yours, using Type=oneshot is probably
more suitable.

-- 
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/ffbcbad8/attachment-0002.sig>