=== not_phunyguy is now known as phunyguy === scoobydoob is now known as scoobydoo === Thumpxr8 is now known as Thumpxr === ajfriesen2 is now known as ajfriesen === zareem3 is now known as zareem === philroche_ is now known as philroche === diddledani_ is now known as diddledani === rafaeldtinoco_ is now known as rafaeldtinoco === odc_ is now known as odc === teward_ is now known as teward === E_Eickmeyer is now known as Eickmeyer === cwaydt4 is now known as cwaydt === polymorp- is now known as polymorphic === Morpheus is now known as Mekaneck [12:56] hmm wasn't there a systemd channel [12:56] anyway uh, so we have this timer but it never seems to run properly [12:57] and we can't figure out why [12:59] turn it off, systemctl clean --what=state misbehaving.timer, then turn it on again? [13:06] does systemctl list-timers list it? [13:07] what does systemctl status misbehaving.timer say, is it active? [13:07] + loaded + enabled [13:08] do you have pending jobs? systemctl list-jobs [13:08] does systemd think the system is fully booted up? systemctl is-system-running [13:08] Soni: ^ [13:08] it previously had Active: active (running) since Sun 2021-07-04 15:29:10 UTC; 2 months 30 days ago [13:08] Trigger: n/a [13:09] now it has Trigger: Mon 2021-10-04 00:00:57 UTC; 11h left [13:09] whatever cleaning the state did, this looks promising [13:10] maybe the system wasn't fully 'running' when you queried the first time [13:11] ● lavabit State: running Jobs: 0 queued Failed: 0 units [13:12] this is what status showed when we queried it the first time [13:19] hmm, okay, so the system was considered runnnig, i guess [13:20] it was possibly a corrupted timer state, but there was no indication of it === xnox1 is now known as xnox