Mysql ne redémarre plus
Hello,
OS : Debian sarge de base avec mysql + apache
MySQL ne veut plus redémarrer alors qu'il fonctinnait TRES bien avant :(
Je pense à un apt-get upgrade qui a mal tourné non ?
Quelqu'un aurait-il une idée ou ce problème ?
Merci
############################
/etc/init.d/mysql restart
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld...failed.
Please take a look at the syslog.
############################
Jan 13 20:40:13 hebus mysqld_safe[14194]: started
Jan 13 20:40:14 hebus mysqld[14198]: mysqld got signal 11;
Jan 13 20:40:14 hebus mysqld[14198]: This could be because you hit a
bug. It is also possible that this binary
Jan 13 20:40:14 hebus mysqld[14198]: or one of the libraries it was
linked against is corrupt, improperly built,
Jan 13 20:40:14 hebus mysqld[14198]: or misconfigured. This error can
also be caused by malfunctioning hardware.
Jan 13 20:40:14 hebus mysqld[14198]: We will try our best to scrape up
some info that will hopefully help diagnose
Jan 13 20:40:14 hebus mysqld[14198]: the problem, but since we have
already crashed, something is definitely wrong
Jan 13 20:40:14 hebus mysqld[14198]: and this may fail.
Jan 13 20:40:14 hebus mysqld[14198]:
Jan 13 20:40:14 hebus mysqld[14198]: key_buffer_size=4194304
Jan 13 20:40:14 hebus mysqld[14198]: read_buffer_size=131072
Jan 13 20:40:14 hebus mysqld[14198]: max_used_connections=0
Jan 13 20:40:14 hebus mysqld[14198]: max_connections=100
Jan 13 20:40:14 hebus mysqld[14198]: threads_connected=0
Jan 13 20:40:14 hebus mysqld[14198]: It is possible that mysqld could
use up to
Jan 13 20:40:14 hebus mysqld[14198]: key_buffer_size + (read_buffer_size
+ sort_buffer_size)*max_connections = 221695 K
Jan 13 20:40:14 hebus mysqld[14198]: bytes of memory
Jan 13 20:40:14 hebus mysqld[14198]: Hope that's ok; if not, decrease
some variables in the equation.
Jan 13 20:40:14 hebus mysqld[14198]:
Jan 13 20:40:14 hebus mysqld[14198]: thd=(nil)
Jan 13 20:40:14 hebus mysqld[14198]: Attempting backtrace. You can use
the following information to find out
Jan 13 20:40:14 hebus mysqld[14198]: where mysqld died. If you see no
messages after this, something went
Jan 13 20:40:14 hebus mysqld[14198]: terribly wrong...
Jan 13 20:40:14 hebus mysqld[14198]: Cannot determine thread,
fp=0x41ac87d8, backtrace may not be correct.
Jan 13 20:40:14 hebus mysqld[14198]: Stack range sanity check OK,
backtrace follows:
Jan 13 20:40:14 hebus mysqld[14198]: 0x810e0cb
Jan 13 20:40:14 hebus mysqld[14198]: 0x41ac8ad0
Jan 13 20:40:14 hebus mysqld[14198]: (nil)
Jan 13 20:40:14 hebus mysqld[14198]: New value of fp=(nil) failed sanity
check, terminating stack trace!
Jan 13 20:40:14 hebus mysqld[14198]: Please read
http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow
instructions on how to resolve the sta
Jan 13 20:40:14 hebus mysqld[14198]: stack trace is much more helpful in
diagnosing the problem, so please do
Jan 13 20:40:14 hebus mysqld[14198]: resolve it
Jan 13 20:40:14 hebus mysqld[14198]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Jan 13 20:40:14 hebus mysqld[14198]: information that should help you
find out what is causing the crash.
Jan 13 20:40:15 hebus mysqld_safe[14201]: ended
Jan 13 20:40:22 hebus /etc/init.d/mysql[14231]: 0 processes alive and
'/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping'
resulted in
Jan 13 20:40:22 hebus /etc/init.d/mysql[14231]: ^G/usr/bin/mysqladmin:
connect to server at 'localhost' failed
Jan 13 20:40:22 hebus /etc/init.d/mysql[14231]: error: 'Can't connect to
local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Jan 13 20:40:22 hebus /etc/init.d/mysql[14231]: Check that mysqld is
running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Jan 13 20:40:22 hebus /etc/init.d/mysql[14231]:
Reply to: