Description:
I have an MySQLd running on Slackware Linux 10.1, mysql version 5.0, mysql admin 1.1.8.
I dont know why this happens, but when i connect to the SQL Server with the Admin everything is fine... until i click on: Catalogs
I just logged the output of the sqld in my console:
root@darkstar:~# /usr/local/mysql/bin/mysqld --user=mysql
060211 23:01:11 InnoDB: Started; log sequence number 0 47606
060211 23:01:11 [Note] Recovering after a crash using mysql-bin
060211 23:01:11 [Note] Starting crash recovery...
060211 23:01:11 [Note] Crash recovery finished.
060211 23:01:11 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.16-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
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=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 802415 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8a69ee0
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=0xb3260248, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8150650
0xffffe420
0x8a54458
0x8211f23
0x8192690
0x81929f5
0x818ebd2
0x8164175
0x816ae7a
0x8162aa2
0x81625cd
0x8161aad
0xb7f8d20e
0xb7eb738e
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 0x8a4f4b8 = SHOW PROCEDURE STATUS
thd->thread_id=5
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.
thats what gdb says:
root@darkstar:~# gdb /usr/local/mysql/bin/mysqld
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-slackware-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) run --user=mysql
Starting program: /usr/local/mysql/bin/mysqld --user=mysql
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210214720 (LWP 1793)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1255752784 (LWP 1796)]
[New Thread -1264141392 (LWP 1797)]
[New Thread -1272530000 (LWP 1798)]
[New Thread -1280918608 (LWP 1799)]
[New Thread -1294214224 (LWP 1800)]
[New Thread -1302602832 (LWP 1801)]
[New Thread -1310991440 (LWP 1802)]
[New Thread -1319380048 (LWP 1803)]
060211 23:14:16 InnoDB: Started; log sequence number 0 47606
060211 23:14:16 [Note] Recovering after a crash using mysql-bin
060211 23:14:16 [Note] Starting crash recovery...
060211 23:14:16 [Note] Crash recovery finished.
(no debugging symbols found)
[Thread -1294214224 (zombie) exited]
[New Thread -1289344080 (LWP 1804)]
060211 23:14:17 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.16-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Com
[New Thread -1289540688 (LWP 1805)]
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1289843792 (LWP 1806)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1289843792 (LWP 1806)]
0x0820f212 in store_schema_proc ()
(gdb) backtrace
#0 0x0820f212 in store_schema_proc ()
#1 0x0820f81f in fill_schema_proc ()
#2 0x08211f23 in get_schema_tables_result ()
#3 0x08192690 in JOIN::exec ()
#4 0x081929f5 in mysql_select ()
#5 0x0818ebd2 in handle_select ()
#6 0x08164175 in mysql_execute_command ()
#7 0x0816ae7a in mysql_parse ()
#8 0x08162aa2 in dispatch_command ()
#9 0x081625cd in do_command ()
#10 0x08161aad in handle_one_connection ()
#11 0xb7f7a20e in start_thread () from /lib/tls/libpthread.so.0
#12 0xb7ea438e in clone () from /lib/tls/libc.so.6
(gdb) info local
No symbol table info available.
(gdb) up
#1 0x0820f81f in fill_schema_proc ()
(gdb) info local
No symbol table info available.
(gdb) up
#2 0x08211f23 in get_schema_tables_result ()
(gdb) info local
No symbol table info available.
and here is my strace output:
select(13, [11 12], NULL, NULL, NULLmysqld 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=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 802415 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8a69ee0
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=0xb3237248, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8150650
0xffffe420
0x8a54458
0x8211f23
0x8192690
0x81929f5
0x818ebd2
0x8164175
0x816ae7a
0x8162aa2
0x81625cd
0x8161aad
0xb7f6420e
0xb7e8e38e
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 0x8a4f4b8 = SHOW PROCEDURE STATUS
thd->thread_id=5
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.
) = ? ERESTARTNOHAND (To be restarted)
How to repeat:
Install the current stable MySQL Server on a Linux platform, run the MySQL Admin from a win platform; connect to it and have a look at the catalog.
Suggested fix:
no idea...
