Цитата |
---|
Евгений Костюк написал: Надеюсь вы не запускали команду смены владельцев файлов для mysql? Я когда-то случайно запустил chown -R bitrix:bitrix /home и у меня база mysql лежала в /home так у меня сразу лег сервер и я минут 10 не мог понять в чем дело, пока не обнаружил что файлы базы данных не принадлежат пользователя мускула, а значит он не может с ними работать. И ошибки были очень похожие. Но возможно в вашем случае что-то другое мешает... |
Код |
---|
2021-02-12T06:58:46.408627Z 0 [Note] InnoDB: Uses event mutexes 2021-02-12T06:58:46.408631Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2021-02-12T06:58:46.408635Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7 2021-02-12T06:58:46.408641Z 0 [Note] InnoDB: Using Linux native AIO 2021-02-12T06:58:46.412793Z 0 [Note] InnoDB: Number of pools: 1 2021-02-12T06:58:46.421153Z 0 [Note] InnoDB: Using CPU crc32 instructions 2021-02-12T06:58:46.424856Z 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 8, chunk size = 128M 2021-02-12T06:58:46.668310Z 0 [Note] InnoDB: Completed initialization of buffer pool 2021-02-12T06:58:46.741337Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2021-02-12T06:58:46.934793Z 0 [Note] InnoDB: Recovering partial pages fr om the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite 2021-02-12T06:58:47.590513Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2021-02-12T06:58:47.769776Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 186078784162 2021-02-12T06:58:49.214514Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 186078964268 2021-02-12T06:58:49.216352Z 0 [Note] InnoDB: Database was not shutdown normally! 2021-02-12T06:58:49.216366Z 0 [Note] InnoDB: Starting crash recovery. 2021-02-12T06:58:49.443509Z 0 [Note] InnoDB: Database page corruption or a failed file read of page [page id: space=0, page number=532]. Trying to recover it from the doublewrite buffer. 2021-02-12T06:58:49.443579Z 0 [ERROR] InnoDB: Dump of the page: 2021-02-12T06:58:49.443591Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): тут дамп InnoDB: End of page dump 2021-02-12T06:58:49.494442Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 2049606457, calculated checksums for field1: crc32 1145418102/2917252669, innodb 1666644705, none 3735928559, stored checksum in field2 2049606457, calculated checksums for field2: crc32 1145418102/2917252669, innodb 2223021145, none 3735928559, page LSN 43 1395177334, low 4 bytes of LSN at page end 1395177334, page number (if stored to page already) 532, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an upd ate undo log page 2021-02-12T06:58:49.494456Z 0 [ERROR] InnoDB: Dump of corresponding page in doublewrite buffer: 2021-02-12T06:58:49.494462Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): и тут дамп InnoDB: End of page dump 2021-02-12T06:58:49.546252Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 2049606457, calculated checksums for field1: crc32 1847096793/2883168024, innodb 2230298171, none 3735928559, stored checksum in field2 2049606457, calculated checksums for field2: crc32 1847096793/2883168024, innodb 2223021145, none 3735928559, page LSN 43 1395177334, low 4 bytes of LSN at page end 1395177334, page number (if stored to page already) 532, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an update undo log page 2021-02-12T06:58:49.546277Z 0 [ERROR] [FATAL] InnoDB: The page in the doublewrite buffer is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6 2021-02-12 09:58:49 0x7f338c65a880 InnoDB: Assertion failure in thread 139859375532160 in file ut0ut.cc line 943 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 06:58:49 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. Please help us make Percona Server better by reporting any bugs at http://bugs.percona.com/ key_buffer_size=100663296 read_buffer_size=131072 max_used_connections=0 max_threads=86 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1677119 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out wh ere mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x80000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xef5c1b] /usr/sbin/mysqld(handle_fatal_signal+0x471)[0x79b061] /lib64/libpthread.so.0(+0xf6d0)[0x7f338c2426d0] /lib64/libc.so.6(gsignal+0x37)[0x7f338a343277] /lib64/libc.so.6(abort+0x148)[0x7f338a344968] /usr/sbin/mysqld[0x7687ec] /usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x118284d] /usr/sbin/mysqld(_Z17buf_dblwr_processv+0x10ee)[0x11d144e] /usr/sbin/mysqld(_Z35recv_recovery_from_checkpoint_startm+0x1f90)[0x1052820] /usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3f11)[0x112dff1] /usr/sbin/mysqld[0xfe27d1] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7fd031] /usr/sbin/mysqld[0xce7545] /usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0xced600] /usr/sbin/mysqld[0x7913bd] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0xabd)[0x794e3d] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f338a32f445] /usr/sbin/mysqld[0x78a234] You may download the Percona Server operations manual by visiting http://www.percona.com/software/percona-server/. You may find information in the manual which will help you identify the cause of the crash. |
Цитата | ||||||
---|---|---|---|---|---|---|
red_eye написал:
В вашей цитате лишние пробелы в командах. Создайте новую чистую директорию /var/lib/mysql Выдайте на неё права И попробуйте использовать эту команду.
Протестировал на percona 5.7, создалось без проблем. Будет создан новый пароль
|
потому что в логах было
Код |
---|
2021-02-14T21:35:19.205156Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not se t. 2021-02-14T21:35:19.846426Z 0 [Warning] InnoDB: New log files created, LSN=45790 2021-02-14T21:35:19.942913Z 0 [Warning] InnoDB: Creating foreign key constraint system tables. 2021-02-14T21:35:19.998079Z 0 [ERROR] unknown variable 'force_recovery=6' 2021-02-14T21:35:19.998095Z 0 [ERROR] Aborting |