ночью что то произошло и перестал запускаться mysql
сейчас при запуске в логе пишет
141121 10:57:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141121 10:57:02 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141121 10:57:03 InnoDB: Initializing buffer pool, size = 8.0M
141121 10:57:03 InnoDB: Completed initialization of buffer pool
141121 10:57:03 InnoDB: Started; log sequence number 0 46200942
141121 10:57:03 [Note] Recovering after a crash using mysql-bin
141121 10:57:03 [Note] Starting crash recovery...
141121 10:57:03 [Note] Crash recovery finished.
08:57:03 UTC - 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 against 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=268435456
read_buffer_size=1048576
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 572371 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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_bottom = 0 thread_stack 0x30000
/usr/libexec/mysqld(my_print_stacktrace+0x2e) [0x84c6d3e]
/usr/libexec/mysqld(handle_fatal_signal+0x484) [0x82ec8b4]
[0x516400]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
141121 10:57:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

что делать?

это свзяно с удалением бинарных файлов, если их удалить вылазит такое:

141121 11:10:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141121 11:10:58 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141121 11:10:58 InnoDB: Initializing buffer pool, size = 8.0M
141121 11:10:58 InnoDB: Completed initialization of buffer pool
141121 11:10:58 InnoDB: Started; log sequence number 0 46200942
^G/usr/libexec/mysqld: File './mysql-bin.000002' not found (Errcode: 2)
141121 11:10:58 [ERROR] Failed to open log (file './mysql-bin.000002', errno 2)
141121 11:10:58 [ERROR] Could not open log file
141121 11:10:58 [ERROR] Can't init tc log
141121 11:10:58 [ERROR] Aborting

141121 11:10:58 InnoDB: Starting shutdown...
141121 11:11:03 InnoDB: Shutdown completed; log sequence number 0 46200942
141121 11:11:03 [Note] /usr/libexec/mysqld: Shutdown complete

141121 11:11:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

если вернуть, то получаю ошибку с первого сообщения

решилось, если удалить
все бинарные и mysql-bin.index, то должно заработать
+ отключение и удаление http://blog.kron-net.ru/archives/320