BlackPearl02

6 ms·

1. 1.▲
   Ask HN: How do you catch cron jobs that "succeed" but produce wrong results?

   1 points by BlackPearl02 8mo ago|3 comments
2. 2.▲
   by BlackPearl02 8mo ago

   I've been running into this issue where my backup cron jobs "succeed" but create empty files. For example: Database backup cron runs, exit code 0, but creates a zero-byte dump file Disk space runs out mid-backup, leaving an e
3. 3.▲
   by BlackPearl02 8mo ago

   Ever had a critical cron job silently fail for days? I've seen backups stop running, cleanup scripts fail, and monitoring jobs die—all without any notification. This guide covers practical ways to detect cron failures before they becom
4. 4.▲
   by BlackPearl02 8mo ago

   Those are all solid practices! I use chronic too, and proper exit codes are essential. The gap I found is that even with all of that, you can still have "successful" jobs (exit code 0, no errors) that produce wrong results. Like a
5. 5.▲
   by BlackPearl02 8mo ago

   That's a clever approach! I used to do something similar, but found I'd miss emails or they'd get buried. The tool I built does something similar but automated - it watches for a ping after your job completes and can validate
6. 6.▲
   Monitor Cron Jobs Without Migration – DeadManPing(deadmanping.com)

   1 points by BlackPearl02 8mo ago|0 comments
7. 7.▲
   Ask HN: How do you verify cron jobs did what they were supposed to?

   8 points by BlackPearl02 8mo ago|9 comments