Hi!, I'm hoping someone can give me a pointer as to what's going wrong that's crashing our MySQL server, I've included a snippet of the log (for the last time it restarted and then the errors after that).
I've been trying to read through the 'Debugging MySQL server' section, but there doesn't seem to be much to go on from the log, and the 'if you don't see anything something went terribly wrong' message with nothing but an 'aborting backtrace' message after it kinda has me worried over here. Any suggestions, pointers, or anything else would be really appreciated as my hair is turning gray by the second :). Thanks in advance, William. mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 020722 08:55:42 mysqld restarted /usr/sbin/mysqld: ready for connections 020722 8:55:45 read_key: Got error 127 when reading table './wahse/keywords' 020722 8:55:45 read_key: Got error 127 when reading table './wahse/keywords' [snip an hour of these] 020722 10:20:37 read_key: Got error 127 when reading table './wahse/keywords' 020722 10:20:37 read_key: Got error 127 when reading table './wahse/keywords' 020722 10:20:38 read_key: Got error 127 when reading table './wahse/keywords' mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong frame pointer (ebp) is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace Number of processes running now: 0 020722 15:44:25 mysqld restarted /usr/sbin/mysqld: ready for connections mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong frame pointer (ebp) is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace Number of processes running now: 0 020722 16:09:54 mysqld restarted /usr/sbin/mysqld: ready for connections --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
