Добрый день.
Прошу помочь с проблемой: после обесточивания сервера в дата-центре не запустить MySQL. Свободное место:
Запуск:
Инфо о проблеме
Запустить удается только с innodb_force_recovery = 2
mysqlcheck -u root --auto-repair --all-databases показывает все ОК.
Но после удаления innodb_force_recovery и перезапуска MySQL проблема остается:
Прошу помочь с проблемой: после обесточивания сервера в дата-центре не запустить MySQL. Свободное место:
Код |
---|
[root@nwtec ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 19G 6.3G 12G 36% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 376M 3.5G 10% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/sda1 190M 164M 13M 94% /boot /dev/sdb1 99G 7.1G 87G 8% /home tmpfs 783M 0 783M 0% /run/user/0 tmpfs 783M 0 783M 0% /run/user/600 |
Запуск:
Код |
---|
[root@nwtec ~]# service mysqld restart Redirecting to /bin/systemctl restart mysqld.service Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details. |
Цитата |
---|
[root@nwtec ~]# systemctl status mysqld.service -l ● mysqld.service - MySQL Server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled) Active: activating (start) since Tue 2019-11-05 09:15:06 MSK; 3s ago Docs: man:mysqld(8) Process: 1903 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS) Main PID: 31858 (code=exited, status=0/SUCCESS); : 1927 (mysqld) CGroup: /system.slice/mysqld.service ├─1927 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid └─1930 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.408375Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.511151Z 0 [Note] InnoDB: Completed initialization of buffer pool Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.557592Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.666198Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.724188Z 0 [Note] InnoDB: Highest supported file format is Barracuda. Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.760008Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 91280744153 Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.760047Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 91280744872 Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.760095Z 0 [Note] InnoDB: Database was not shutdown normally! Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.760103Z 0 [Note] InnoDB: Starting crash recovery. Nov 05 09:15:06 nwtec.ru mysqld[1927]: 2019-11-05T06:15:06.940825Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes |
mysqlcheck -u root --auto-repair --all-databases показывает все ОК.
Но после удаления innodb_force_recovery и перезапуска MySQL проблема остается:
Цитата |
---|
[root@nwtec ~]# service mysqld restart Redirecting to /bin/systemctl restart mysqld.service Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details. [root@nwtec ~]# systemctl status mysqld.service -l ● mysqld.service - MySQL Server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled) Active: activating (start) since Tue 2019-11-05 09:20:00 MSK; 503ms ago Docs: man:mysqld(8) Process: 3667 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS) Main PID: 3358 (code=exited, status=0/SUCCESS); : 3691 (mysqld) CGroup: /system.slice/mysqld.service ├─3691 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid └─3694 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.650562Z 0 [Note] InnoDB: Uses event mutexes Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.650567Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.650583Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7 Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.650589Z 0 [Note] InnoDB: Using Linux native AIO Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.650931Z 0 [Note] InnoDB: Number of pools: 1 Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.651101Z 0 [Note] InnoDB: Using CPU crc32 instructions Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.659595Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.763948Z 0 [Note] InnoDB: Completed initialization of buffer pool Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.810829Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). Nov 05 09:20:00 nwtec.ru mysqld[3691]: 2019-11-05T06:20:00.906738Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite |
Код |
---|
[root@nwtec ~]# journalctl -xe -- Subject: Unit mysqld.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mysqld.service has failed. -- -- The result is failed. Nov 05 09:21:50 nwtec.ru systemd[1]: Unit mysqld.service entered failed state. Nov 05 09:21:50 nwtec.ru systemd[1]: mysqld.service failed. Nov 05 09:21:50 nwtec.ru systemd[1]: mysqld.service holdoff time over, scheduling restart. Nov 05 09:21:50 nwtec.ru systemd[1]: Stopped MySQL Server. -- Subject: Unit mysqld.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mysqld.service has finished shutting down. Nov 05 09:21:50 nwtec.ru systemd[1]: Starting MySQL Server... -- Subject: Unit mysqld.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mysqld.service has begun starting up. Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.712564Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 24642) Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.712911Z 0 [Warning] Changed limits: table_open_cache: 2467 (requested 12288) Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.889688Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set. Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.890991Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.25-28) starting as process 5412 ... Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.900687Z 0 [Note] InnoDB: PUNCH HOLE support available Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.900742Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.900749Z 0 [Note] InnoDB: Uses event mutexes Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.900755Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.900762Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7 Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.900767Z 0 [Note] InnoDB: Using Linux native AIO Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.901126Z 0 [Note] InnoDB: Number of pools: 1 Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.901289Z 0 [Note] InnoDB: Using CPU crc32 instructions Nov 05 09:21:50 nwtec.ru mysqld[5409]: 2019-11-05T06:21:50.922227Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.026848Z 0 [Note] InnoDB: Completed initialization of buffer pool Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.073883Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man pag Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.165590Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.210073Z 0 [Note] InnoDB: Highest supported file format is Barracuda. Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.246443Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 91280745385 Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.246479Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 91280745952 Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.246511Z 0 [Note] InnoDB: Database was not shutdown normally! Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.246518Z 0 [Note] InnoDB: Starting crash recovery. Nov 05 09:21:51 nwtec.ru mysqld[5409]: 2019-11-05T06:21:51.402899Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes |