How not to handle an error condition
-
So yesterday my server starts beeping. Once every half hour. I checked the logs, no errors. Woke up this morning and it was beeping every second continuously. Thinking it's overheating I shut it down. Break open the IBM Maintenance manual for POST diagnostic beeps. Nothing listed. I happen to unplug both ethernet cables and rebooted and it stops. Plug one in, it starts again. Great, my on-board gigabit ethernet controller must be getting ready to fail. Call IBM and the technician's baffled. On one of the many reboots, I catch a small tray icon that seems to be blinking in sync with the beeps. Look in process explorer and it's a Dynamic DNS update program that's failed and the idiot that programmed it didn't think to write a message to the event log, pop up a message or write a log file and instead chose to beep the bleeping speaker! Okay, blood pressure's just getting back to normal now. uninstall
-
So yesterday my server starts beeping. Once every half hour. I checked the logs, no errors. Woke up this morning and it was beeping every second continuously. Thinking it's overheating I shut it down. Break open the IBM Maintenance manual for POST diagnostic beeps. Nothing listed. I happen to unplug both ethernet cables and rebooted and it stops. Plug one in, it starts again. Great, my on-board gigabit ethernet controller must be getting ready to fail. Call IBM and the technician's baffled. On one of the many reboots, I catch a small tray icon that seems to be blinking in sync with the beeps. Look in process explorer and it's a Dynamic DNS update program that's failed and the idiot that programmed it didn't think to write a message to the event log, pop up a message or write a log file and instead chose to beep the bleeping speaker! Okay, blood pressure's just getting back to normal now. uninstall
cheap programming, cheap labor :(
Member number three million seven hundred seventy two thousand nine hundred sixty three
-
So yesterday my server starts beeping. Once every half hour. I checked the logs, no errors. Woke up this morning and it was beeping every second continuously. Thinking it's overheating I shut it down. Break open the IBM Maintenance manual for POST diagnostic beeps. Nothing listed. I happen to unplug both ethernet cables and rebooted and it stops. Plug one in, it starts again. Great, my on-board gigabit ethernet controller must be getting ready to fail. Call IBM and the technician's baffled. On one of the many reboots, I catch a small tray icon that seems to be blinking in sync with the beeps. Look in process explorer and it's a Dynamic DNS update program that's failed and the idiot that programmed it didn't think to write a message to the event log, pop up a message or write a log file and instead chose to beep the bleeping speaker! Okay, blood pressure's just getting back to normal now. uninstall
quick, do a C++/MFC forum search for "Urgent How I Beep?". shouldn't take more than a couple of seconds to find the culprit.
-
So yesterday my server starts beeping. Once every half hour. I checked the logs, no errors. Woke up this morning and it was beeping every second continuously. Thinking it's overheating I shut it down. Break open the IBM Maintenance manual for POST diagnostic beeps. Nothing listed. I happen to unplug both ethernet cables and rebooted and it stops. Plug one in, it starts again. Great, my on-board gigabit ethernet controller must be getting ready to fail. Call IBM and the technician's baffled. On one of the many reboots, I catch a small tray icon that seems to be blinking in sync with the beeps. Look in process explorer and it's a Dynamic DNS update program that's failed and the idiot that programmed it didn't think to write a message to the event log, pop up a message or write a log file and instead chose to beep the bleeping speaker! Okay, blood pressure's just getting back to normal now. uninstall
Immortalize it in the Coding Horrors forum.