Вот из еррор.лог
Цитата |
---|
2019-05-05T03:58:45.138904Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 16246) 2019-05-05T03:58:45.139066Z 0 [Warning] Changed limits: table_open_cache: 2473 (requested 8096) 2019-05-05T03:58:45.283444Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set. 2019-05-05T03:58:45.284404Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-21) starting as process 16755 ... 2019-05-05T03:58:45.288204Z 0 [Note] InnoDB: PUNCH HOLE support available 2019-05-05T03:58:45.288232Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-05-05T03:58:45.288235Z 0 [Note] InnoDB: Uses event mutexes 2019-05-05T03:58:45.288239Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-05-05T03:58:45.288242Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7 2019-05-05T03:58:45.288248Z 0 [Note] InnoDB: Using Linux native AIO 2019-05-05T03:58:45.288409Z 0 [Note] InnoDB: Number of pools: 1 2019-05-05T03:58:45.288483Z 0 [Note] InnoDB: Using CPU crc32 instructions 2019-05-05T03:58:45.289745Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M 2019-05-05T03:58:45.309553Z 0 [Note] InnoDB: Completed initialization of buffer pool 2019-05-05T03:58:45.315954Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2019-05-05T03:58:45.333722Z 0 [Note] InnoDB: Recovering partial pages fr om the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite 2019-05-05T03:58:45.368434Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2019-05-05T03:58:45.371743Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12164232838 2019-05-05T03:58:45.371785Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 12164271377 2019-05-05T03:58:45.373488Z 0 [Note] InnoDB: Database was not shutdown normally! 2019-05-05T03:58:45.373504Z 0 [Note] InnoDB: Starting crash recovery. 2019-05-05T03:58:45.857160Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes 2019-05-05T03:58:45.921864Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 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 03:58:45 UTC - mysqld got signal 11 ; 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 key_buffer_size=50331648 read_buffer_size=131072 max_used_connections=0 max_threads=44 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 = 407533 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... 61 stack_bottom = 0 thread_stack 0x20000 62 63 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xef5c1b] |