Форум пользователей MySQL

Здравствуйте. Обновил mysql с версии 5.5.60 до 5.7.23 всё проработало минут 20-30, после чего mysql упал и больше не поднимался

journalctl -xe

июл 31 17:18:11 server01new systemd[1]: Failed to start MySQL Community Server.
-- Subject: Ошибка юнита mysql.service
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Произошел сбой юнита mysql.service.
--
-- Результат: failed.
июл 31 17:18:11 server01new systemd[1]: mysql.service: Unit entered failed state.
июл 31 17:18:11 server01new systemd[1]: mysql.service: Failed with result 'exit-code'.
июл 31 17:18:12 server01new systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
июл 31 17:18:12 server01new systemd[1]: Stopped MySQL Community Server.
-- Subject: Завершена остановка юнита mysql.service.
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Процесс остановки юнита mysql.service был завершен.
июл 31 17:18:12 server01new systemd[1]: Starting MySQL Community Server...
-- Subject: Начинается запуск юнита mysql.service
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Начат процесс запуска юнита mysql.service.
июл 31 17:18:13 server01new mysqld[24651]: Unable to determine if daemon is running: No such file or directory
июл 31 17:18:13 server01new systemd[1]: mysql.service: Control process exited, code=exited status=1
июл 31 17:18:13 server01new systemd[1]: Failed to start MySQL Community Server.
-- Subject: Ошибка юнита mysql.service
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Произошел сбой юнита mysql.service.
--
-- Результат: failed.
июл 31 17:18:13 server01new systemd[1]: mysql.service: Unit entered failed state.
июл 31 17:18:13 server01new systemd[1]: mysql.service: Failed with result 'exit-code'.
июл 31 17:18:14 server01new systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
июл 31 17:18:14 server01new systemd[1]: Stopped MySQL Community Server.
-- Subject: Завершена остановка юнита mysql.service.
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Процесс остановки юнита mysql.service был завершен.
июл 31 17:18:14 server01new systemd[1]: Starting MySQL Community Server...
-- Subject: Начинается запуск юнита mysql.service
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Начат процесс запуска юнита mysql.service.


из error.log

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-07-31T13:00:28.381393Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-07-31T13:00:28.384851Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.23) starting as process 23226 ...
2018-07-31T13:00:28.391094Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-07-31T13:00:28.391137Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-07-31T13:00:28.391150Z 0 [Note] InnoDB: Uses event mutexes
2018-07-31T13:00:28.391163Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-07-31T13:00:28.391175Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-07-31T13:00:28.391186Z 0 [Note] InnoDB: Using Linux native AIO
2018-07-31T13:00:28.391628Z 0 [Note] InnoDB: Number of pools: 1
2018-07-31T13:00:28.391798Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2018-07-31T13:00:28.394255Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-07-31T13:00:28.410889Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-07-31T13:00:28.413520Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-07-31T13:00:28.427707Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-07-31T13:00:28.429142Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 283496662954
2018-07-31T13:00:28.641987Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 283498490526
2018-07-31T13:00:28.646159Z 0 [Note] InnoDB: Database was not shutdown normally!
2018-07-31T13:00:28.646176Z 0 [Note] InnoDB: Starting crash recovery.
2018-07-31T13:00:28.730604Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
2018-07-31T13:00:29.328707Z 0 [Note] InnoDB: Apply batch completed
2018-07-31T13:00:29.441067Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-07-31T13:00:29.441103Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-07-31T13:00:29.441183Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-07-31T13:00:29.619329Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-07-31T13:00:29.621086Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-07-31T13:00:29.621107Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-07-31T13:00:29.622326Z 0 [Note] InnoDB: 5.7.23 started; log sequence number 283498490526
2018-07-31T13:00:29.622805Z 0 [Note] Plugin 'FEDERATED' is disabled.
2018-07-31T13:00:29.623458Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2018-07-31T13:00:29.629047Z 0 [Warning] System table 'plugin' is expected to be transactional.
2018-07-31 17:00:29 0x9acf9b40  InnoDB: Assertion failure in thread 2597296960 in file os0file.cc line 1699
InnoDB: Failing assertion: offset > 0
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/ … overy.html
InnoDB: about forcing recovery.
13:00:29 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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 67527 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x9dd00468
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 9acf92bc thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x28)[0x8a82c18]
/usr/sbin/mysqld(handle_fatal_signal+0x406)[0x83a7dd6]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xb77bfd2c]
linux-gate.so.1(__kernel_vsyscall+0x9)[0xb77bfd21]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(gsignal+0x47)[0xb745b367]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(abort+0x143)[0xb745ca23]
/usr/sbin/mysqld[0x837dc2f]
/usr/sbin/mysqld[0x8c0d9bb]
/usr/sbin/mysqld[0x8c0df86]
/usr/sbin/mysqld[0x8c0e0b0]
2018-07-31T13:00:29.637144Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2018-07-31T13:00:29.637199Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
/usr/sbin/mysqld[0x8c13076]
/usr/sbin/mysqld(_Z17os_file_read_funcR9IORequestiPvym+0x21)[0x8c133d1]
/usr/sbin/mysqld(_Z11os_aio_funcR9IORequestmPKc13pfs_os_file_tPvymbP10fil_node_tS4_+0x176)[0x8c13cd6]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0xb63)[0x8def083]
2018-07-31T13:00:29.642551Z 0 [Warning] CA certificate ca.pem is self signed.
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xc6)[0x8d9c666]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x314)[0x8d69b84]
/usr/sbin/mysqld(_Z19xdes_get_descriptormmRK11page_size_tP5mtr_t+0x1f2)[0x8df4712]
/usr/sbin/mysqld[0x8df7753]
/usr/sbin/mysqld(_Z14fseg_free_pagePhmmbP5mtr_t+0x1bb)[0x8df904b]
/usr/sbin/mysqld(_Z17btr_page_free_lowP12dict_index_tP11buf_block_tmP5mtr_t+0x65)[0x8d337a5]
/usr/sbin/mysqld(_Z13btr_page_freeP12dict_index_tP11buf_block_tP5mtr_t+0x32)[0x8d33822]
/usr/sbin/mysqld(_Z12btr_compressP9btr_cur_tmP5mtr_t+0xc63)[0x8d3b4c3]
/usr/sbin/mysqld(_Z26btr_cur_compress_if_usefulP9btr_cur_tmP5mtr_t+0x199)[0x8d47fc9]
/usr/sbin/mysqld(_Z26btr_cur_pessimistic_deleteP7dberr_tmP9btr_cur_tmbP5mtr_t+0x433)[0x8d4b543]
2018-07-31T13:00:29.662547Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2018-07-31T13:00:29.662582Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2018-07-31T13:00:29.662675Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2018-07-31T13:00:29.662950Z 0 [Warning] Failed to open optimizer cost constant tables

/usr/sbin/mysqld[0x8c919c1]
/usr/sbin/mysqld(_Z14row_purge_stepP9que_thr_t+0x41e)[0x8c936be]
/usr/sbin/mysqld(_Z15que_run_threadsP9que_thr_t+0xa18)[0x8c3fa28]
/usr/sbin/mysqld(srv_worker_thread+0x476)[0x8cc6516]
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0(+0x6ecb)[0xb7786ecb]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(clone+0x5e)[0xb7518d0e]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.



UPD: Запустил через

[mysqld]
innodb_force_recovery = 2

Сейчас вопрос в том, что послужило причиной падения? Какая-то база?

Отредактированно deminart (31.07.2018 19:15:48)