Description:
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=268435456
read_buffer_size=2093056
max_used_connections=34
max_connections=100
threads_connected=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 671343 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x7eb44f78
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x67961d48, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x814caec
0x4002647e
0x82ff808
0x82a01a0
0x82a0c18
0x829f1f7
0x8294740
0x827a0b7
0x8276b73
0x81ef6f3
0x819e9ae
0x8190def
0x8196c94
0x8190dfa
0x8196c94
0x8190dfa
0x8196c94
0x8190d9e
0x8196956
0x818d73d
0x818e245
0x818a5f2
0x8160209
0x8166ce2
0x815eb02
0x815e635
0x815db00
0x40020941
0x420da1ca
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9ba8228 = select max(b.AuditedTime) from tblLemma a , tblVersion b, tblLink c where c.LinkTerm= '海洋' and a.VersionId = b.ID and c.ID1=a.ID
thd->thread_id=88451
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Number of processes running now: 0
070320 09:27:06 mysqld restarted
070320 9:27:06 [Warning] Changed limits: max_open_files: 1024 max_connections: 100 table_cache: 457
070320 9:27:06 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hos
tname changed!! Please use '--log-bin=tc-wiki-db01-bin' to avoid this problem.
070320 9:27:06 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070320 9:27:07 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 30 724456067.
InnoDB: Doing recovery: scanned up to log sequence number 30 724499525
070320 9:27:07 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 5
4 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 190, file name tc-wiki-db00-bin.000216
InnoDB: Last MySQL binlog file position 0 28351285, file name ./tc-wiki-db01-bin.000149
070320 9:27:08 InnoDB: Started; log sequence number 30 724499525
070320 9:27:08 [Note] Recovering after a crash using tc-wiki-db01-bin
070320 9:27:08 [Note] Starting crash recovery...
070320 9:27:08 [Note] Crash recovery finished.
070320 9:27:08 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Pleas
e use '--relay-log=tc-wiki-db01-relay-bin' to avoid this problem.
070320 9:27:08 [Note] /home/wiki/database/mysql/libexec/mysqld: ready for connections.
Version: '5.0.15-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
How to repeat:
When request comes frequently, It happened very often.
