Yesterday my server died abruptly. I can't even guess the reason. Fortunately there remain error messages, following are the messages
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=268431360 record_buffer=1044480 sort_buffer=4194296 max_used_connections=133 max_connections=400 threads_connected=60 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2308536 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: 0x80a926a 0x4002b8d5 0x80a4aa6 0x80a4c66 0x80adbd3 0x80aded1 0x80adbd3 0x80aded1 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions o n 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=129599 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 129599 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: 21 mysqld process hanging, pid 338 - killed 020526 13:01:41 mysqld restarted /usr/local/libexec/mysqld: ready for connections ~ Does anybody know the reason? It's critical to me. If you know anything about it, please let me know. Any information will be appreciated. --------------------------------------------------------------------- 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
