Package: mysql-server Version: 4.0.24-10 This morning I upgraded mysql-server using apt-get on a box running debian-sarge 3.1. Since then, mysqld fails to start. The following messages appear in the syslog file:
May 29 10:02:39 mysqld_safe[18836]: started May 29 10:02:39 mysqld[18840]: mysqld got signal 11; May 29 10:02:39 mysqld[18840]: This could be because you hit a bug. It is also possible that this binary May 29 10:02:39 mysqld[18840]: or one of the libraries it was linked against is corrupt, improperly built, May 29 10:02:39 mysqld[18840]: or misconfigured. This error can also be caused by malfunctioning hardware. May 29 10:02:39 mysqld[18840]: We will try our best to scrape up some info that will hopefully help diagnose May 29 10:02:39 mysqld[18840]: the problem, but since we have already crashed, something is definitely wrong and this may fail. May 29 10:02:39 mysqld[18840]: key_buffer_size=16777216 May 29 10:02:39 mysqld[18840]: read_buffer_size=131072 May 29 10:02:39 mysqld[18840]: max_used_connections=0 May 29 10:02:39 mysqld[18840]: max_connections=100 May 29 10:02:39 mysqld[18840]: threads_connected=0 May 29 10:02:39 mysqld[18840]: It is possible that mysqld could use up to May 29 10:02:39 mysqld[18840]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K bytes of memory May 29 10:02:39 mysqld[18840]: Hope that's ok; if not, decrease some variables in the equation. May 29 10:02:39 mysqld[18840]: thd=0x842a638 May 29 10:02:39 mysqld[18840]: Attempting backtrace. You can use the following information to find out May 29 10:02:39 mysqld[18840]: where mysqld died. If you see no messages after this, something went terribly wrong... May 29 10:02:39 mysqld[18840]: Cannot determine thread, fp=0x4201e7d8, backtrace may not be correct. May 29 10:02:39 mysqld[18840]: Stack range sanity check OK, backtrace follows: May 29 10:02:39 mysqld[18840]: 0x810e48b May 29 10:02:39 mysqld[18840]: 0x40038af8 May 29 10:02:39 mysqld[18840]: (nil) May 29 10:02:39 mysqld[18840]: New value of fp=(nil) failed sanity check, terminating stack trace! May 29 10:02:39 mysqld[18840]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved May 29 10:02:39 mysqld[18840]: stack trace is much more helpful in diagnosing the problem, so please do resolve it May 29 10:02:39 mysqld[18840]: Trying to get some variables. May 29 10:02:39 mysqld[18840]: Some pointers may be invalid and cause the dump to abort... May 29 10:02:39 mysqld[18840]: thd->query at 0x76f0e210 is invalid pointer May 29 10:02:39 mysqld[18840]: thd->thread_id=2037198702 May 29 10:02:39 mysqld[18840]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains May 29 10:02:39 mysqld[18840]: information that should help you find out what is causing the crash. May 29 10:02:39 mysqld_safe[18844]: ended I followed some of the instructions on the mysql.com crashing help page. Running "resolve_stack_dump" returned: 0x810e48b handle_segfault + 667 0x40038af8 _end + 935391344 If this is an issue I should be reporting to mysql, please let me know. All help appreciated. Thanks, Stella -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
