Проблемы с мусколом в Ubuntu Server 12.04

[anytup]

Использую Ubuntu Server 12.04 для моего проекта на Django. На локальной машине все пашет, никаких ошибок и прочего. Но на сервере я часто вижу ошибку:

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

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)Логи:

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

cat /var/log/mysql/error.log
140415 23:05:34 [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.
140415 23:05:34 [Note] Plugin 'FEDERATED' is disabled.
140415 23:05:34 InnoDB: The InnoDB memory heap is disabled
140415 23:05:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140415 23:05:34 InnoDB: Compressed tables use zlib 1.2.3.4
140415 23:05:34 InnoDB: Initializing buffer pool, size = 128.0M
140415 23:05:34 InnoDB: Completed initialization of buffer pool
140415 23:05:34 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140415 23:05:34  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140415 23:05:35 [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.
140415 23:05:35 [Note] Plugin 'FEDERATED' is disabled.
140415 23:05:35 InnoDB: The InnoDB memory heap is disabled
140415 23:05:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140415 23:05:35 InnoDB: Compressed tables use zlib 1.2.3.4
140415 23:05:35 InnoDB: Initializing buffer pool, size = 128.0M
140415 23:05:35 InnoDB: Completed initialization of buffer pool
140415 23:05:35 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140415 23:05:35  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...Это уже не в первый раз, и я не могу понять, из-за чего она появляется.
Пробую

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

/etc/init.d/mysql restart или

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

service mysql restart, но это не помогает. У меня именно mysql-server, а не клиент. Сайт работал, работал, работал, а потом бац и из неоткуда такая ошибка.

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

ps ax | grep mysql
15654 pts/0    S+     0:00 grep --color=auto mysql
sudo service mysql start
start: Job failed to startСразу логи:

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

140416  1:11:17 [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.
140416  1:11:17 [Note] Plugin 'FEDERATED' is disabled.
140416  1:11:17 InnoDB: The InnoDB memory heap is disabled
140416  1:11:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140416  1:11:17 InnoDB: Compressed tables use zlib 1.2.3.4
140416  1:11:17 InnoDB: Initializing buffer pool, size = 128.0M

dpkg -l | grep mysql
ii  libdbd-mysql-perl                    4.020-1build2                     Perl5 database interface to the MySQL database
ii  libmysqlclient18                     5.5.35-0ubuntu0.12.04.2           MySQL database client library
ii  mysql-client-5.5                     5.5.35-0ubuntu0.12.04.2           MySQL database client binaries
ii  mysql-client-core-5.5                5.5.35-0ubuntu0.12.04.2           MySQL database core client binaries
ii  mysql-common                         5.5.35-0ubuntu0.12.04.2           MySQL database common files, e.g. /etc/mysql/my.cnf
ii  mysql-server                         5.5.35-0ubuntu0.12.04.2           MySQL database server (metapackage depending on the latest version)
ii  mysql-server-5.5                     5.5.35-0ubuntu0.12.04.2           MySQL database server binaries and system database setup
ii  mysql-server-core-5.5                5.5.35-0ubuntu0.12.04.2           MySQL database server binaries
ii  python-mysqldb                       1.2.3-1ubuntu0.1                  Python interface to MySQL

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

grep socket /etc/mysql/my.cnf                       
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
socket      = /var/run/mysqld/mysqld.sock
#socket=/var/lib/mysql/mysql.sock
socket      = /var/run/mysqld/mysqld.sock
socket      = /var/run/mysqld/mysqld.sock

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

/var/run/mysqld$ ls -la
total 4
drwxr-xr-x  2 mysql root   80 Apr 13 12:06 .
drwxr-xr-x 16 root  root  520 Apr 16 01:33 ..
-rw-rw----  1 mysql mysql   4 Apr 13 12:06 mysqld.pid
srwxrwxrwx  1 mysql mysql   0 Apr 13 12:06 mysqld.sock
Как это зафиксить? Как рестартануть мускул? Почему появляется такая ошибка? В чем ошибка? (мускул стандартный, ничего не менял).

Спасибо

[GrafDmitrii]

У меня такая же ошибка была. В моем случае по непонятной причине слетел пользователь мускуля. используемый программой

[anytup]

Так я даже mysql -v запустить не могу, как узнать, что юзер слетел?

[AnrDaemon]

Системный лог смотрите. Либо MySQL сервер крашится, либо не может получить доступ на запись в каталог БД.

[anytup]

mysql.err - пуст
mysql.log - пуст

[AnrDaemon]

Шутите?... Я сказал - СИСТЕМНЫЙ лог.
/var/log/syslog

[anytup]

что в grep указать? так то системный лог очень большой.

[AnrDaemon]

Подумайте?... Как минимум "mysql", а как максимум - весь лог за время, в которое сервер падал.

[anytup]

Я и спросил, потому что

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

| grep mysql ничего не вернул.
Проблема в том, что упало в 0:47, а первая запись в логах с 2:18

[AnrDaemon]

Так смотрите предыдущий лог >.<

[anytup]

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

Apr 12 23:31:35 my_site mysqld_safe[3231]: 140412 23:31:35 [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.
Apr 12 23:31:35 my_site mysqld_safe[3231]: 140412 23:31:35 [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.
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:35 my_site mysqld_safe[3231]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
Apr 12 23:31:35 my_site mysqld_safe[3231]: To do so, start the server, then issue the following commands:
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:35 my_site mysqld_safe[3231]: /usr/bin/mysqladmin -u root password 'new-password'
Apr 12 23:31:35 my_site mysqld_safe[3231]: /usr/bin/mysqladmin -u root -h my_site password 'new-password'
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:35 my_site mysqld_safe[3231]: Alternatively you can run:
Apr 12 23:31:35 my_site mysqld_safe[3231]: /usr/bin/mysql_secure_installation
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:35 my_site mysqld_safe[3231]: which will also give you the option of removing the test
Apr 12 23:31:35 my_site mysqld_safe[3231]: databases and anonymous user created by default.  This is
Apr 12 23:31:35 my_site mysqld_safe[3231]: strongly recommended for production servers.
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:35 my_site mysqld_safe[3231]: See the manual for more instructions.
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:35 my_site mysqld_safe[3231]: Please report any problems with the /usr/scripts/mysqlbug script!
Apr 12 23:31:35 my_site mysqld_safe[3231]:
Apr 12 23:31:36 my_site mysqld_safe[3278]: 140412 23:31:36 [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.
Apr 12 23:31:40 my_site mysqld_safe[3321]: 140412 23:31:40 [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.
Apr 12 23:31:41 my_site mysqld_safe[3342]: 140412 23:31:41 [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.
Apr 12 23:31:43 my_site mysqld_safe[3363]: 140412 23:31:43 [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.
Apr 12 23:31:46 my_site /etc/mysql/debian-start[3477]: Upgrading MySQL tables if necessary.
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: Looking for 'mysql' as: /usr/bin/mysql
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock'
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock'
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.columns_priv                                 OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.db                                           OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.event                                        OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.func                                         OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.general_log                                  OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.help_category                                OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.help_keyword                                 OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.help_relation                                OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.help_topic                                   OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.host                                         OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.ndb_binlog_index                             OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.plugin                                       OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.proc                                         OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.procs_priv                                   OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.proxies_priv                                 OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.servers                                      OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.slow_log                                     OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.tables_priv                                  OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.time_zone                                    OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.time_zone_leap_second                        OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.time_zone_name                               OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.time_zone_transition                         OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.time_zone_transition_type                    OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: mysql.user                                         OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: Running 'mysql_fix_privilege_tables'...
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3480]: OK
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3514]: Checking for insecure root accounts.
Apr 12 23:31:49 my_site /etc/mysql/debian-start[3519]: Triggering myisam-recover for all MyISAM tables
Apr 13 00:39:13 my_site /etc/mysql/debian-start[628]: Upgrading MySQL tables if necessary.
Apr 13 00:39:13 my_site /etc/mysql/debian-start[631]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 13 00:39:13 my_site /etc/mysql/debian-start[631]: Looking for 'mysql' as: /usr/bin/mysql
Apr 13 00:39:13 my_site /etc/mysql/debian-start[631]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 13 00:39:13 my_site /etc/mysql/debian-start[631]: This installation of MySQL is already upgraded to 5.5.35, use --force if you still need to run mysql_upgrade
Apr 13 00:39:13 my_site /etc/mysql/debian-start[642]: Checking for insecure root accounts.
Apr 13 00:39:13 my_site /etc/mysql/debian-start[647]: Triggering myisam-recover for all MyISAM tables
Что самое интересное, я не делал

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

Apr 12 23:31:35 my_site mysqld_safe[3231]: /usr/bin/mysqladmin -u root password 'new-password'
Apr 12 23:31:35 my_site mysqld_safe[3231]: /usr/bin/mysqladmin -u root -h my_site password 'new-password'

[anytup]

неужели, никто не знает?

[AnrDaemon]

Логи MySQL и системы по времени не совпадают. Сами не видиите? >.<

[anytup]

это все системные логи, где встречается упоминание mysql:

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

cat syslog.4 | grep mysql
Apr 13 11:40:08 mysite /etc/mysql/debian-start[651]: Upgrading MySQL tables if necessary.
Apr 13 11:40:08 mysite /etc/mysql/debian-start[654]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 13 11:40:08 mysite /etc/mysql/debian-start[654]: Looking for 'mysql' as: /usr/bin/mysql
Apr 13 11:40:08 mysite /etc/mysql/debian-start[654]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 13 11:40:08 mysite /etc/mysql/debian-start[654]: This installation of MySQL is already upgraded to 5.5.35, use --force if you still need to run mysql_upgrade
Apr 13 11:40:08 mysite /etc/mysql/debian-start[691]: Checking for insecure root accounts.
Apr 13 11:40:08 mysite /etc/mysql/debian-start[697]: Triggering myisam-recover for all MyISAM tables
Apr 13 12:06:23 mysite /etc/mysql/debian-start[655]: Upgrading MySQL tables if necessary.
Apr 13 12:06:23 mysite /etc/mysql/debian-start[658]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 13 12:06:23 mysite /etc/mysql/debian-start[658]: Looking for 'mysql' as: /usr/bin/mysql
Apr 13 12:06:23 mysite /etc/mysql/debian-start[658]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 13 12:06:23 mysite /etc/mysql/debian-start[658]: This installation of MySQL is already upgraded to 5.5.35, use --force if you still need to run mysql_upgrade
Apr 13 12:06:23 mysite /etc/mysql/debian-start[669]: Checking for insecure root accounts.
Apr 13 12:06:23 mysite /etc/mysql/debian-start[674]: Triggering myisam-recover for all MyISAM tables


cat syslog.5 | grep mysql
Apr 12 23:31:35 mysite mysqld_safe[3231]: 140412 23:31:35 [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.
Apr 12 23:31:35 mysite mysqld_safe[3231]: 140412 23:31:35 [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.
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:35 mysite mysqld_safe[3231]: PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
Apr 12 23:31:35 mysite mysqld_safe[3231]: To do so, start the server, then issue the following commands:
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:35 mysite mysqld_safe[3231]: /usr/bin/mysqladmin -u root password 'new-password'
Apr 12 23:31:35 mysite mysqld_safe[3231]: /usr/bin/mysqladmin -u root -h mysite password 'new-password'
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:35 mysite mysqld_safe[3231]: Alternatively you can run:
Apr 12 23:31:35 mysite mysqld_safe[3231]: /usr/bin/mysql_secure_installation
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:35 mysite mysqld_safe[3231]: which will also give you the option of removing the test
Apr 12 23:31:35 mysite mysqld_safe[3231]: databases and anonymous user created by default.  This is
Apr 12 23:31:35 mysite mysqld_safe[3231]: strongly recommended for production servers.
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:35 mysite mysqld_safe[3231]: See the manual for more instructions.
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:35 mysite mysqld_safe[3231]: Please report any problems with the /usr/scripts/mysqlbug script!
Apr 12 23:31:35 mysite mysqld_safe[3231]:
Apr 12 23:31:36 mysite mysqld_safe[3278]: 140412 23:31:36 [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.
Apr 12 23:31:40 mysite mysqld_safe[3321]: 140412 23:31:40 [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.
Apr 12 23:31:41 mysite mysqld_safe[3342]: 140412 23:31:41 [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.
Apr 12 23:31:43 mysite mysqld_safe[3363]: 140412 23:31:43 [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.
Apr 12 23:31:46 mysite /etc/mysql/debian-start[3477]: Upgrading MySQL tables if necessary.
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: Looking for 'mysql' as: /usr/bin/mysql
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock'
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock'
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.columns_priv                                 OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.db                                           OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.event                                        OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.func                                         OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.general_log                                  OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.help_category                                OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.help_keyword                                 OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.help_relation                                OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.help_topic                                   OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.host                                         OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.ndb_binlog_index                             OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.plugin                                       OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.proc                                         OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.procs_priv                                   OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.proxies_priv                                 OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.servers                                      OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.slow_log                                     OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.tables_priv                                  OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.time_zone                                    OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.time_zone_leap_second                        OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.time_zone_name                               OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.time_zone_transition                         OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.time_zone_transition_type                    OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: mysql.user                                         OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: Running 'mysql_fix_privilege_tables'...
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3480]: OK
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3514]: Checking for insecure root accounts.
Apr 12 23:31:49 mysite /etc/mysql/debian-start[3519]: Triggering myisam-recover for all MyISAM tables
Apr 13 00:39:13 mysite /etc/mysql/debian-start[628]: Upgrading MySQL tables if necessary.
Apr 13 00:39:13 mysite /etc/mysql/debian-start[631]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 13 00:39:13 mysite /etc/mysql/debian-start[631]: Looking for 'mysql' as: /usr/bin/mysql
Apr 13 00:39:13 mysite /etc/mysql/debian-start[631]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 13 00:39:13 mysite /etc/mysql/debian-start[631]: This installation of MySQL is already upgraded to 5.5.35, use --force if you still need to run mysql_upgrade
Apr 13 00:39:13 mysite /etc/mysql/debian-start[642]: Checking for insecure root accounts.
Apr 13 00:39:13 mysite /etc/mysql/debian-start[647]: Triggering myisam-recover for all MyISAM tables

cat syslog | grep mysql
Apr 18 16:12:26 mysite /etc/mysql/debian-start[625]: Upgrading MySQL tables if necessary.
Apr 18 16:12:27 mysite /etc/mysql/debian-start[628]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Apr 18 16:12:27 mysite /etc/mysql/debian-start[628]: Looking for 'mysql' as: /usr/bin/mysql
Apr 18 16:12:27 mysite /etc/mysql/debian-start[628]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 18 16:12:27 mysite /etc/mysql/debian-start[628]: This installation of MySQL is already upgraded to 5.5.35, use --force if you still need to run mysql_upgrade
Apr 18 16:12:27 mysite /etc/mysql/debian-start[663]: Checking for insecure root accounts.
Apr 18 16:12:27 mysite /etc/mysql/debian-start[668]: Triggering myisam-recover for all MyISAM tables

[AnrDaemon]

anytup, смотреть надо на все логи одновременно. То есть за одно время. Вы видите проблему в одном (mysql?) логе? Смотрите, что В ЭТО ЖЕ ВРЕМЯ происходило в соседнем (syslog?) логе.
Нет в syslog? Копайте dmesg.