Bug #11117 MySQL random crashes
Submitted: 6 Jun 2005 15:06 Modified: 7 Jun 2005 14:15
Reporter: Ryan Paulson Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.1.11a OS:Windows (Windows 2003 Server)
Assigned to: CPU Architecture:Any

[6 Jun 2005 15:06] Ryan Paulson
Description:
The MySQL service stops unexpectedly at random times.  No entry is found in the error.log file, but there is a record of the crash in the Windows Event Viewer.

Error:
Faulting application mysqld-nt.exe, version 0.0.0.0, faulting module mysqld-nt.exe, version 0.0.0.0, fault address 0x001ea7e0.

This has happened 3 times on 2 of my 3 replicated servers in the last week.  All three slaves replicate from the same master.

When the failure is detected the service simply needs to be started back up again and everything works again.

How to repeat:
I have not been able to find any way to repeat this error.  I thought it might be a query until it started happening on a slave that is not currently being used.  

Other people have reported this issue in the forums without resolution or even finding a cause.

Suggested fix:
Unknown.
[6 Jun 2005 15:30] MySQL Verification Team
Could you please verify if in the Windows Event there is (are) error(s)
from the mysqld-nt.exe  start it as standalone: e.g.:

mysqld-nt --defaults-file=path_for_your_ini_file --standalone --console

and look if some warning/error is printed in the prompt screen.

Otherwise we can't to analyze what is happened with the information
you are provided.
[6 Jun 2005 16:18] Ryan Paulson
I have restarted 2 of the servers to run standalone in the console.

I will report any errors after a failure.
[7 Jun 2005 14:15] MySQL Verification Team
Please re-open this issue when you provide us with more information
about the issue's cause.

Thanks in advance.