@Hakas_Lepehen

После некорректного отключения виртуалки не запускается MySQL. Почему?

Доброго времени суток Читателю этого вопроса.

Имеется виртуалка на которой запущен портал на битриксе. После непрогнозируемого отключения питания на сервере - не запускается сервер БД.
вырезка части ошибок из error.log
```
You may download the Percona Server operations manual by visiting
www.percona.com/software/percona-server. You may find information
in the manual which will help you identify the cause of the crash.
2021-01-14T04:09:54.900650Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 24642)
2021-01-14T04:09:54.900903Z 0 [Warning] Changed limits: table_open_cache: 2467 (requested 12288)
2021-01-14T04:09:55.050320Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2021-01-14T04:09:55.051299Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.29-32) starting as process 16723 ...
2021-01-14T04:09:55.057549Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-01-14T04:09:55.057603Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-01-14T04:09:55.057607Z 0 [Note] InnoDB: Uses event mutexes
2021-01-14T04:09:55.057610Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-01-14T04:09:55.057613Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2021-01-14T04:09:55.057616Z 0 [Note] InnoDB: Using Linux native AIO
2021-01-14T04:09:55.057773Z 0 [Note] InnoDB: Number of pools: 1
2021-01-14T04:09:55.057851Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-01-14T04:09:55.059591Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M
2021-01-14T04:09:55.120068Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-01-14T04:09:55.138373Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-01-14T04:09:55.191337Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2021-01-14T04:09:55.227301Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-01-14T04:09:55.237659Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 105797597060
2021-01-14T04:09:55.237699Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 105797597107
2021-01-14T04:09:55.237711Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-01-14T04:09:55.237715Z 0 [Note] InnoDB: Starting crash recovery.
2021-01-14T04:09:55.291477Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes
2021-01-14T04:09:55.296471Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=45] log sequence number 105797609576 is in the future! Current system log sequence number 105797597116.
2021-01-14T04:09:55.296503Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec... for information about forcing recovery.
2021-01-14T04:09:55.296640Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=598] log sequence number 105797609576 is in the future! Current system log sequence number 105797597116.
2021-01-14T04:09:55.296650Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec... for information about forcing recovery.
2021-01-14T04:09:55.296857Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=335] log sequence number 105797599538 is in the future! Current system log sequence number 105797597116.
2021-01-14T04:09:55.296867Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec... for information about forcing recovery.
2021-01-14T04:09:55.297028Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=46] log sequence number 105797609654 is in the future! Current system log sequence number 105797597116.
2021-01-14T04:09:55.297040Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec... for information about forcing recovery.
2021-01-14T04:09:55.297532Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 105797609732 is in the future! Current system log sequence number 105797597116.
```
  • Вопрос задан
  • 287 просмотров
Пригласить эксперта
Ответы на вопрос 1
402d
@402d
начинал с бейсика на УКНЦ в 1988
моя ставка на "пропал куда-то конфиг mysql"
а что конкретно и как пропал телепатия бессильна.
Может физически стерся. может пути потерлись. может он как параметр передавался или еще чего
Ответ написан
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Похожие вопросы