1

For the 3rd time, my server where my MySQL instance is running simply shutdown unexpectedly, this time, causing my tables to be corrupt as I had ALTER statements running.

While in contact with my hosting company, they deny that it is a hardware failure (they have done test that showed no hardware failure) and says that MySQL uses up all resources which causes the server to just shutdown. In my mind, the MySQL instance would shutdown unexpectedly, not the server itself but maybe I'm wrong.

My question is simple. Could MySQL cause the server to shutdown unexpectedly?

There are nothing in the error logs of either the server, or MySQL. Just that the server had shutdown unexpectedly.

Has anyone had this problem where MySQL causes a unexpected server shutdown?

I found that a kernel-power error with event id 41 has been generated all 3 times the error has occured.

EventData 

  BugcheckCode 10 
  BugcheckParameter1 0xffffffff49bd9dc9 
  BugcheckParameter2 0x2 
  BugcheckParameter3 0x1 
  BugcheckParameter4 0xfffff80005ed80d8 
  SleepInProgress false 
  PowerButtonTimestamp 0 

Luckily, I've managed to find a minidump file, (only for the first time it happened thought) and I've decoded it to this.

IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.

Could this be that I've simply used up all available memory or is there maybe something wrong with the memory itself? I've just sent this details to the hosting company and I am awaiting answer but figured I would get some more opinions.

  • it may cause high resource utlization..high swap use ete causing hang of system..what is there in event logs or os logs? – Nawaz Sohail Jan 7 '15 at 14:07
  • reboot the server yes, due high resource usage – Ahmad Abuhasna Jan 7 '15 at 14:13
  • Nothing really, just that the server was shutdown unexpectedly. The previous system shutdown at 5:47:23 on ‎6-‎1-‎2015 was unexpected Eventid 6008 – Kay Nelson Jan 7 '15 at 14:14
  • @AhmadAbuhasna So that could be both CPU and MEMORY? Where could i find the trace for this? – Kay Nelson Jan 7 '15 at 14:14
  • 2
    I am extremely skeptical that MySQL Server is causing Windows to completely shut down without leaving a trace. If it is, then Windows Server is an even worse platform than I already suspected. The more likely explanation is that the hosting provider doesn't understand the nature of the problem... therefore, according to them, there is no problem. – Michael - sqlbot Jan 8 '15 at 1:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.