Cron jobs & systemd timers fail silently #3
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We don't get any notifications for failed cron jobs, so we can't fix things like e.g. LE certs not updating
Moved from https://gitlab.com/kosmos/chef/issues/21
Cron jobs fail silentlyto Cron jobs & systemd timers fail silentlyWe're using systemd timers to run certbot, so now this issue is about both cron jobs and system timers. I'm going to work on that one
After having implemented the email notifications, this issue needs updating about which cron jobs and timers are left, that can fail silently.
I checked on barnard and andromeda, the only cron job is backup (already notifies on failures/warnings) and the certbot timer is the only one that I found that needs email notifications. Closing this one