Как исправит ошибки в mysql?

Question

[NikoNovr]

Добрый вечер
После рестарта появились проблемы с отображением онлайна и статистики
Мне сказали проблемы со stocket
Вот mysql.log

161217 6:09:18 [Note] /usr/sbin/mysqld: Normal shutdown
161217 6:09:18 [Note] Event Scheduler: Purging the queue. 0 events
161217 6:09:19 InnoDB: Starting shutdown...
161217 6:09:21 InnoDB: Shutdown completed; log sequence number 4184323
161217 6:09:21 [Note] /usr/sbin/mysqld: Shutdown complete
161217 06:09:21 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
161217 06:09:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161217 6:09:46 [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.
161217 6:09:46 [Note] /usr/sbin/mysqld (mysqld 5.5.53-0+deb8u1) starting as process 1654 ...
161217 6:09:47 [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.
161217 6:09:47 [Note] Plugin 'FEDERATED' is disabled.
161217 6:09:47 InnoDB: The InnoDB memory heap is disabled
161217 6:09:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161217 6:09:47 InnoDB: Compressed tables use zlib 1.2.8
161217 6:09:47 InnoDB: Using Linux native AIO
161217 6:09:47 InnoDB: Initializing buffer pool, size = 128.0M
161217 6:09:47 InnoDB: Completed initialization of buffer pool
161217 6:09:47 InnoDB: highest supported file format is Barracuda.
161217 6:09:49 InnoDB: Waiting for the background threads to start
161217 6:09:50 InnoDB: 5.5.53 started; log sequence number 4184323
161217 6:09:50 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161217 6:09:50 [Note] - '0.0.0.0' resolves to '0.0.0.0';
161217 6:09:50 [Note] Server socket created on IP: '0.0.0.0'.
161217 6:09:52 [Note] Event Scheduler: Loaded 0 events
161217 6:09:52 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.53-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
161217 6:30:52 [Warning] IP address '204.44.80.165' has been resolved to the host name '204.44.80.165.static.quadranet.com', which resembles IPv4-address itself.
161217 10:21:27 [Note] /usr/sbin/mysqld: Normal shutdown
161217 10:21:27 [Note] Event Scheduler: Purging the queue. 0 events
161217 10:21:27 InnoDB: Starting shutdown...
161217 10:21:30 InnoDB: Shutdown completed; log sequence number 4189560
161217 10:21:30 [Note] /usr/sbin/mysqld: Shutdown complete
161217 10:21:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
161217 10:21:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161217 10:21:30 [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.
161217 10:21:30 [Note] /usr/sbin/mysqld (mysqld 5.5.53-0+deb8u1) starting as process 11176 ...
161217 10:21:30 [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.
161217 10:21:30 [Note] Plugin 'FEDERATED' is disabled.
161217 10:21:30 InnoDB: The InnoDB memory heap is disabled
161217 10:21:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161217 10:21:30 InnoDB: Compressed tables use zlib 1.2.8
161217 10:21:30 InnoDB: Using Linux native AIO
161217 10:21:30 InnoDB: Initializing buffer pool, size = 128.0M
161217 10:21:30 InnoDB: Completed initialization of buffer pool
161217 10:21:30 InnoDB: highest supported file format is Barracuda.
161217 10:21:30 InnoDB: Waiting for the background threads to start
161217 10:21:31 InnoDB: 5.5.53 started; log sequence number 4189560
161217 10:21:31 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161217 10:21:31 [Note] - '0.0.0.0' resolves to '0.0.0.0';
161217 10:21:31 [Note] Server socket created on IP: '0.0.0.0'.
161217 10:21:31 [Note] Event Scheduler: Loaded 0 events
161217 10:21:31 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.53-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
161217 12:42:15 [Warning] IP address '104.223.180.19' could not be resolved: Name or service not known
161217 15:47:59 [Warning] IP address '123.249.45.197' could not be resolved: Name or service not known
161217 19:15:42 [Warning] IP address '222.186.34.102' could not be resolved: Name or service not known

Прощу помощи в исправлении
При необходимости оплачу

Comments

[Макс]

не совсем понятно - а что не работает то? в логах ничего такого страшного нет

[NikoNovr]

Макс: socket
Не отображает онлайн на сайте

[Макс]

NikoNovr: т.е. сервер не доступен?

Answer 1

[cap_nemo]

Как раз сокеты вроде бы успешно созданы у вас.

Может проблемы из-за этого?
161217 12:42:15 [Warning] IP address '104.223.180.19' could not be resolved: Name or service not known
161217 15:47:59 [Warning] IP address '123.249.45.197' could not be resolved: Name or service not known
161217 19:15:42 [Warning] IP address '222.186.34.102' could not be resolved: Name or service not known

Есть предположение, что это связано с описанием пользователей при наделениями их полномочиями.
Где-то фигурируют эти IP. Может быть вам поможет отключение reverseDNS в конфигурации MySQL.
Ищите skip_name_resolve в my.cnf

Comments

[NikoNovr]

Спасибо за ответ
но в my.cnf нету skip_name_resolve
Может в чем то еще может быть проблема?

[cap_nemo]

Если нет, значит это можно включить. Не все параметры описаны в конфиге mysql.
Лучше IP вообще не прописывать в пользователей, а делать это через /hosts

В раздел:
[mysqld]
...
skip-name-resolve

Потом сервис рестартуем, хлопаем в ладоши, и выкатываем бочонок вкусного пива :-)

Answer 2

[Руслан Федосеев]

В этом логе нет никаких ошибок. Проверяйте приложение.