Hi, I have a problem with some of my servers running 4.1.10. It is running on linux 2.6.10, Fedora Core 3 default installation. The mysql I use is from RPM package that mysql.com provides. About once a day, the servers will crash and I find mysqld got signal 11 error on the log file.
These machines only run 1 mysql server per machine, and I only have 1 InnoDB table there. Is there anyone with the same experience? --- start: hostname.err --- 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=2093056 max_used_connections=51 max_connections=400 threads_connected=12 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3209660 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x4da2ab50 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=0xbfe7f5a8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808d8d7 0x82e68d8 0x80929a3 0x809af45 0x809b709 0x82e408c 0x830d95a 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 (nil) is invalid pointer thd->thread_id=10940509 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. pure virtual method called Fatal signal 6 while backtracing Number of processes running now: 0 --- end: hostname.err --- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
