Description:
our mysql is crashing and it's bringing down the OS as well. I can provide windows crash dump file as well.
windows: server 2008 r2 standard; 64bit; 8Gb ram;
mysql: 5.5.24 -- the latest we could found available
db size: we have only one db which is about 8Gb in size
I can provide any other info if needed
-------------------------------------------------------------------------------
mysql error log
-------------------------------------------------------------------------------
120523 19:33:39 InnoDB: Waiting for the background threads to start
120523 19:33:40 InnoDB: 1.1.8 started; log sequence number 18278812914
120523 19:33:41 [Note] Server hostname (bind-address): '(null)'; port: 3306
120523 19:33:41 [Note] - '(null)' resolves to '::';
120523 19:33:41 [Note] - '(null)' resolves to '0.0.0.0';
120523 19:33:41 [Note] Server socket created on IP: '0.0.0.0'.
120523 19:33:48 [Note] Event Scheduler: Loaded 0 events
120523 19:33:48 [Note] C:\mysql\bin\mysqld: ready for connections.
Version: '5.5.24' socket: '' port: 3306 MySQL Community Server (GPL)
120523 22:25:09 InnoDB: Assertion failure in thread 1872 in file rem0rec.c line 561
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 2728 stopped in file os0sync.c line 781
InnoDB: Thread 1972 stopped in file os0sync.c line 781
InnoDB: Thread 2444 stopped in file fil0fil.c line 4702
InnoDB: Thread 2624 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 824 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2932 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2312 stopped in file ha_innodb.cc line 7723
InnoDB: Thread 1840 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2632 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1984 stopped in file ut0ut.c line 76
InnoDB: Thread 2628 stopped in file ha_innodb.cc line 7723
InnoDB: Thread 2696 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1968 stopped in file os0sync.c line 474
InnoDB: Thread 2976 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1592 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2648 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2136 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 548 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2752 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2812 stopped in file ha_innodb.cc line 7723
InnoDB: Thread 2856 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2644 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 652 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2028 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 812 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2680 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1700 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1172 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1372 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2348 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 1908 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2852 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2520 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2352 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2636 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2236 stopped in file ha_innodb.cc line 6039
InnoDB: Thread 2816 stopped in file sync0rw.c line 572
InnoDB: Thread 1168 stopped in file sync0arr.c line 359
InnoDB: Thread 2652 stopped in file sync0arr.c line 359
InnoDB: Thread 2504 stopped in file sync0arr.c line 359
InnoDB: Thread 1432 stopped in file sync0arr.c line 359
InnoDB: Thread 2476 stopped in file sync0arr.c line 359
InnoDB: Thread 2748 stopped in file sync0arr.c line 359
InnoDB: Thread 2340 stopped in file sync0arr.c line 359
InnoDB: Thread 2364 stopped in file sync0arr.c line 359
InnoDB: Thread 1976 stopped in file os0sync.c line 474
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
windows crash info
the file "C:\Users\Administrator\AppData\Local\Temp\2\WER-32049703-0.sysdata.xml" mentioned in the log was not found on the server though; only the dmp file.
-------------------------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 2057
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000005003
BCP2: FFFFF70001080000
BCP3: 000000000000EE98
BCP4: 00000001810DD009
OS Version: 6_1_7601
Service Pack: 1_0
Product: 272_3
Files that help describe the problem:
C:\Windows\Minidump\052312-16468-01.dmp
C:\Users\Administrator\AppData\Local\Temp\2\WER-32049703-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
--------------------------------------------------------------------------------
How to repeat:
it is not reproduce-able
only to our server
Suggested fix:
n/a