MySQL Failure Following Windows Server 2003 Re-boot

I've just experienced two completely independent, unrelated servers with totally different web-applications reboot and unable to start the MySQL service, one on 1st April, second on 2nd April. Coincidence? Probably. Is there a Microsoft Windows 2003 server patch killing MySQL? Not found any other incidences being Googled... let's see if anyone finds this post also experiencing the same thing...

UPDATE: This appears to have been triggered by a fire at BT on March 31st.

Timeline:

  • 31 March 2010 07:30 hrs fire crews attended the fire at BT Exchange in Paddington, caused by an electrical fault. According to Gradwell, a business ISP, 437 local exchanges and up to 37,500 Datastream circuits have been affected. It said the fire was having nationwide repercussions on communications - http://www.theregister.co.uk/2010/03/31/burne_house_burns/
    • It was speculated that the systems would not be back to normal until Tuesday the 6th of April 2010.
    • The BBC was alerted to the fault by IT consultant Jerry Sanders, who said customers as far afield as Potters Bar, Hertfordshire and Nottingham were reporting problems with Pipex UK broadband coverage.
  • The exchange was flooded for some time and power was not returned until the following morning when the traffic was re-routed.
  • 01 April 2010 09:30 the traffic from the Paddington exchange finally makes it out along the re-routed options and hits our servers.
    • BT said in an updated statement issued at 8:30am this morning. "Customers in other parts of the country may also be affected."
    • Looks like this led to a flux of requests all at the SAME TIME when service resumed, causing MySQL to process lots of requests at once, delaying other requests, which they added to the delay and the servers snowballed into a frozen mess of MySQL connections

Comments

Popular posts from this blog

Installing LAMP Apache/MySQL/PHP on Chromebook/Chromebox

Installing Ubuntu Linux on your ChromeBox/ChromeBook

Changing your Mac OSX Terminal's default text editor