=== chris14_ is now known as chris14
=== cpaelzer_ is now known as cpaelzer
[14:09] <Odd_Bloke> Hey folks, I have a jammy system with a few timers which aren't triggering their services when expected.  man-db and apt-daily are a couple of affected examples.  The timers are enabled and "active (waiting)", and the corresponding unit files are loaded.  I'm not really sure how to debug what's going on, does anyone have any suggestions?
=== TheCaptain8985 is now known as TheCaptain898
[17:06] <teward> server team, i forget, where do we have documentation for the NGINX package for our team/devel?  I have details about the nginx-abi definition that we should be aware of for the Future.
[17:06] <teward> cc bryceh rbasak 
[17:14] <sdeziel> Odd_Bloke: dunno if you've already checked but `.timer` units also have their logs you can consult with: `journalctl -u apt-daily.timer`
[17:19] <teward> (answered my own question, see https://wiki.ubuntu.com/ServerTeam/NGINX#NGINXABI )
[17:37] <Odd_Bloke> sdeziel: I have, yeah: it has a single "Started Daily apt download activities." log message (which is the name of both the timer and the service, confusingly) from right after boot, and that's it. ;.;
[17:39] <sdeziel> Odd_Bloke: are there any clues in the corresponding `.service` file?
[17:52] <Odd_Bloke> sdeziel: There's not really anything common between the various units that aren't running, that I can see.  (Some of them are ConditionACPower=true, but there are no `/sys/class/power_supply` devices on this machine.)
[18:03] <sdeziel> Odd_Bloke: `systemctl status <>` on the `.timer` and `.service` will tell you if a `Condition*=` was not met. `systemctl list-timer` will give you an overview of when those timers will/have fired. I can't think of other ways to debug this, sorry :/
[18:04] <sdeziel> `systemctl status <unit>`*