1Panel
1Panel copied to clipboard
1Panel-dev
[BUG]手动备份的快照恢复失败
联系方式
No response
1Panel 版本
1.9.6
问题描述
恢复后，mysql存在问题
1Panel-mysql-JhRU | 2024-02-11T17:14:20.016209Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... 1Panel-mysql-JhRU | InnoDB: Progress in percent: 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 17:14:20 UTC - mysqld got signal 11 ; 1Panel-mysql-JhRU | This could be because you hit a bug. It is also possible that this binary 1Panel-mysql-JhRU | or one of the libraries it was linked against is corrupt, improperly built, 1Panel-mysql-JhRU | or misconfigured. This error can also be caused by malfunctioning hardware. 1Panel-mysql-JhRU | Attempting to collect some information that could help diagnose the problem. 1Panel-mysql-JhRU | As this is a crash and something is definitely wrong, the information 1Panel-mysql-JhRU | collection process might fail. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | key_buffer_size=8388608 1Panel-mysql-JhRU | read_buffer_size=131072 1Panel-mysql-JhRU | max_used_connections=0 1Panel-mysql-JhRU | max_threads=151 1Panel-mysql-JhRU | thread_count=0 1Panel-mysql-JhRU | connection_count=0 1Panel-mysql-JhRU | It is possible that mysqld could use up to 1Panel-mysql-JhRU | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory 1Panel-mysql-JhRU | Hope that's ok; if not, decrease some variables in the equation. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | Thread pointer: 0x0 1Panel-mysql-JhRU | Attempting backtrace. You can use the following information to find out 1Panel-mysql-JhRU | where mysqld died. If you see no messages after this, something went 1Panel-mysql-JhRU | terribly wrong... 1Panel-mysql-JhRU | 84 85 86 87 88 stack_bottom = 0 thread_stack 0x40000 1Panel-mysql-JhRU | 89 90 91 92 93 94 95 96 97 98 99 mysqld(my_print_stacktrace+0x3b)[0xf11c0b] 1Panel-mysql-JhRU | mysqld(handle_fatal_signal+0x486)[0x79f7d6] 1Panel-mysql-JhRU | /lib64/libpthread.so.0(+0xf8c0)[0x7faf428668c0] 1Panel-mysql-JhRU | 2024-02-11 12:14:23-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | 2024-02-11 12:14:23-05:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 1Panel-mysql-JhRU | 2024-02-11 12:14:23-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' 1Panel-mysql-JhRU | 2024-02-11T17:14:23.912242Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ... 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915516Z 0 [Note] InnoDB: PUNCH HOLE support available 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915561Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915565Z 0 [Note] InnoDB: Uses event mutexes 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915568Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915571Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915574Z 0 [Note] InnoDB: Using Linux native AIO 1Panel-mysql-JhRU | 2024-02-11T17:14:23.915868Z 0 [Note] InnoDB: Number of pools: 1 1Panel-mysql-JhRU | 2024-02-11T17:14:23.916000Z 0 [Note] InnoDB: Using CPU crc32 instructions 1Panel-mysql-JhRU | 2024-02-11T17:14:23.917874Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 1Panel-mysql-JhRU | 2024-02-11T17:14:23.924604Z 0 [Note] InnoDB: Completed initialization of buffer pool 1Panel-mysql-JhRU | 2024-02-11T17:14:23.927788Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 1Panel-mysql-JhRU | 2024-02-11T17:14:23.939568Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 1Panel-mysql-JhRU | 2024-02-11T17:14:23.940949Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438668919 1Panel-mysql-JhRU | 2024-02-11T17:14:23.940972Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 438670384 1Panel-mysql-JhRU | 2024-02-11T17:14:23.941135Z 0 [Note] InnoDB: Database was not shutdown normally! 1Panel-mysql-JhRU | 2024-02-11T17:14:23.941140Z 0 [Note] InnoDB: Starting crash recovery. 1Panel-mysql-JhRU | 2024-02-11T17:14:23.946826Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... 1Panel-mysql-JhRU | InnoDB: Progress in percent: 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 17:14:23 UTC - mysqld got signal 11 ; 1Panel-mysql-JhRU | This could be because you hit a bug. It is also possible that this binary 1Panel-mysql-JhRU | or one of the libraries it was linked against is corrupt, improperly built, 1Panel-mysql-JhRU | or misconfigured. This error can also be caused by malfunctioning hardware. 1Panel-mysql-JhRU | Attempting to collect some information that could help diagnose the problem. 1Panel-mysql-JhRU | As this is a crash and something is definitely wrong, the information 1Panel-mysql-JhRU | collection process might fail. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | key_buffer_size=8388608 1Panel-mysql-JhRU | read_buffer_size=131072 1Panel-mysql-JhRU | max_used_connections=0 1Panel-mysql-JhRU | max_threads=151 1Panel-mysql-JhRU | thread_count=0 1Panel-mysql-JhRU | connection_count=0 1Panel-mysql-JhRU | It is possible that mysqld could use up to 1Panel-mysql-JhRU | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory 1Panel-mysql-JhRU | Hope that's ok; if not, decrease some variables in the equation. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | Thread pointer: 0x0 1Panel-mysql-JhRU | Attempting backtrace. You can use the following information to find out 1Panel-mysql-JhRU | where mysqld died. If you see no messages after this, something went 1Panel-mysql-JhRU | terribly wrong... 1Panel-mysql-JhRU | stack_bottom = 0 thread_stack 0x40000 1Panel-mysql-JhRU | mysqld(my_print_stacktrace+0x3b)[0xf11c0b] 1Panel-mysql-JhRU | mysqld(handle_fatal_signal+0x486)[0x79f7d6] 1Panel-mysql-JhRU | /lib64/libpthread.so.0(+0xf8c0)[0x7f23edbfe8c0] 1Panel-mysql-JhRU | mysqld(_Z23page_cur_insert_rec_lowPhP12dict_index_tPKhPmP5mtr_t+0x2fb)[0xfdbfeb] 1Panel-mysql-JhRU | mysqld(_Z25page_cur_parse_insert_recmPKhS0_P11buf_block_tP12dict_index_tP5mtr_t+0x675)[0xfde995] 1Panel-mysql-JhRU | mysqld[0xfb7ad7] 1Panel-mysql-JhRU | mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0x99e)[0xfb86ee] 1Panel-mysql-JhRU | mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x41d)[0x112db2d] 1Panel-mysql-JhRU | mysqld(_Z12fil_aio_waitm+0x15f)[0x11a3eaf] 1Panel-mysql-JhRU | mysqld(io_handler_thread+0x88)[0x108a5c8] 1Panel-mysql-JhRU | /lib64/libpthread.so.0(+0x8105)[0x7f23edbf7105] 1Panel-mysql-JhRU | /lib64/libc.so.6(clone+0x6d)[0x7f23ebfd9b2d] 1Panel-mysql-JhRU | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 1Panel-mysql-JhRU | information that should help you find out what is causing the crash. 1Panel-mysql-JhRU | 2024-02-11 12:14:27-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | 2024-02-11 12:14:27-05:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 1Panel-mysql-JhRU | 2024-02-11 12:14:27-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' 1Panel-mysql-JhRU | 2024-02-11T17:14:28.203102Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ... 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206235Z 0 [Note] InnoDB: PUNCH HOLE support available 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206280Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206284Z 0 [Note] InnoDB: Uses event mutexes 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206286Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206289Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206294Z 0 [Note] InnoDB: Using Linux native AIO 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206534Z 0 [Note] InnoDB: Number of pools: 1 1Panel-mysql-JhRU | 2024-02-11T17:14:28.206677Z 0 [Note] InnoDB: Using CPU crc32 instructions 1Panel-mysql-JhRU | 2024-02-11T17:14:28.208805Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 1Panel-mysql-JhRU | 2024-02-11T17:14:28.215105Z 0 [Note] InnoDB: Completed initialization of buffer pool 1Panel-mysql-JhRU | 2024-02-11T17:14:28.219015Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 1Panel-mysql-JhRU | 2024-02-11T17:14:28.231109Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 1Panel-mysql-JhRU | 2024-02-11T17:14:28.232423Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438668919 1Panel-mysql-JhRU | 2024-02-11T17:14:28.232447Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 438670384 1Panel-mysql-JhRU | 2024-02-11T17:14:28.232612Z 0 [Note] InnoDB: Database was not shutdown normally! 1Panel-mysql-JhRU | 2024-02-11T17:14:28.232633Z 0 [Note] InnoDB: Starting crash recovery. 1Panel-mysql-JhRU | 2024-02-11T17:14:28.238674Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... 1Panel-mysql-JhRU | InnoDB: Progress in percent: 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 17:14:28 UTC - mysqld got signal 11 ; 1Panel-mysql-JhRU | This could be because you hit a bug. It is also possible that this binary 1Panel-mysql-JhRU | or one of the libraries it was linked against is corrupt, improperly built, 1Panel-mysql-JhRU | or misconfigured. This error can also be caused by malfunctioning hardware. 1Panel-mysql-JhRU | Attempting to collect some information that could help diagnose the problem. 1Panel-mysql-JhRU | As this is a crash and something is definitely wrong, the information 1Panel-mysql-JhRU | collection process might fail. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | 77 key_buffer_size=8388608 1Panel-mysql-JhRU | read_buffer_size=131072 1Panel-mysql-JhRU | max_used_connections=0 1Panel-mysql-JhRU | max_threads=151 1Panel-mysql-JhRU | thread_count=0 1Panel-mysql-JhRU | connection_count=0 1Panel-mysql-JhRU | It is possible that mysqld could use up to 1Panel-mysql-JhRU | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory 1Panel-mysql-JhRU | Hope that's ok; if not, decrease some variables in the equation. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | Thread pointer: 0x0 1Panel-mysql-JhRU | Attempting backtrace. You can use the following information to find out 1Panel-mysql-JhRU | where mysqld died. If you see no messages after this, something went 1Panel-mysql-JhRU | terribly wrong... 1Panel-mysql-JhRU | 78 79 80 81 stack_bottom = 0 thread_stack 0x40000 1Panel-mysql-JhRU | 82 83 84 85 86 87 88 89 90 91 92 93 94 mysqld(my_print_stacktrace+0x3b)[0xf11c0b] 1Panel-mysql-JhRU | 95 96 97 98 99 2024-02-11 12:14:36-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | 2024-02-11 12:14:36-05:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 1Panel-mysql-JhRU | 2024-02-11 12:14:36-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' 1Panel-mysql-JhRU | 2024-02-11T17:14:36.647210Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ... 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651653Z 0 [Note] InnoDB: PUNCH HOLE support available 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651674Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651677Z 0 [Note] InnoDB: Uses event mutexes 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651681Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651684Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651686Z 0 [Note] InnoDB: Using Linux native AIO 1Panel-mysql-JhRU | 2024-02-11T17:14:36.651905Z 0 [Note] InnoDB: Number of pools: 1 1Panel-mysql-JhRU | 2024-02-11T17:14:36.652104Z 0 [Note] InnoDB: Using CPU crc32 instructions 1Panel-mysql-JhRU | 2024-02-11T17:14:36.654459Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 1Panel-mysql-JhRU | 2024-02-11T17:14:36.661231Z 0 [Note] InnoDB: Completed initialization of buffer pool 1Panel-mysql-JhRU | 2024-02-11T17:14:36.665014Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 1Panel-mysql-JhRU | 2024-02-11T17:14:36.676985Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 1Panel-mysql-JhRU | 2024-02-11T17:14:36.678585Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438668919 1Panel-mysql-JhRU | 2024-02-11T17:14:36.678695Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 438670384 1Panel-mysql-JhRU | 2024-02-11T17:14:36.678943Z 0 [Note] InnoDB: Database was not shutdown normally! 1Panel-mysql-JhRU | 2024-02-11T17:14:36.678952Z 0 [Note] InnoDB: Starting crash recovery. 1Panel-mysql-JhRU | 2024-02-11T17:14:36.686107Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... 1Panel-mysql-JhRU | InnoDB: Progress in percent: 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 17:14:36 UTC - mysqld got signal 11 ; 1Panel-mysql-JhRU | 2024-02-11 12:14:51-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | 2024-02-11 12:14:51-05:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 1Panel-mysql-JhRU | 2024-02-11 12:14:51-05:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started. 1Panel-mysql-JhRU | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' 1Panel-mysql-JhRU | 2024-02-11T17:14:51.804341Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ... 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809304Z 0 [Note] InnoDB: PUNCH HOLE support available 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809362Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809366Z 0 [Note] InnoDB: Uses event mutexes 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809368Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809372Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809378Z 0 [Note] InnoDB: Using Linux native AIO 1Panel-mysql-JhRU | 2024-02-11T17:14:51.809659Z 0 [Note] InnoDB: Number of pools: 1 1Panel-mysql-JhRU | 2024-02-11T17:14:51.810056Z 0 [Note] InnoDB: Using CPU crc32 instructions 1Panel-mysql-JhRU | 2024-02-11T17:14:51.812444Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 1Panel-mysql-JhRU | 2024-02-11T17:14:51.822108Z 0 [Note] InnoDB: Completed initialization of buffer pool 1Panel-mysql-JhRU | 2024-02-11T17:14:51.828811Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 1Panel-mysql-JhRU | 2024-02-11T17:14:51.841741Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 1Panel-mysql-JhRU | 2024-02-11T17:14:51.843618Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 438668919 1Panel-mysql-JhRU | 2024-02-11T17:14:51.843684Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 438670384 1Panel-mysql-JhRU | 2024-02-11T17:14:51.843966Z 0 [Note] InnoDB: Database was not shutdown normally! 1Panel-mysql-JhRU | 2024-02-11T17:14:51.844064Z 0 [Note] InnoDB: Starting crash recovery. 1Panel-mysql-JhRU | 2024-02-11T17:14:51.850392Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... 1Panel-mysql-JhRU | InnoDB: Progress in percent: 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 17:14:51 UTC - mysqld got signal 11 ; 1Panel-mysql-JhRU | This could be because you hit a bug. It is also possible that this binary 1Panel-mysql-JhRU | or one of the libraries it was linked against is corrupt, improperly built, 1Panel-mysql-JhRU | or misconfigured. This error can also be caused by malfunctioning hardware. 1Panel-mysql-JhRU | Attempting to collect some information that could help diagnose the problem. 1Panel-mysql-JhRU | As this is a crash and something is definitely wrong, the information 1Panel-mysql-JhRU | collection process might fail. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | key_buffer_size=8388608 1Panel-mysql-JhRU | read_buffer_size=131072 1Panel-mysql-JhRU | max_used_connections=0 1Panel-mysql-JhRU | max_threads=151 1Panel-mysql-JhRU | thread_count=0 1Panel-mysql-JhRU | connection_count=0 1Panel-mysql-JhRU | It is possible that mysqld could use up to 1Panel-mysql-JhRU | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory 1Panel-mysql-JhRU | Hope that's ok; if not, decrease some variables in the equation. 1Panel-mysql-JhRU | 1Panel-mysql-JhRU | Thread pointer: 0x0 1Panel-mysql-JhRU | Attempting backtrace. You can use the following information to find out 1Panel-mysql-JhRU | where mysqld died. If you see no messages after this, something went 1Panel-mysql-JhRU | terribly wrong...
重现步骤
手动备份的快照恢复失败
期待的正确结果
No response
相关日志输出
No response
附加信息
No response
可以进入 容器 页面，查看一下 MySQL 容器全部日志是否有 ERROR 相关信息。
也可以参考一下官方这篇文章： https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
进入应用商店页面，再次全新安装相同版本 MySQL 应用，观察是否存在相同问题。
你可以将之前的 MySQL 数据库表备份出来导入新库，确认一下是不是数据库的问题。
本地尝试恢复带有数据的 MySQL 应用也未能复现问题。