Hello All, I have mysql 3.23.41 running on a Dell Poweredge 2550 on standard install of Red Hat 7.2 (2.4.9-21smp). This version of mysql came with Red Hat. It's been running my website very smoothly for the last few months, and averages 130 queries per second.
Mysql has crashed twice in the last month with the same errors in the error log (see log below). I attempted to resolve the stack dump, but when I do "nm -n libexec/mysqld > /tmp/mysqld.sym" I get a "nm: libexec/mysqld: no symbols" error. The good news is that mysql restarted itself and there seems to be no table corruption (whew!), but I'd still like to figure out why the server crashed on the "SHOW PROCESSLIST" command (which does run once a minute in a cron job). Any pointers or help would be greatly appreciated! Thanks, -Hank Eskin Here is the error log of the last crash: ---------------------------------------- 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 agaist 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 record_buffer=131072 sort_buffer=2097144 max_used_connections=58 max_connections=100 threads_connected=4 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 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... Stack range sanity check OK, backtrace follows: 0x80b25bf 0x4003aac5 0x4003bb56 0x40038ddc 0x810e76b 0x80b9fab 0x80bb9a5 0x80b7ac3 0x80b7099 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/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 0x82b2358 = show processlist thd->thread_id=2144083 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 2144083 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash Number of processes running now: 0 020617 17:32:41 mysqld restarted ---------------------------------------- __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com --------------------------------------------------------------------- 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
