не стартует mysql

[DimmKo]

Добрый день.
Случилась неприятность: не стартует mysql. Ubuntu (x86_64) 14.04.4 LTS.
Всё было нормально, провел обновление apt-get update && apt-get upgrade (mysql не обновлялся), всё прошло штатно без ошибок, перезапустил сервер.
При загрузке написал, что starting mysql - failed.
Запускаю руками и вижу вот такое дело:

(Нажмите, чтобы показать/скрыть)

root@server:/home/dimmko# /etc/init.d/mysql start
 * Starting MySQL database server mysqld                                                                                                                                                                       [ OK ]
 * Checking for tables which need an upgrade, are corrupt or were
not closed cleanly.
root@server:/home/dimmko# ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

и ничего не происходит. Нажимаю CTRL + C, делаю service mysql start --> OK | service mysql status mysql start/running, process 29726
далее, хочу сделать дамп БД, на что получаю вот такую ошибку:

(Нажмите, чтобы показать/скрыть)

root@server:/media/hdd2/mysql_bck# mysqldump -u root -p testdb > testdb_`date +"%F_%H-%M-%S"`.sql
Enter password:
mysqldump: Got error: 2013: Lost connection to MySQL server during query when using LOCK TABLES

Попробовал поиска в гугле ошибку, но что нашел не подходит. Не могу понять в чем дело.
Логи:
1) /var/log/mysql/error

(Нажмите, чтобы показать/скрыть)

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7804004bd0): is an invalid pointer
Connection ID (thread ID): 2
Status: NOT_KILLED

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.
160311 10:06:19 mysqld_safe Number of processes running now: 0
160311 10:06:19 mysqld_safe mysqld restarted
160311 10:06:19 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160311 10:06:19 [Note] /usr/sbin/mysqld (mysqld 5.5.47-0ubuntu0.14.04.1) starting as process 30508 ...
160311 10:06:19 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160311 10:06:19 [Note] Plugin 'FEDERATED' is disabled.
160311 10:06:19 InnoDB: The InnoDB memory heap is disabled
160311 10:06:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160311 10:06:19 InnoDB: Compressed tables use zlib 1.2.8
160311 10:06:19 InnoDB: Using Linux native AIO
160311 10:06:19 InnoDB: Initializing buffer pool, size = 128.0M
160311 10:06:19 InnoDB: Completed initialization of buffer pool
160311 10:06:19 InnoDB: highest supported file format is Barracuda.
160311 10:06:20  InnoDB: Waiting for the background threads to start

2) /var/log/syslog

(Нажмите, чтобы показать/скрыть)

Mar 11 10:05:58 server /etc/mysql/debian-start[30336]: Upgrading MySQL tables if necessary.
Mar 11 10:05:58 server /etc/mysql/debian-start[30339]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Mar 11 10:05:58 server /etc/mysql/debian-start[30339]: Looking for 'mysql' as: /usr/bin/mysql
Mar 11 10:05:58 server /etc/mysql/debian-start[30339]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Mar 11 10:05:58 server /etc/mysql/debian-start[30339]: This installation of MySQL is already upgraded to 5.5.47, use --force if you still need to run mysql_upgrade
Mar 11 10:05:58 server /etc/mysql/debian-start[30350]: Checking for insecure root accounts.
Mar 11 10:05:58 server /etc/mysql/debian-start[30355]: Triggering myisam-recover for all MyISAM tables
Mar 11 10:07:38 server kernel: [13109.183706] init: mysql main process (30327) terminated with status 1
Mar 11 10:07:38 server kernel: [13109.183746] init: mysql main process ended, respawning
Mar 11 10:07:38 server kernel: [13109.208695] audit: type=1400 audit(1457680058.599:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=30599 comm="apparmor_parser"
Mar 11 10:07:38 server /etc/mysql/debian-start[30620]: Upgrading MySQL tables if necessary.
Mar 11 10:07:38 server /etc/mysql/debian-start[30623]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Mar 11 10:07:38 server /etc/mysql/debian-start[30623]: Looking for 'mysql' as: /usr/bin/mysql
Mar 11 10:07:38 server /etc/mysql/debian-start[30623]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Mar 11 10:07:38 server /etc/mysql/debian-start[30623]: This installation of MySQL is already upgraded to 5.5.47, use --force if you still need to run mysql_upgrade
Mar 11 10:07:38 server /etc/mysql/debian-start[30634]: Checking for insecure root accounts.
Mar 11 10:07:38 server /etc/mysql/debian-start[30649]: Triggering myisam-recover for all MyISAM tables

Может дополнительно какие-то логи надо добавить.

Может кто знает, что я упустил из виду, для решения это проблемы?
Спасибо.

[lAionl]

Бегло ознакомившись с текстом:

Checking for tables which need an upgrade, are corrupt or were
not closed cleanly.

могу сказать, что нужно чинить ^_^:

Код: [Выделить]

mysqlcheck --check-upgrade --all-databases --auto-repair -u root -p
mysql_upgrade --force -u root -p
P.S. если пока я иду разогревать обед, вы воспользовавшись этими командами убьете содержимое БД, я снимаю с себя ответственность за это. Перед вводом команд, убедитесь что имеется резервная копия данных.

[DimmKo]

lAionl,
добрый день, спасибо за ваш совет, но что-то пошло не так ^_^
Enter password:
mysqlcheck: Got error: 1049: Unknown database '—check-upgrade' when selecting the database

[lAionl]

Исправил команды в ответе выше, попробуйте.

[DimmKo]

lAionl,
благодарю...
1) команду запустил... появилось много "ОК", а закончилось вот этим
mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ...  FOR UPGRADE'

вторую команду стоит ли запускать?

[lAionl]

Попробуйте.

Код: [Выделить]

mysqlcheck --all-databases --repair --analyze --optimize --auto-repair


[DimmKo]

Попробуйте.

Код: [Выделить]

mysqlcheck --all-databases --repair --analyze --optimize --auto-repair


Error:  mysqlcheck doesn't support multiple contradicting commands.

[lAionl]

Код: [Выделить]

mysqlcheck --all-databases --repair --analyze --optimize


[DimmKo]

lAionl,
та же ошибка
попробовал вот это

Код: [Выделить]

mysqlcheck --all-databases --optimize --auto-repair -u root -pвыдало значения по одной базе

(Нажмите, чтобы показать/скрыть)

blog.wp_banner
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_blc_filters
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_blc_instances
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_blc_links
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_blc_synch
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_album
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_album_gallery
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_gallery
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_image
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_image_comment
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_image_rate
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_image_tag
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_option
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_shortcode
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_bwg_theme
Warning  : Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_cleantalk_sfw                              Table is already up to date
blog.wp_commentmeta
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_comments
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_cptch_images
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_cptch_packages
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_cptch_whitelist
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_gmedia
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_gmedia_meta
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_gmedia_term
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_gmedia_term_meta
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_gmedia_term_relationships
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_huge_itgallery_gallerys                    OK
blog.wp_huge_itgallery_images                      OK
blog.wp_leaves
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_links
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_lockdowns
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_login_fails
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_media_player_stats
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_mts_wp_reviews
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_ngg_album
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_ngg_gallery
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_ngg_pictures
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_options
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_postmeta
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_posts
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_modules
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_modules_type
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_popup
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_popup_show_pages
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_statistics
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_subscribers
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_pps_usage_stat
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_sms_send
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_sms_subscribes
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK
blog.wp_sms_subscribes_group
note     : Table does not support optimize, doing recreate + analyze instead
status   : OK

и закончилось вот этим
mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'OPTIMIZE TABLE ... '

может удалить эту базу?

[lAionl]

нужно запустить  mysql и передать как параметр --net_read_timeout=6000, затем повторить самую первую команду которую вводили (самый первый ответ)

[DimmKo]

нужно запустить  mysql и передать как параметр --net_read_timeout=6000, затем повторить самую первую команду которую вводили (самый первый ответ)

сделал /etc/init.d/mysql start --net_read_timeout=6000
запустился так же с кучей ошибок.
Выполнил команду из вашего 1-го ответа:
mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ...  FOR UPGRADE'

Может удалить нафиг, да и заново поставить?

[lAionl]

Может удалить нафиг, да и заново поставить?

Можно попробовать.

[DimmKo]

lAionl,
спасибо за вашу помощь.

Решение:
удалил (правда через webmin) всё что связано с mysql:

(Нажмите, чтобы показать/скрыть)

libdbd-mysql-perl
libmysqlclient18:amd64
libqt4-sql-mysql:amd64
mysql-client-5.5
mysql-client-core-5.5
mysql-common
mysql-server
mysql-server-5.5
mysql-server-core-5.5
php5-mysql
python-mysqldb

потом папки удалил (/etc/mysql | /var/lib/mysql)
потом перезагрузился и заново установил.
Залил дампы баз обратно - всё корректно работает.