49
How do you handle cron jobs that silently stop working? (lemmy.world)
submitted 3 months ago by to c/programming@programming.dev
15 comments fedilink hide all child comments
 

Had a backup script running via cron for months. Worked fine until it didn't — turns out the disk filled up three weeks ago and the job started failing silently. Nobody noticed until we actually needed a restore.

The obvious answer is "check your logs" but let's be honest, nobody's reading cron logs daily for 15 different scheduled tasks across 4 servers.

What's your setup for making sure crons are actually completing? Do you just grep logs periodically, or do you have something more structured? Curious how others handle this without turning it into a whole project.

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 3 months ago (1 child)

I think the real obvious question is, why aren't you monitoring your disk space?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 3 points 3 months ago

    Can’t answer for them, but I can explain a similar situation I ran into:

    Large external RAID I was using for telescoping backups with a restic cron job. Didn’t want to have it on all the time cuz it was noisy, so I put it on a smart plug and had it turn on and off as part of the job.

    I really wanted a set of backup rules that worked like… “always a full snapshot of current state, plus as much of the following as will fit into the destination: daily for the past 7 days, weekly for the past 4 weeks, monthly for the rest until full” …but restic doesn’t (or didn’t) support that kind of dynamic rule set.

    I tried to estimate it programmatically, but it never worked 100% and I frequently ran into out of space errors.

    But of course, I never saw the actual disk usage in my day-to-day, because the RAID was only on at like 4 AM.

  • permalink
  • fedilink
  • source
  • parent