共计 5357 个字符，预计需要花费 14 分钟才能阅读完成。
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 pages2023-01-23 07:34:22 3087 [Note] InnoDB: The InnoDB memory heap is disabled2023-01-23 07:34:22 3087 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2023-01-23 07:34:22 3087 [Note] InnoDB: Memory barrier is not used2023-01-23 07:34:22 3087 [Note] InnoDB: Compressed tables use zlib 1.2.112023-01-23 07:34:22 3087 [Note] InnoDB: Using CPU crc32 instructions2023-01-23 07:34:22 3087 [Note] InnoDB: Initializing buffer pool, size = 16.0M2023-01-23 07:34:22 3087 [Note] InnoDB: Completed initialization of buffer poolInnoDB: Database page corruption on disk or a failedInnoDB: 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 dump2023-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) 0InnoDB: Page may be a transaction system pageInnoDB: Database page corruption on disk or a failedInnoDB: file read of page 5.InnoDB: You may have to recover from a backup.InnoDB: It is also possible that your operatingInnoDB: system has corrupted its own file cacheInnoDB: and rebooting your computer removes theInnoDB: error.InnoDB: If the corrupt page is an index pageInnoDB: you can also try to fix the corruptionInnoDB: by dumping, dropping, and reimportingInnoDB: the corrupt table. You can use CHECKInnoDB: TABLE to scan your table for corruption.InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.htmlInnoDB: 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 4303InnoDB: 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, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.htmlInnoDB: 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 binaryor 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 helpdiagnose the problem, but since we have already crashed,something is definitely wrong and this may fail.key_buffer_size=8388608read_buffer_size=131072max_used_connections=0max_threads=500thread_count=0connection_count=0It is possible that mysqld could use up tokey_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 206582 K bytes of memoryHope that\’s ok; if not, decrease some variables in the equation.Thread pointer: 0x0Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly 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 containsinformation that should help you find out what is causing the crash. toot 2023-01-23 23:53 2 哪里的机子 Jack 2023-01-23 23:56 3toot 发表于 2023-1-23 23:53 哪里的机子 Psychz dua 2023-01-24 02:26 4 數據庫表壞了~~~ 要你備份 數據庫在寫資料然後 機器有斷電或不正常重啟？先下指令備份出數據 在其他台機器先想辦法還原 hanweizhe 2023-01-24 02:39 5 估计机器问题 撒配置 突然断电没 TechBlack 2023-01-24 09:40 6 先备份目录，然后 MySQL 配置里面加 innodb_force_recovery=6，重启，然后把表备份出来，然后新建一个数据库，还原
