Oct 14 19:42:45 localhost mysqld[10003]: InnoDB: Error: the transaction object for the table handle is at
Oct 14 19:42:46 localhost mysqld[10003]: InnoDB: 0x2c92bc68, but for the current thread it is at 0x2c9ad468
Oct 14 19:42:46 localhost mysqld[10003]: InnoDB: Dump of 200 bytes around prebuilt: len 200; hex 043ca33f00000000010000000800000000000000
00020000000000001834962c01000000b307952d6d7973716c2e63007c01000000000000000000000000000028188d2c28a49e2cc001000000000000000000000001000040
0000000000000010000000ef6fae0468f2722c68bc922c0100000001000000000000000000000000000000000000006f72756d000000006f7374696e672e7068703f6d0000
000028188d2c00000000000000000000000000000000000000000000000068bb972c68c4a02c00000000; asc < ? 4 , -mysql.c
| ( ,( , @ o h r,h , orum osting.php?m ( ,
h ,h , ;
Oct 14 19:42:46 localhost mysqld[10003]: InnoDB: Dump of 200 bytes around transaction.all: len 200; hex 000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000068d49a2c0100000000000000000000004d4b5a0800000000000000000000000000000000010000000000000030ecf45000000
00030ecf45020000000e41f00000400000000000000109c15080000000000000000000000000000000000000000; asc
h , MKZ 0 P 0 P
;
Oct 14 19:42:49 localhost mysqld[10003]: mysqld got signal 11;
Oct 14 19:42:49 localhost mysqld[10003]: This could be because you hit a bug. It is also possible that this binary
Oct 14 19:42:49 localhost mysqld[10003]: or one of the libraries it was linked against is corrupt, improperly built,
Oct 14 19:42:49 localhost mysqld[10003]: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 14 19:42:49 localhost mysqld[10003]: We will try our best to scrape up some info that will hopefully help diagnose
Oct 14 19:42:49 localhost mysqld[10003]: the problem, but since we have already crashed, something is definitely wrong
Oct 14 19:42:49 localhost mysqld[10003]: and this may fail.
Oct 14 19:42:49 localhost mysqld[10003]:
Oct 14 19:42:49 localhost mysqld[10003]: key_buffer_size=16777216
Oct 14 19:42:49 localhost mysqld[10003]: read_buffer_size=131072
Oct 14 19:42:49 localhost mysqld[10003]: max_used_connections=392
Oct 14 19:42:49 localhost mysqld[10003]: max_connections=1024
Oct 14 19:42:49 localhost mysqld[10003]: threads_connected=390
Oct 14 19:42:49 localhost mysqld[10003]: It is possible that mysqld could use up to
Oct 14 19:42:49 localhost mysqld[10003]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2244600 K
Oct 14 19:42:49 localhost mysqld[10003]: bytes of memory
Oct 14 19:42:49 localhost mysqld[10003]: Hope that's ok; if not, decrease some variables in the equation.
Oct 14 19:42:49 localhost mysqld[10003]:
Oct 14 19:42:49 localhost mysqld[10003]: You seem to be running 32-bit Linux and have 390 concurrent connections.
Oct 14 19:42:49 localhost mysqld[10003]: If you have not changed STACK_SIZE in LinuxThreads and built the binary
Oct 14 19:42:49 localhost mysqld[10003]: yourself, LinuxThreads is quite likely to steal a part of the global heap for
Oct 14 19:42:49 localhost mysqld[10003]: the thread stack. Please read http://www.mysql.com/doc/en/Linux.html
Oct 14 19:42:49 localhost mysqld[10003]:
Oct 14 19:42:49 localhost mysqld[10003]: thd=(nil)
Oct 14 19:42:49 localhost mysqld[10003]: Attempting backtrace. You can use the following information to find out
Oct 14 19:42:49 localhost mysqld[10003]: where mysqld died. If you see no messages after this, something went
Oct 14 19:42:49 localhost mysqld[10003]: terribly wrong...
Oct 14 19:42:49 localhost mysqld[10003]: Cannot determine thread, fp=0x5f7fe0b8, backtrace may not be correct.
Oct 14 19:42:49 localhost mysqld[10003]: Stack range sanity check OK, backtrace follows:
Oct 14 19:42:49 localhost mysqld[10003]: 0x81893bf
Oct 14 19:42:49 localhost mysqld[10003]: 0x25647825
Oct 14 19:42:49 localhost mysqld[10003]: 0x84b9e9e
Oct 14 19:42:49 localhost mysqld[10003]: 0x84b9ef7
Oct 14 19:42:49 localhost mysqld[10003]: 0x822d355
Oct 14 19:42:49 localhost mysqld[10003]: 0x822e7e2
Oct 14 19:42:49 localhost mysqld[10003]: 0x819bea5
Oct 14 19:42:49 localhost mysqld[10003]: 0x819bd46
Oct 14 19:42:49 localhost mysqld[10003]: 0x819b4a8
Oct 14 19:42:49 localhost mysqld[10003]: 0x25641e51
Oct 14 19:42:49 localhost mysqld[10003]: 0x2588c92a
Oct 14 19:42:49 localhost mysqld[10003]: New value of fp=(nil) failed sanity check, terminating stack trace!
Oct 14 19:42:49 localhost mysqld[10003]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on h
ow to resolve the stack trace. Resolved
Oct 14 19:42:49 localhost mysqld[10003]: stack trace is much more helpful in diagnosing the problem, so please do
Oct 14 19:42:49 localhost mysqld[10003]: resolve it
Oct 14 19:42:49 localhost mysqld[10003]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Oct 14 19:42:49 localhost mysqld[10003]: information that should help you find out what is causing the crash.