MySQL Bugs: #22981: MySQL-Server crashes at random

Bug #22981	MySQL-Server crashes at random
Submitted:	4 Oct 2006 12:46	Modified:	4 Nov 2006 16:06
Reporter:	Sebastian Gräber	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.24	OS:	Windows (Windows Server 2003)
Assigned to:		CPU Architecture:	Any

Description:
The MySQL-Server crashes at random. Sometimes more than threetimes a day. The service must be restarted. As a result I had the loss of an index table (AutoIncrement) and the index was reseted to its initial value. A loss of data is not recognizable.

I use the MySQL-Java-Connector (3.1.13) to connect to the database. Before migrating to the 5.0.24 I had no problems with MySQL.

How to repeat:
???

Thank you for a problem report. Please, send your error log (or, at least, part of it that corresponds to crashes you described). Send your my.ini content and described your hardware (how much RAM do you have).

Additional information on the hardware:

Athlon64 X2 3800+
2GB RAM
HighPoint RocketRAID Controller
RAID 0+1 with 4 HD à 80 GB connected to the HP RocketRAID
100 MBit LAN Adapter

Every hour a backup file is written on another server in the domain with MySQL Administrator 1.1.6

There are no information according the crash in the error log.

We need a user.dmp from dr. watson to analyze the stack traces.
Run drwtsn32.exe and select the following options:
 * Log file path: c:\crashes\ (make sure this directory exists)
 * Crash dump: c:\crashes\user.dmp
 * Number of instructions: 100 
 * Number of errors to save: 100
 * [X] Dump Symbol Table
 * [X] Dump All Thread Contexts
 * [X] Append to Existing Log File
 * [X] Visual Notification
 * [ ] Audio Notification
 * [X] Create Crash Dump File 

Close drwtsn32. Run again with "drwtsn32.exe -i" to register it as the default debugger. Then, after a crash, compress and upload the contents of c:\crashes.
Also, try 5.0.26.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".