Не стартует mysql
in the manual which will help you identify the cause of the crash.
2018-10-01T11:20:44.356181Z 0 [Warning] Changed limits: max_open_files: 5000max_ (requested 16238)
2018-10-01T11:20:44.356451Z 0 [Warning] Changed limits: table_open_cache: 2477 (requested 8096)
2018-10-01T11:20:44.599328Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2018-10-01T11:20:44.600471Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.23-23-log) starting as process 9271 ...
2018-10-01T11:20:44.622430Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-10-01T11:20:44.622486Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-01T11:20:44.622492Z 0 [Note] InnoDB: Uses event mutexes
2018-10-01T11:20:44.622499Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-10-01T11:20:44.622506Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2018-10-01T11:20:44.622513Z 0 [Note] InnoDB: Using Linux native AIO
2018-10-01T11:20:44.622738Z 0 [Note] InnoDB: Number of pools: 1
2018-10-01T11:20:44.622856Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-10-01T11:20:44.633151Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
2018-10-01T11:20:44.644920Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-10-01T11:20:44.664473Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-10-01T11:20:44.705692Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2018-10-01T11:20:44.711435Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-01T11:20:44.713489Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5097840291
2018-10-01T11:20:44.713545Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 5097868313
2018-10-01T11:20:44.715416Z 0 [Note] InnoDB: Database was not shutdown normally!
2018-10-01T11:20:44.715448Z 0 [Note] InnoDB: Starting crash recovery.
2018-10-01T11:20:45.382046Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 3932160 bytes
2018-10-01T11:20:47.134693Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-10-01T11:20:47.134741Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-10-01T11:20:47.134799Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-10-01T11:20:47.196062Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-10-01T11:20:47.197255Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-10-01T11:20:47.197291Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-10-01T11:20:47.219341Z 0 [Note] InnoDB: Waiting for purge to start
2018-10-01 14:20:47 0x7f777f7fe700 InnoDB: Assertion failure in thread 140151216924416 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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:
dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec...
InnoDB: about forcing recovery.
11:20:47 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
bugs.percona.com
key_buffer_size=25165824
read_buffer_size=131072
max_used_connections=0
max_threads=36
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 = 172925 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f7778000900
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 = 7f777f7fdcb0 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf0077b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0x7a5161]
/lib64/libpthread.so.0(+0xf6d0)[0x7f77bd6ee6d0]
/lib64/libc.so.6(gsignal+0x37)[0x7f77bb7ef277]
/lib64/libc.so.6(abort+0x148)[0x7f77bb7f0968]
/usr/sbin/mysqld[0x772564]
/usr/sbin/mysqld[0x772052]
/usr/sbin/mysqld[0x10faa75]
/usr/sbin/mysqld[0x10fcb8e]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10ff499]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xa47)[0x10d92a7]
/lib64/libpthread.so.0(+0x7e25)[0x7f77bd6e6e25]
/lib64/libc.so.6(clone+0x6d)[0x7f77bb8b7bad]
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
Простой
Средний
