I'll take this opportunity to share a classic: https://beza1e1.tuxen.de/lore/high_tide.html
"Its high tide!"
Which was met with blank looks and probably a wavering hand over the intercom to Security.
"It stops working at high tide"
I'll take this opportunity to share a classic: https://beza1e1.tuxen.de/lore/high_tide.html
"Its high tide!"
Which was met with blank looks and probably a wavering hand over the intercom to Security.
"It stops working at high tide"
Can't send mails to destinations too far away? https://web.mit.edu/jemorris/humor/500-miles
Reminds me of this: https://unix.stackexchange.com/questions/405783/why-does-man-print-gimme-gimme-gimme-at-0030
I have a cron job that has been failing since I added it. I'll get around to fixing it at some point.
Loved the replies. Once it’s over (that’s the hard part), everyone has a funny story to tell!
Mine was a race condition in an outsourced core system that showed up about six months after release, only when enough transactions hit at the same moment. The contact centre was on fire, with people calling non-stop.
Same lesson as yours: when something fails only sometimes, stop staring at the code and look at what else is running at that moment.
That's why I uses systemd timers with RandomizeDelay. Spreads the load a but
all 9 comments