Description:
Seemingly random crash, the server was running ok for several weeks then it crashed and curupted the indexes on one of the tables.
i have no idea how to read the .err file and was hoping someone could point me in the right direction.
im not able to repeat this but it has hapend 3 times now.
if there is something i can do to get more information let me know.
thnaks.
mysqladmin -u root -p version
--------------------------------
mysqladmin Ver 8.41 Distrib 4.1.14, for pc-linux-gnu on i386
Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license
Server version 4.1.14-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 1 hour 22 min 36 sec
Threads: 2 Questions: 475454 Slow queries: 0 Opens: 121 Flush tables: 1 Open tables: 110 Queries per second avg: 95.935
mysqld.err
-----------------------
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=402653184
read_buffer_size=2093056
max_used_connections=1275
max_connections=5000
threads_connected=97
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 4075960 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x892fc538
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=0xbe5ff4b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8134ee0
0xb7e1ce61
0x84150ea
0x812ed47
0x814e4c4
0xb7e15f5b
0xb7c7089a
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 (nil) is invalid pointer
thd->thread_id=61178410
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.
070423 10:25:28 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...
070423 10:25:28 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 47197.
InnoDB: Doing recovery: scanned up to log sequence number 0 47805
InnoDB: Last MySQL binlog file position 0 4, file name ./db-master-bin.000017
070423 10:25:28 InnoDB: Flushing modified pages from the buffer pool...
070423 10:25:28 InnoDB: Started; log sequence number 0 47805
070423 10:25:28 [Warning] 'user' entry 'root@<REMOVED>' ignored in --skip-name-resolve mode.
070423 10:25:28 [Warning] 'user' entry '(null)@<REMOVED>' ignored in --skip-name-resolve mode.
070423 10:25:28 [Warning] 'user' entry 'root@<REMOVED>' ignored in --skip-name-resolve mode.
070423 10:25:28 [Warning] 'user' entry '<REMOVED>@<REMOVED>' ignored in --skip-name-resolve mode.
/usr/sbin/mysqld: ready for connections.
Version: '4.1.14-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-4.1.14
070423 11:41:24 [Note] /usr/sbin/mysqld: Normal shutdown
How to repeat:
im not able to repeat this but it has hapend 3 times now.
