[12:56] <Soni> hmm wasn't there a systemd channel
[12:56] <Soni> anyway uh, so we have this timer but it never seems to run properly
[12:57] <Soni> and we can't figure out why
[12:59] <Soni> turn it off, systemctl clean --what=state misbehaving.timer, then turn it on again?
[13:06] <tomreyn> does    systemctl list-timers    list it?
[13:07] <tomreyn> what does    systemctl status misbehaving.timer    say, is it active?
[13:07] <tomreyn> + loaded + enabled
[13:08] <tomreyn> do you have pending jobs?    systemctl list-jobs
[13:08] <tomreyn> does systemd think the system is fully booted up?    systemctl is-system-running
[13:08] <tomreyn> Soni: ^
[13:08] <Soni> it previously had      Active: active (running) since Sun 2021-07-04 15:29:10 UTC; 2 months 30 days ago
[13:08] <Soni>     Trigger: n/a
[13:09] <Soni> now it has     Trigger: Mon 2021-10-04 00:00:57 UTC; 11h left
[13:09] <Soni> whatever cleaning the state did, this looks promising
[13:10] <tomreyn> maybe the system wasn't fully 'running' when you queried the first time
[13:11] <Soni> ● lavabit    State: running     Jobs: 0 queued   Failed: 0 units
[13:12] <Soni> this is what status showed when we queried it the first time
[13:19] <tomreyn> hmm, okay, so the system was considered runnnig, i guess
[13:20] <Soni> it was possibly a corrupted timer state, but there was no indication of it