Hi,
Iam having a mysql version 5.0.15-standard-log installed on redhat es4.
It is configured as slave server. It was running fine till yesterday.
Then it hit a mysql bug with signal 6. The mysql db was throwing the
following errors on the shell prompt ie the OS shell prompt.
*** glibc detected *** free(): invalid pointer: 0x089e6843 ***
*** glibc detected *** free(): invalid pointer: 0x089e6843 ***
The mysql error log shows continuous occurence of mysql signal 6 and
signal 11.
The output of error log file is as follows:
-
mysqld got signal 6;
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=0
max_connections=10
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 434135 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x89fd360
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=0x177f9c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x814e7f8
0x8787c8
(nil)
0x69840a
0x69eb3f
0x69eeba
0x81f8bb3
0x8240d56
0x824123a
0x82403cb
0x8166f0b
0x8168d82
0x81bf14b
0x81beb8c
0x8222586
0x8220387
0x872341
0x7046fe
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 0x89f1860 = drop procedure FHLMC.pool_info_select
thd-thread_id=2
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
060413 13:01:56 mysqld restarted
Can anyone help me trace out the problem and how to go about the same ?
Is it something related to glibc version that is causing the problem ?
Thanks in advance,
Abdul.
This email has been Scanned for Viruses!
www.newbreak.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
