MySQL fails to start after out of memory error.

[emc]

Hi Everyone,

 

after a out of memory issue on my server, my MySQL wouldn't start anymore. I am running debian. Here is my syslog. Do you have an idea how I best solve that? I tried apt-get remove and apt-get install again but it didn't help

 

Any other ideas? Help would be much appreciated!

 

Thanks and best regards,

Christoph

 

Mysql version:

 

christoph:/usr/share# mysql --version

mysql  Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2

 

 

...
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 661 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 662 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 663 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 664 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 665 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 666 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 667 (mysqld).
Sep 17 08:27:55 christoph kernel: Out of Memory: Killed process 668 (mysqld).
Sep 17 08:27:56 christoph /USR/SBIN/CRON[674]: (www-data) CMD (/usr/share/cacti/site/poller.php >/dev/null 2>&1)
Sep 17 08:28:18 christoph mysqld_safe[685]: Number of processes running now: 0
Sep 17 08:28:19 christoph mysqld_safe[687]: restarted
Sep 17 08:28:55 christoph mysqld[691]: mysqld got signal 11;
Sep 17 08:28:55 christoph mysqld[691]: This could be because you hit a bug. It is also possible that this binary
Sep 17 08:28:55 christoph mysqld[691]: or one of the libraries it was linked against is corrupt, improperly built,
Sep 17 08:28:55 christoph mysqld[691]: or misconfigured. This error can also be caused by malfunctioning hardware.
Sep 17 08:28:55 christoph mysqld[691]: We will try our best to scrape up some info that will hopefully help diagnose
Sep 17 08:28:55 christoph mysqld[691]: the problem, but since we have already crashed, something is definitely wrong
Sep 17 08:28:55 christoph mysqld[691]: and this may fail.
Sep 17 08:28:55 christoph mysqld[691]: 
Sep 17 08:28:55 christoph mysqld[691]: key_buffer_size=16777216
Sep 17 08:28:55 christoph mysqld[691]: read_buffer_size=131072
Sep 17 08:28:55 christoph mysqld[691]: max_used_connections=0
Sep 17 08:28:55 christoph mysqld[691]: max_connections=100
Sep 17 08:28:55 christoph mysqld[691]: threads_connected=0
Sep 17 08:28:55 christoph mysqld[691]: It is possible that mysqld could use up to 
Sep 17 08:28:55 christoph mysqld[691]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Sep 17 08:28:55 christoph mysqld[691]: bytes of memory
Sep 17 08:28:55 christoph mysqld[691]: Hope that's ok; if not, decrease some variables in the equation.
Sep 17 08:28:55 christoph mysqld[691]: 
Sep 17 08:28:55 christoph mysqld[691]: thd=(nil)
Sep 17 08:28:58 christoph mysqld[691]: Attempting backtrace. You can use the following information to find out
Sep 17 08:28:58 christoph mysqld[691]: where mysqld died. If you see no messages after this, something went
Sep 17 08:28:58 christoph mysqld[691]: terribly wrong...
Sep 17 08:28:58 christoph mysqld[691]: Cannot determine thread, fp=0x42175158, backtrace may not be correct.
Sep 17 08:28:58 christoph mysqld[691]: Stack range sanity check OK, backtrace follows:
Sep 17 08:28:58 christoph mysqld[691]: 0x810e48b
Sep 17 08:28:58 christoph mysqld[691]: 0x42175450
Sep 17 08:28:58 christoph mysqld[691]: (nil)
Sep 17 08:28:58 christoph mysqld[691]: New value of fp=(nil) failed sanity check, terminating stack trace!
Sep 17 08:28:58 christoph mysqld[691]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
Sep 17 08:28:58 christoph mysqld[691]: stack trace is much more helpful in diagnosing the problem, so please do 
Sep 17 08:28:58 christoph mysqld[691]: resolve it
Sep 17 08:28:58 christoph mysqld[691]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Sep 17 08:28:58 christoph mysqld[691]: information that should help you find out what is causing the crash.
Sep 17 08:29:19 christoph mysqld_safe[695]: ended
...

[fenway]

Have you tried re-installing?