标题: 宝塔面板MYSQL5.6.50无法启动，帮忙看一下日志 [打印本页] 作者: Jack 时间: 2023-1-23 23:49 标题: 宝塔面板MYSQL5.6.50无法启动，帮忙看一下日志 2023-01-23 07:34:22 3087 [Note] Plugin 'FEDERATED' is disabled.
2023-01-23 07:34:22 14814edab740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2023-01-23 07:34:22 3087 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-01-23 07:34:22 3087 [Note] InnoDB: The InnoDB memory heap is disabled
2023-01-23 07:34:22 3087 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-01-23 07:34:22 3087 [Note] InnoDB: Memory barrier is not used
2023-01-23 07:34:22 3087 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-01-23 07:34:22 3087 [Note] InnoDB: Using CPU crc32 instructions
2023-01-23 07:34:22 3087 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2023-01-23 07:34:22 3087 [Note] InnoDB: Completed initialization of buffer pool
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
2023-01-23 07:34:22 14814edab740 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 2ddc5be300000005000000000000000000000013df9030b700070000000000000000000000000000000042505f00000000000000000200f20000000000000006000000000000002d00f902cae; asc mysql-bin.000323 _ @ _ @ jPs
> , ;
InnoDB: End of page dump
2023-01-23 07:34:22 14814edab740 InnoDB: uncompressed page, stored checksum in field1 769416163, calculated checksums for field1: crc32 4022788669, innodb 1561684456, none 3735928559, stored checksum in field2 1053557639, calculated checksums for field2: crc32 4022788669, innodb 996869806, none 3735928559, page LSN 19 3750768823, low 4 bytes of LSN at page end 3750767790, page number (if stored to page already) 5, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a transaction system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
2023-01-23 07:34:22 14814edab740 InnoDB: Assertion failure in thread 22545606293312 in file buf0buf.cc line 4303
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:34:22 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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=500
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 = 206582 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
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0x556ee4799a9c]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x378)[0x556ee4517518]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x14814f660730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x14814ede77bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x14814edd2535]
/www/server/mysql/bin/mysqld(+0x3968fa)[0x556ee442e8fa]
/www/server/mysql/bin/mysqld(+0x84e958)[0x556ee48e6958]
/www/server/mysql/bin/mysqld(+0x837b1e)[0x556ee48cfb1e]
/www/server/mysql/bin/mysqld(+0x7fb6e4)[0x556ee48936e4]
/www/server/mysql/bin/mysqld(+0x7e9b05)[0x556ee4881b05]
/www/server/mysql/bin/mysqld(+0x7333a4)[0x556ee47cb3a4]
/www/server/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4c)[0x556ee445c77c]
/www/server/mysql/bin/mysqld(+0x50a74b)[0x556ee45a274b]
/www/server/mysql/bin/mysqld(_Z11plugin_initPiPPci+0xa8b)[0x556ee45a76cb]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x89f)[0x556ee4455daf]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x14814edd409b]
/www/server/mysql/bin/mysqld(_start+0x2a)[0x556ee4449e5a]
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.作者: toot 时间: 2023-1-23 23:53
哪里的机子作者: Jack 时间: 2023-1-23 23:56