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

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 trigge

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

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 trigge

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

Am 08.11.2017 um 20:21 schrieb Alberto Manzaneque García: > I have the same problem too on version 234. > Do you know if there is a systemd (not debian) bug open? > > On Sat, 25 Feb 2017 16:35:20 +0200 (EET) Madis Janson > wrote: >> >> I have exactly the same problem with D

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

I have the same problem too on version 234. Do you know if there is a systemd (not debian) bug open? On Sat, 25 Feb 2017 16:35:20 +0200 (EET) Madis Janson wrote: > > I have exactly the same problem with Debian Stretch (testing) on amd64. > Package version is 232-15. > > $ systemctl --version > sy

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

I have exactly the same problem with Debian Stretch (testing) on amd64. Package version is 232-15. $ systemctl --version systemd 232 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN The system wakes, b

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

Alright, I'm giving up on this. A timer with "WakeSystem=yes" will consistently wake this system from suspend, whether it will then execute that same timer's payload is quite another matter. I had it running for ~2 months, thought I'd cracked it, now it's stopped working entirely (still wakes up e

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

Hello, it seems like 216 has a change that might affect this, namely giving OnCalendar-timers an implicit After-dependency on time-sync.target. (The changelog and most documentation says timeR-sync.target, but Debian's 215 at least doesn't have that.) Easy enough to add manually, but it would be n

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

Hello again, I just wanted to document a few further observations & things I tried: * A dummy timer that just sent me mail every hour (but otherwise configured identically) managed to wake the system up 20 out of 20 times and did send mail on 18 of these. Sadly, with the backup.service the track