MySQL not responding after certain time

simonchs

Verified User
Joined
Feb 19, 2006
Messages
11
I'm using CentOS 4.2 x86_64 and the MySQL server stop responding after certain time, and the log of MySQL show the following:

*** glibc detected *** double free or corruption (!prev): 0x00000000012f78e0 ***
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=8388600
read_buffer_size=131072
max_used_connections=101
max_connections=100
threads_connected=23
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

And then I need to kill -9 the mysql process and start it again.

I had googled and somebody said the problem related with the bug of glibc 2.3.4, when he changed back to glibc 2.3.2, the problem solved.

Is the problem really related with glibc 2.3.4 ? (or glibc 2.3.4 x86_64 ?)

Thanks for helping!
 
update my status...

i had downgraded the MySQL to 4.1.18 (x86_64 rpm package from mysql.com) and everything ok now...
 
Back
Top