Our mysql database sometimes crashes on a show column call for a View.
The steps that i believe produce the problem are as follows.
A view is being run at the same time that another user is logging into the mysql browser.
The the database crashes:
The following is what i found in the error file. We are using 5.0.45. Any ideas on steps i can take to reduce or eliminate this issue;
100211 16:30:48 - 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=1048576
read_buffer_size=1044480
max_used_connections=45
max_connections=100
threads_connected=19
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 512623 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x2aaab04e4490
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=0x4520b078, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
Stack trace seems successful - bottom reached
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 0x3666610 = SHOW COLUMNS FROM `vw_OATSReportableOrders`
thd->thread_id=6925
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.
100211 16:39:04 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...
100211 16:39:04 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 265 1114948129.
InnoDB: Doing recovery: scanned up to log sequence number 265 1114948129
InnoDB: Last MySQL binlog file position 0 463003052, file name /appl/aqua/prod/db- data/bin.000089
100211 16:39:04 InnoDB: Started; log sequence number 265 1114948129
100211 16:39:04 [Note] Recovering after a crash using /appl/aqua/prod/db-data/bin
100211 16:39:12 [Note] Starting crash recovery...
100211 16:39:12 [Note] Crash recovery finished.
100211 16:39:12 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.45-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)