3860 b0fe0 0c32 8022 80002022-06-19T00:31:15.668786+08:00 51 [Note] InnoDB: Uncompressed page, stored checksum in field1 2608893470, calculated checksums for field1: crc32 2222807756/33661786, innodb 2654183753, none 3735928559, stored checksum in field2 2608893470, calculated checksums for field2: crc32 2222807756/33661786, innodb 3118498483, none 3735928559, page LSN 491 1797757467, low 4 bytes of LSN at page end 1797757467, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 00006fInnoDB: Page may be a freshly allocated page k0b8d92022-06-19T00:31:15.668833+08:00 51 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. fb 8000:D8be3 61c3 0f2022-06-19T00:31:15.668900+08:00 51 [ERROR] [FATAL] InnoDB: Unable to read page [page id: space=1426, page number=857195] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see http://dev.mysql.com/doc/rejydban/5.7/en/ for more details. Aborting... ca38 t2022-06-19 00:31:15 0x7f1fae5ef700 InnoDB: Assertion failure in thread 139774046172928 in file ut0ut.cc line 916 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/rejydban/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. c3df16:31:15 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. key_buffer_size=134217728 oread_buffer_size=4194304 Umax_used_connections=94 max_threads=3000 thread_count=94 connection_count=93 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 24747103 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f1ea0000ae0 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... d28fb e800m }1a0bf044>b4600xg0463S 3b80 2280 008b e367gstack_bottom = 7f1fae5eeea8 thread_stack 0x40000 606f H99da de00 b040f 2f06d b2e262e04a80 [006f 0b0b f050 398bm e361 7162g 40db 1900000ff80d e1000000 00000002nJa3e2 ~62e0c20be373 0ce9 9207 4f00 001c 4000 3800 w0000 0000 0062 Vf000LM0000 008b^ e315 6a00 A00ba ;ab80 0010 088b "eae8/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(my_print_stacktrace+0x35)[0xf1dff5] w1e00 000c486f 2900 0000 H008bbbe373 n96e2m 625br cd00047d b8627861b2 8000 0000 e4fbK/f44a 0004 87b3 84eb Se262bb5c09 0000 1de3m 801abb/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(handle_fatal_signal+0x4a4)[0x79d3b4] 8000/lib64/libpthread.so.0(+0xf6d0)[0x7f2392ea86d0] 0000 E6da8 /lib64/libc.so.6(gsignal+0x37)[0x7f2391a9d277] 0d69 /lib64/libc.so.6(abort+0x148)[0x7f2391a9e968] 622ab<8000bb8be3 0174 "1d9b 5c460c 58100280 1a80ow 0000m 000d fbef 0b80 b0000 00e6 4bf2, 3580 c1dc 8100 "009b d88bowa580 000c600022ef0b8000 0000 8618j 1631bb6262 5cbdbb6dac 7252 e306 0000 0000G 8bf0o/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld[0x1159d65] w f87c 8000" 0c68 vY8bc1bb1c1e 16262 5cf9 0dfb 9038 001abb8000 6da8 w6262 8c9f 0000 0000 0013n 02bc 6266 5145 0022 9040 001a 8000 0dfbow8000 6f0b80006da8e9814381bbe262` 5d71 8bf0bbbe6ciF001a`$8c78 0022 80/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_ZN2ib5fatalD1Ev+0xb3)[0x115e8b3] 006f "0b80 000d fb0bowe3ad 7f62 6230 0562 K66f4 d480 M1a80 008b f0b9c06f0b8c8000220be3b35b6262501280001058001aeda86262e4fcef0b80008bf04e6fb9046eea5e0780001060001a8dfb800000006f0beda862626e973f1f6262d591d13c106c/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0xf16)[0x119f176] 0c8a8022800000006f0b8dfb80008be3c4fb0fca3cffe5ee9070001a0bf0dcc300006393802280008be3caba6f99ded9000010786db2e262e66280006f0b0bf0e90a8be3dc186240df15000010800de100000000000002a3e262e6db0be3d6aae992abe200001c200038000000/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld[0x1187140] 00000062f0000000008be3b1f10000b8de800410908beb807500040cb06f29000000008be3efdee2625fc900007d30627867ca80000000e4fa8c2e0000875be7d5e262600600001d5b801a800000006da80d69684280008be36607 7a4160k 410cc0108a80 1a800000000dfbbwef0b800000 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_ZN11ha_innopart16records_in_rangeEjP12st_key_rangeS1_+0x4ce)[0x1009a5e] " 00e64b91 f68ad8e0 7e0004 o9b4124 c498000 0cc800 22ef0b m800000 008618b 79c862 6260b9 o6da872w dae928 w000000 008bf1 5f1680 b040cd0@d8bc17f 9b626260 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_ZN7handler27multi_range_read_info_constEjP15st_range_seq_ifPvjPjS3_P13Cost_estimate+0xa2)[0x7e3bf2] f60dfb90 c0001a 80006da8 626286a1 000000000015 397c6262 6de9b 002290c8z 001a g8000f 0dfb80006f0b 8000 6da88 e986 e15b e262 b616e 8bf5 5709 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_ZN10DsMrr_impl16dsmrr_info_constEjP15st_range_seq_ifPvjPjS3_P13Cost_estimate+0x53)[0x7eba13] 001a 8ce0 0022 8000 6f0b 8000 0dfb 0be4 1135 6262 o0c01U 6262 fa42 801a 8000 8bf1b 53eb 6f0b |8ce8 b0022xm0be4j 16e3 62626c1f80 0010 e000. 1aed a862 62eb 12efb 0b80 008b f1eb c21c ca6e 9262 m0280 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld[0xe3c702] 0010 me800 1a8d fb80 `0000 006fg 0bed{ a862, 6260 6ea2 b862 62e9 ad6b eb10w f00c e280V 2280 0000006f0b8d8ffb80 008b e428 c20f 0 " ca00w faec 0290 f8001a0bf1 77ffZb0000b 620bgm8022 s8000" 8be4 2ecf 6f99 e2d4 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld[0xe40207] 0000 1100 6db28 e262 ec7a.b8000b 6f0b 0bf1 83f2H 8be4 380c m6240 be310b 0000= 1108 0de1 0000 0000 b0000b 02a3 e262& ecf2P 0be4 3ad4 e993 ecb2 o0000w 1c00 m0038 0000 0000 0000b 62f0 n 0000 H0000 " /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z17test_quick_selectP3THD6BitmapILj64EEyybN8st_order10enum_orderEPK16QEP_shared_ownerP4ItemPS2_PP14QUICK_SELECT_I+0xc5e)[0xe4ac9e] ow 28be41bb 2d02 b0000b 8ee2Z 8000 o1118s 8bebP " =1c2a b0000b 0d18E 6f29 0000h 0000 b8be4b 4b3c e262w 63c4 0000 d7c88 I6278 o6de2: 8000 0000 e4fap 280e 0000 ow bbz86c4 b4c99ba_ e262 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z12mysql_updateP3THDR4ListI4ItemES4_y15enum_duplicatesPyS6_+0xa6d)[0xd77e3d] x6400 z0000 "1cd3 801a ow8000 0000 6da8 0d69b*6e5a 8000 D8be4 d97a d676 643c 0d2c 1112b 801a "8000 0000 0dfbn ef0bo 8000k 0000 e64c 3af0m 8cb0 be4780000 9ac9 owbfc2 8004 0d30 0022t /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_ZN14Sql_cmd_update23try_single_table_updateEP3THDPb+0x198)[0xd793a8] ef0bb@8000l 0000 861f de1a 6262 64b3 6da8 7322 bef50 0000 0000 8bf1 a4f5 <8000 0d38 8bc6 8e405 6262 64ef 0dfbb 9148 001a 8000 6da8 G6262 80c9 0000 00000015b1fc 6262 686b 0026 9150 /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_ZN14Sql_cmd_update7executeEP3THD+0x2c)[0xd7a37c] oU 001a 8000b 0dfb~ 8000 | b6f0bxs8000 6da8 e986 9fe3 e262 6567 y 8bf1; f2abb 001a8d48 0022 K 8000 m 6f0b s8000 0dfb 0be4 =75ba ! j 6262 080b 6262 e1d2 801a w8000 8b/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z21mysql_execute_commandP3THDb+0xd99)[0xcf34e9] f1ef e86f W0f8d 5000 220bn 2e47bP 6c62 6268 2480 " w0011 6800 1aed a862M 62f1bb2aef ^0b80m 008bs f170 4d81 916f 3a66 39804 0411 7000 1a8d fb80Z 0000bb 006f 0bed a862 627am 4607b/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3a5)[0xcf7a15] b 7a62 62ed a507 bc11 780d b7a80b 2280 0000" 006f o0b8dw fb80 m008b e48d 300f ca04b f1f2 1a91 bI 8000 1a0b" f213 od900w 0062 6380 2280008be4 92b8 b6f99b e6cf b0000b 1188 6db2 e262/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x116d)[0xcf8bed] f292 8000 o6f0bw 0bf2 1fc1" 8be0 95a5 b6240b e70bM 0004 b1190b 0de1 0000w 0000 0000 02a3 oe262 f30a 0be4 9ee9 e990 4c87 0000 o1ce0w 0038 bb|0000 0000 b0000by62f0T 0000 0000/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(_Z10do_commandP3THD+0x194)[0xcf96e4] 8be4" c937 0000 o9401w 8000 11a0 8be8 - b7c5| 0000 0d80 6f29 000000008be4a747e2 b6267 bf00" 007c 90062 o s 7873 fa80 m0000 00e4b f9c32 d300 o0086w 6cb0 f9e2 6267 Hfb00vb041c@t 4b/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(handle_connection+0x29c)[0xdc5a0c] 801a 8000 0000 6da8 0d69b 7472 8000 Q8be4 3d86 O2d9d 6833 0d908 119a 801a b8000 0000 0dfb ef0b 08000Q 0000 e64c( ded8 G9688 e874 o0000U 9a32 5be8 8000 d0d98 0022b ef0bv 8000 0000 b861fxy42/usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld(pfs_spawn_thread+0x174)[0xf7a804] 6e62/lib64/libpthread.so.0(+0x7e25)[0x7f2392ea0e25] 6268 af6d /lib64/libc.so.6(clone+0x6d)[0x7f2391b65bad] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f1ea00054d0): S a873 is an invalid pointer aaConnection ID (thread ID): 51 f5Status: NOT_KILLED 78The 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. 0000u 00008bf208d780000da08bc6480e626268ed0dff91d0001a80006da862629ad1000000000016be376262648f002291d8001a80000dfb80006f0b80006da8e98625b7e26269638bf26e35001e8db0002280006f0b80000dfb0be4d9b2622022-06-18T16:31:17.123242Z mysqld_safe Number of processes running now: 0 2022-06-18T16:31:17.128208Z mysqld_safe mysqld restarted 2022-06-19T00:31:17.369506+08:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2022-06-19T00:31:17.369613+08:00 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 2022-06-19T00:31:17.369646+08:00 0 [Note] /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld (mysqld 5.7.16-log) starting as process 12749 ... 2022-06-19T00:31:17.373898+08:00 0 [Warning] You need to use --log-bin to make --log-slave-updates work. 2022-06-19T00:31:17.373969+08:00 0 [Warning] You need to use --log-bin to make --binlog-format work. 2022-06-19T00:31:17.391323+08:00 0 [Note] InnoDB: PUNCH HOLE support not available 2022-06-19T00:31:17.391350+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-06-19T00:31:17.391355+08:00 0 [Note] InnoDB: Uses event mutexes 2022-06-19T00:31:17.391360+08:00 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier 2022-06-19T00:31:17.391365+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2022-06-19T00:31:17.391369+08:00 0 [Note] InnoDB: Using Linux native AIO 2022-06-19T00:31:17.393288+08:00 0 [Note] InnoDB: Number of pools: 1 2022-06-19T00:31:17.393425+08:00 0 [Note] InnoDB: Using CPU crc32 instructions 2022-06-19T00:31:17.398922+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 14G, instances = 4, chunk size = 128M 2022-06-19T00:31:18.416152+08:00 0 [Note] InnoDB: Completed initialization of buffer pool 2022-06-19T00:31:18.652509+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2022-06-19T00:31:18.665052+08:00 0 [Note] InnoDB: Opened 3 undo tablespaces 2022-06-19T00:31:18.665079+08:00 0 [Note] InnoDB: 3 undo tablespaces made active 2022-06-19T00:31:18.665311+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda. 2022-06-19T00:31:18.855553+08:00 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 59502440283800 2022-06-19T00:31:19.042004+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502445526528 2022-06-19T00:31:19.196114+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502450769408 2022-06-19T00:31:19.373302+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502456012288 2022-06-19T00:31:19.656532+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502461255168 2022-06-19T00:31:19.855589+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502466498048 2022-06-19T00:31:20.025584+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502471740928 2022-06-19T00:31:20.206198+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502476983808 2022-06-19T00:31:20.388223+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502482226688 2022-06-19T00:31:20.538656+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502487469568 2022-06-19T00:31:20.692274+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502492712448 2022-06-19T00:31:20.856650+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502497955328 2022-06-19T00:31:21.153652+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502503198208 2022-06-19T00:31:21.294624+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502508441088 2022-06-19T00:31:21.491243+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502513683968 2022-06-19T00:31:21.650566+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502518926848 2022-06-19T00:31:21.820194+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502524169728 2022-06-19T00:31:21.994892+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502529412608 2022-06-19T00:31:22.158918+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502534655488 2022-06-19T00:31:22.337704+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502539898368 2022-06-19T00:31:22.513756+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502545141248 2022-06-19T00:31:22.662858+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502550384128 2022-06-19T00:31:22.828893+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502555627008 2022-06-19T00:31:23.018735+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502560869888 2022-06-19T00:31:23.189029+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502566112768 2022-06-19T00:31:23.351925+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502571355648 2022-06-19T00:31:23.519988+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502576598528 2022-06-19T00:31:23.687924+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502581841408 2022-06-19T00:31:23.870997+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502587084288 2022-06-19T00:31:24.058935+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502592327168 2022-06-19T00:31:24.222232+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502597570048 2022-06-19T00:31:24.386927+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502602812928 2022-06-19T00:31:24.567410+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502608055808 2022-06-19T00:31:24.747404+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502613298688 2022-06-19T00:31:24.932890+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502618541568 2022-06-19T00:31:25.121151+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502623784448 2022-06-19T00:31:25.285641+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502629027328 2022-06-19T00:31:25.456117+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502634270208 2022-06-19T00:31:25.639036+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502639513088 2022-06-19T00:31:25.784414+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502644755968 2022-06-19T00:31:25.956741+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502649998848 2022-06-19T00:31:26.160790+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502655241728 2022-06-19T00:31:26.347175+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502660484608 2022-06-19T00:31:26.539516+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502665727488 2022-06-19T00:31:26.703234+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502670970368 2022-06-19T00:31:26.901281+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502676213248 2022-06-19T00:31:27.063909+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502681456128 2022-06-19T00:31:27.236646+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502686699008 2022-06-19T00:31:27.422288+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502691941888 2022-06-19T00:31:27.597563+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502697184768 2022-06-19T00:31:27.786716+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502702427648 2022-06-19T00:31:27.969233+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502707670528 2022-06-19T00:31:28.149212+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502712913408 2022-06-19T00:31:28.324997+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502718156288 2022-06-19T00:31:28.487460+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502723399168 2022-06-19T00:31:28.661262+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502728642048 2022-06-19T00:31:28.852834+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502733884928 2022-06-19T00:31:29.121974+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502739127808 2022-06-19T00:31:29.362026+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502744370688 2022-06-19T00:31:29.613181+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502749613568 2022-06-19T00:31:29.794955+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502754856448 2022-06-19T00:31:30.004993+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502760099328 2022-06-19T00:31:30.209047+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502765342208 2022-06-19T00:31:30.475471+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502770585088 2022-06-19T00:31:30.847279+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502775827968 2022-06-19T00:31:31.143248+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502781070848 2022-06-19T00:31:31.445699+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502786313728 2022-06-19T00:31:31.760356+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502791556608 2022-06-19T00:31:32.049798+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502796799488 2022-06-19T00:31:32.298426+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502802042368 2022-06-19T00:31:32.567337+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502807285248 2022-06-19T00:31:32.881040+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502812528128 2022-06-19T00:31:33.197816+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502817771008 2022-06-19T00:31:33.477037+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502823013888 2022-06-19T00:31:33.778889+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502828256768 2022-06-19T00:31:34.130930+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502833499648 2022-06-19T00:31:34.392101+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502838742528 2022-06-19T00:31:34.705998+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502843985408 2022-06-19T00:31:35.050673+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502849228288 2022-06-19T00:31:35.346571+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502854471168 2022-06-19T00:31:35.601703+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502859714048 2022-06-19T00:31:35.878119+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502864956928 2022-06-19T00:31:36.115244+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502870199808 2022-06-19T00:31:36.344180+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502875442688 2022-06-19T00:31:36.652963+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502880685568 2022-06-19T00:31:36.923037+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502885928448 2022-06-19T00:31:37.172677+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502891171328 2022-06-19T00:31:37.609248+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502444019200 2022-06-19T00:31:37.786834+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502449262080 2022-06-19T00:31:37.982839+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502454504960 2022-06-19T00:31:38.259279+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502459747840 2022-06-19T00:31:38.526994+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502464990720 2022-06-19T00:31:38.723038+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502470233600 2022-06-19T00:31:38.918402+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502475476480 2022-06-19T00:31:39.123557+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502480719360 2022-06-19T00:31:39.284323+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502485962240 2022-06-19T00:31:39.471958+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502491205120 2022-06-19T00:31:39.640005+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502496448000 2022-06-19T00:31:39.974076+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502501690880 2022-06-19T00:31:40.149507+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502506933760 2022-06-19T00:31:40.349301+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502512176640 2022-06-19T00:31:40.524878+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502517419520 2022-06-19T00:31:40.713978+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502522662400 2022-06-19T00:31:40.907440+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502527905280 2022-06-19T00:31:41.093570+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502533148160 2022-06-19T00:31:41.299002+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502538391040 2022-06-19T00:31:41.487191+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502543633920 2022-06-19T00:31:41.670421+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502548876800 2022-06-19T00:31:42.024556+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502554119680 2022-06-19T00:31:42.379986+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502559362560 2022-06-19T00:31:42.587063+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502564605440 2022-06-19T00:31:42.772910+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502569848320 2022-06-19T00:31:42.976582+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502575091200 2022-06-19T00:31:43.149458+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502580334080 2022-06-19T00:31:43.351649+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502585576960 2022-06-19T00:31:43.549791+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502590819840 2022-06-19T00:31:43.736121+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502596062720 2022-06-19T00:31:43.917194+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502601305600 2022-06-19T00:31:44.142220+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502606548480 2022-06-19T00:31:44.321642+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502611791360 2022-06-19T00:31:44.532087+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502617034240 2022-06-19T00:31:44.715824+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502622277120 2022-06-19T00:31:44.918813+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502627520000 2022-06-19T00:31:45.107025+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502632762880 2022-06-19T00:31:45.297642+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502638005760 2022-06-19T00:31:45.477494+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502643248640 2022-06-19T00:31:45.652341+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502648491520 2022-06-19T00:31:45.861663+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502653734400 2022-06-19T00:31:46.049313+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502658977280 2022-06-19T00:31:46.248415+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502664220160 2022-06-19T00:31:46.440344+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502669463040 2022-06-19T00:31:46.649708+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502674705920 2022-06-19T00:31:46.818153+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502679948800 2022-06-19T00:31:47.016414+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502685191680 2022-06-19T00:31:47.227999+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502690434560 2022-06-19T00:31:47.442449+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502695677440 2022-06-19T00:31:47.652025+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502700920320 2022-06-19T00:31:47.865890+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502706163200 2022-06-19T00:31:48.069198+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502711406080 2022-06-19T00:31:48.274354+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502716648960 2022-06-19T00:31:48.475761+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502721891840 2022-06-19T00:31:48.669768+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502727134720 2022-06-19T00:31:48.863067+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502732377600 2022-06-19T00:31:49.140602+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502737620480 2022-06-19T00:31:49.401505+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502742863360 2022-06-19T00:31:49.666094+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502748106240 2022-06-19T00:31:49.873580+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502753349120 2022-06-19T00:31:50.068069+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502758592000 2022-06-19T00:31:50.299367+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502763834880 2022-06-19T00:31:50.568505+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502769077760 2022-06-19T00:31:50.946656+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502774320640 2022-06-19T00:31:51.269216+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502779563520 2022-06-19T00:31:51.574943+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502784806400 2022-06-19T00:31:51.900602+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502790049280 2022-06-19T00:31:52.219623+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502795292160 2022-06-19T00:31:52.490987+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502800535040 2022-06-19T00:31:52.757708+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502805777920 2022-06-19T00:31:53.100821+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502811020800 2022-06-19T00:31:53.446072+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502816263680 2022-06-19T00:31:53.740145+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502821506560 2022-06-19T00:31:54.059909+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502826749440 2022-06-19T00:31:54.391192+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502831992320 2022-06-19T00:31:54.685939+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502837235200 2022-06-19T00:31:54.965661+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502842478080 2022-06-19T00:31:55.346911+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502847720960 2022-06-19T00:31:55.653932+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502852963840 2022-06-19T00:31:55.917634+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502858206720 2022-06-19T00:31:56.221497+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502863449600 2022-06-19T00:31:56.472465+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502868692480 2022-06-19T00:31:56.724878+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502873935360 2022-06-19T00:31:57.032934+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502879178240 2022-06-19T00:31:57.336655+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502884421120 2022-06-19T00:31:57.596609+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502889664000 2022-06-19T00:31:57.874750+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 59502894147904 2022-06-19T00:31:57.876555+08:00 0 [Note] InnoDB: Database was not shutdown normally! 2022-06-19T00:31:57.876562+08:00 0 [Note] InnoDB: Starting crash recovery. 2022-06-19T00:31:59.052834+08:00 0 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 0 1 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 2022-06-19T00:32:09.043294+08:00 0 [Note] InnoDB: Apply batch completed 2022-06-19T00:32:09.043348+08:00 0 [Note] InnoDB: Last MySQL binlog file position 0 344446779, file name jydb_bin.003133 2022-06-19T00:32:09.396932+08:00 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2022-06-19T00:32:09.396993+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-06-19T00:32:09.397115+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-06-19T00:32:09.440260+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-06-19T00:32:09.442331+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2022-06-19T00:32:09.442369+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2022-06-19T00:32:09.442832+08:00 0 [Note] InnoDB: Waiting for purge to start 2022-06-19T00:32:09.493133+08:00 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 50841ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.) 2022-06-19T00:32:09.493274+08:00 0 [Note] InnoDB: 5.7.16 started; log sequence number 59502894147904 2022-06-19T00:32:09.493644+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /database/jydb/data/ib_buffer_pool 2022-06-19T00:32:09.525216+08:00 0 [Note] Semi-sync replication initialized for transactions. 2022-06-19T00:32:09.525258+08:00 0 [Note] Semi-sync replication enabled on the master. 2022-06-19T00:32:09.525373+08:00 0 [Note] Starting ack receiver thread 2022-06-19T00:32:09.560823+08:00 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 2022-06-19T00:32:09.560885+08:00 0 [Note] Server hostname (bind-address): '*'; port: 3306 2022-06-19T00:32:09.560978+08:00 0 [Note] IPv6 is available. 2022-06-19T00:32:09.561004+08:00 0 [Note] - '::' resolves to '::'; 2022-06-19T00:32:09.561062+08:00 0 [Note] Server socket created on IP: '::'. 2022-06-19T00:32:09.597858+08:00 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode. 2022-06-19T00:32:09.599447+08:00 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode. 2022-06-19T00:32:09.633214+08:00 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode. 2022-06-19T00:32:09.660165+08:00 0 [Note] Event Scheduler: Loaded 0 events 2022-06-19T00:32:09.660380+08:00 1 [Note] Event Scheduler: scheduler thread started with id 1 2022-06-19T00:32:09.660520+08:00 0 [Note] /usr/local/mysql-5.7.16-linux-glibc2.5-x86_64/bin/mysqld: ready for connections. Version: '5.7.16-log' socket: '/tmp/mysql_jydb.sock' port: 3306 MySQL Community Server (GPL) 2022-06-19T00:33:32.254461+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.254663+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.254685+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex c66dffe000000050000475eb000017f400000002db586b47000000000000000000000000000000ec01bc03be0000003800000000000003b2000000000002dc310000000000000000001c0000000000000000000000000000000000000000000000000800000000000000000200000000000000000000000000000000000000000000000062830000000089637e350000001480000018897991cc000000186f55000000008bd8e46ee261e3b600006d866278a81380000000e4a9281a00008bf8f327e261e42e00000dd3801a800000006da60d15a88b80008bd87761d139e4a6002c0012801a800000000dfbef7780000000e67f645e4b62651e00008be6be23800400300022ef778000000086228fa26261e5966da662222961000000008bdea652800000388bfb99196261e60e0dfb8048001a80006da662624684000000000007f6866261e6c600268050001a80000............ ................... InnoDB: End of page dump 2022-06-19T00:33:32.338027+08:00 45 [Note] InnoDB: Uncompressed page, stored checksum in field1 3329097696, calculated checksums for field1: crc32 3650104114/884774814, innodb 1809404915, none 3735928559, stored checksum in field2 3329097696, calculated checksums for field2: crc32 3650104114/884774814, innodb 992001978, none 3735928559, page LSN 2 3680004935, low 4 bytes of LSN at page end 3680004935, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2022-06-19T00:33:32.338051+08:00 45 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2022-06-19T00:33:32.338424+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.338479+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.338484+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex c66dffe000000050000475eb000017f400000002db586b47000000000000000000000000000000ec01bc03be0000003800000000000003b2000000000002dc310000000000000000001c0000000000000000000000000000000000000000000000000800000000000000000200000000000000000000000000000000000000000000000062830000000089637e350000001480000018897991cc000000186f55000000008bd8e46ee261e3b600006d866278a81380000000e4a9281a00008bf8f327e261e42e00000dd3801a800000006da60d15a88b80008bd87761d139e4a6002c0012801a800000000dfbef7780000000e67f645e4b62651e00008be6be23800400300022ef778000000086228fa26261e5966da662222961000000008bdea652800000388bfb99196261e60e0dfb8048001a80006da662624684000000000007f6866261e6c600268050001a80000dfb80006f7780006da6e9bb062be261e6fe8bdedeb8001a8048002280006f7780000dfb0bd935c162618ad062622a83801a80008bdeea0f6f73805000220bd93f346261ea1580000068001aeda662622b5bef7780008bde7f0148cf6239e8448............. .................... InnoDB: End of page dump 2022-06-19T00:33:32.412341+08:00 45 [Note] InnoDB: Uncompressed page, stored checksum in field1 3329097696, calculated checksums for field1: crc32 3650104114/884774814, innodb 1809404915, none 3735928559, stored checksum in field2 3329097696, calculated checksums for field2: crc32 3650104114/884774814, innodb 992001978, none 3735928559, page LSN 2 3680004935, low 4 bytes of LSN at page end 3680004935, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2022-06-19T00:33:32.412356+08:00 45 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2022-06-19T00:33:32.412637+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.412690+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.412695+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex c66dffe000000050000475eb000017f400000002db586b47000.... ............... ........................... InnoDB: End of page dump 2022-06-19T00:33:32.486815+08:00 45 [Note] InnoDB: Uncompressed page, stored checksum in field1 3329097696, calculated checksums for field1: crc32 3650104114/884774814, innodb 1809404915, none 3735928559, stored checksum in field2 3329097696, calculated checksums for field2: crc32 3650104114/884774814, innodb 992001978, none 3735928559, page LSN 2 3680004935, low 4 bytes of LSN at page end 3680004935, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2022-06-19T00:33:32.486829+08:00 45 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2022-06-19T00:33:32.487139+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.487203+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.487209+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex c66dffe000000050000475eb000017f400000002db586b478bdcd28ae262138700046ef66278cca380000000e49583f80004894ce9c7e26213ff00000ea3801a800000006da60d15cd1a80008bdc7fd56d85147702980342801a800000000dfbef7780000000e67a9cf82ff094ef0000888a1beb800002a00022ef77...... ..... ................... InnoDB: End of page dump 2022-06-19T00:33:32.564064+08:00 45 [Note] InnoDB: Uncompressed page, stored checksum in field1 3329097696, calculated checksums for field1: crc32 3650104114/884774814, innodb 1809404915, none 3735928559, stored checksum in field2 3329097696, calculated checksums for field2: crc32 3650104114/884774814, innodb 992001978, none 3735928559, page LSN 2 3680004935, low 4 bytes of LSN at page end 3680004935, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2022-06-19T00:33:32.564095+08:00 45 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2022-06-19T00:33:32.564963+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.565019+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.565025+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): InnoDB: End of page dump 2022-06-19T00:33:32.564064+08:00 45 [Note] InnoDB: Uncompressed page, stored checksum in field1 3329097696, calculated checksums for field1: crc32 3650104114/884774814, innodb 1809404915, none 3735928559, stored checksum in field2 3329097696, calculated checksums for field2: crc32 3650104114/884774814, innodb 992001978, none 3735928559, page LSN 2 3680004935, low 4 bytes of LSN at page end 3680004935, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2022-06-19T00:33:32.564095+08:00 45 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2022-06-19T00:33:32.564963+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.565019+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.565025+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): @ ...... InnoDB: End of page dump 2022-06-19T00:33:32.486815+08:00 45 [Note] InnoDB: Uncompressed page, stored checksum in field1 3329097696, calculated checksums for field1: crc32 3650104114/884774814, innodb 1809404915, none 3735928559, stored checksum in field2 3329097696, calculated checksums for field2: crc32 3650104114/884774814, innodb 992001978, none 3735928559, page LSN 2 3680004935, low 4 bytes of LSN at page end 3680004935, page number (if stored to page already) 80, space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 2022-06-19T00:33:32.486829+08:00 45 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/rejydban/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2022-06-19T00:33:32.487139+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.487203+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.487209+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes): @ ..... 2022-06-19T00:33:32.412637+08:00 45 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=80], should be [page id: space=1426, page number=857190] 2022-06-19T00:33:32.412690+08:00 45 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=1426, page number=857190]. You may have to recover from a backup. 2022-06-19T00:33:32.412695+08:00 45 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):