I've been searching the mailing list for a solution to my problem with "mysqld got signal 11;" and I haven't seen any answers that might help me. This is the situation.
I have a db that is being accessed intensively about 400 connections during the wee at a time. I noticed the problem at first with 4.0.13 and tried 3.23.57 and now 4.0.14 with the same problem. I've run the db on FreeBSD 5.1 and 4.8, again same problem. This is what shows up in the error log: ---------- 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=33554432 read_buffer_size=520192 max_used_connections=97 max_connections=450 threads_connected=85 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 491764 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Number of processes running now: 0 030726 06:14:51 mysqld restarted 030726 6:14:51 InnoDB: Started /usr/local/libexec/mysqld: ready for connections. Version: '4.0.14-debug-log' socket: '/tmp/mysql.sock' port: 3306 ---------- As you can see I have recently compiled 4.0.14 in debug mode and doing some more logging. However I'm still not seeing any further information to help me figure out what is causing this signal 11. The db is accesed remotely via web based php scripts as well as command line php scripts. I've tried to reproduce a test case as described on the on-line MySQL manual ( E.1.6 Making a Test Case If You Experience Table Corruption ) but I can't seem to reproduce the problem. It just seems to singal 11 randomly. When I had a Master/slave setup, only the master would signal 11, the slave seemed completely unaffected, however nothing was accessing the slave directly, I had setup the slave purely as a bit of a remote backup solution for the db. What else can I do to help troubleshoot my problem? I've been looking into stack trace and trace files but I'm not sure if these would help me out. Does anyone have any suggestions for me to try and what other information I might be able to provide? Thank you, Stephane Raimbault. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
