243纯70版本《自创内容群服端》绝无雷同

skybin2006

和上面的一样，数据库运行不了

skybin2006

2025-01-07T04:59:47.979017Z 0 [System] [MY-010116] [Server] F:\TBC\mysql-server\bin\mysqld.exe (mysqld 8.0.28) starting as process 8196
2025-01-07T04:59:48.007845Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-01-07T04:59:49.357509Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=60] log sequence number 7759955218 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.357939Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=59] log sequence number 7759955323 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.359186Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=58] log sequence number 7759950531 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.359552Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.359926Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=56] log sequence number 7759948207 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.360322Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.360640Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.361064Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.362568Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=433] log sequence number 7759955218 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.364007Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=288] log sequence number 7759955323 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.365079Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.365984Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.366250Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=300] log sequence number 7759950531 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.366483Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.366794Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=54] log sequence number 7759945201 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.367039Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.367382Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=55] log sequence number 7759946371 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.367738Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=386] log sequence number 7759945201 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.369217Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.369527Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=50] log sequence number 7759940532 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.369815Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.370114Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.370409Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=441] log sequence number 7759940532 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.370739Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.371044Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=445] log sequence number 7759946371 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.371319Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.385034Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=397] log sequence number 7759948207 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.385175Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.389126Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=48] log sequence number 7759938454 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.389221Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.389525Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=49] log sequence number 7759939509 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.389778Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.390079Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=47] log sequence number 7759937285 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.390316Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.396224Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=46] log sequence number 7759936367 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.396367Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.396779Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=259] log sequence number 7759938454 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.396997Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.397327Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=295] log sequence number 7759937285 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.397526Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.398972Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=438] log sequence number 7759936367 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.404677Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.405050Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=44] log sequence number 7759934880 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.405275Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.405573Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=158] log sequence number 7759935213 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.406015Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.406313Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=396] log sequence number 7759939509 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.406551Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.406835Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=43] log sequence number 7759934770 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.407075Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=41] log sequence number 7759934694 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.407358Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=42] log sequence number 7759934732 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.407648Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.407951Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=40] log sequence number 7759934656 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.408228Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.408542Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.408884Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.409202Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=334] log sequence number 7759934732 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.409451Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.409796Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=335] log sequence number 7759934770 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.410066Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=315] log sequence number 7759934694 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.410363Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.410652Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=39] log sequence number 7759934618 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.410977Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.411277Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=341] log sequence number 7759934656 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.411492Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.411817Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.412117Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=37] log sequence number 7759934542 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.412510Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=38] log sequence number 7759934580 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.412817Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=399] log sequence number 7759920976 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.413294Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=417] log sequence number 7759934618 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.413616Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.413909Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.415352Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.415697Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=340] log sequence number 7759934580 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.416043Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=147] log sequence number 7759920058 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.416390Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.416706Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.417118Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.417416Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=33] log sequence number 7759934450 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.417707Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.418072Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=228] log sequence number 7759934542 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.418417Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_002' Page [page id: space=4294967278, page number=345] log sequence number 7759934450 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.418693Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.418990Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.546029Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=60] log sequence number 7759952015 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.546151Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=61] log sequence number 7759955900 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.547502Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.547743Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.551591Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=59] log sequence number 7759951108 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.551720Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.552009Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=464] log sequence number 7759952015 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.552249Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.552516Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=284] log sequence number 7759955900 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.552779Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.553218Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=57] log sequence number 7759948784 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.553469Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.553734Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=298] log sequence number 7759951108 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.553949Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.554218Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=56] log sequence number 7759947630 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.554406Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.554665Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=382] log sequence number 7759948784 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.554926Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=54] log sequence number 7759944634 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.555158Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.555412Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.555600Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=474] log sequence number 7759947630 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.555875Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=55] log sequence number 7759945794 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.556116Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.556377Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.556657Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=317] log sequence number 7759944634 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.556902Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.558650Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=51] log sequence number 7759941157 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.558763Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=346] log sequence number 7759945794 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.559008Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.559249Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=50] log sequence number 7759940086 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.559466Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.559738Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=49] log sequence number 7759938900 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.560013Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.560258Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.560496Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=381] log sequence number 7759940086 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.560753Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.561050Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=283] log sequence number 7759938900 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.561316Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=159] log sequence number 7759936708 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.561547Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.561776Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.562062Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=48] log sequence number 7759937862 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.562491Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.562790Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=286] log sequence number 7759941157 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.563075Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.564987Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=46] log sequence number 7759935790 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.565111Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=45] log sequence number 7759934070 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.565362Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.565652Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=44] log sequence number 7759934032 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.565905Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=280] log sequence number 7759937862 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.566144Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.566402Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.566641Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=247] log sequence number 7759934070 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.566888Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.567165Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=43] log sequence number 7759933994 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.567404Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.567666Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=316] log sequence number 7759934032 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.567869Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=42] log sequence number 7759933940 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.568092Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.568350Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.568601Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=380] log sequence number 7759933994 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.568981Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.569036Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=139] log sequence number 7759933940 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.569101Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.569368Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.569636Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=41] log sequence number 7759933902 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.569853Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=40] log sequence number 7759933864 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.570070Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.570329Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.570573Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=383] log sequence number 7759935790 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.570816Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=39] log sequence number 7759933826 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.571032Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.571285Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.571507Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=138] log sequence number 7759933902 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.571872Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.572119Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=142] log sequence number 7759933826 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.572361Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.572614Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=302] log sequence number 7759933864 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.572872Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=38] log sequence number 7759933788 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.573106Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=149] log sequence number 7759921317 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.573313Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=36] log sequence number 7759933750 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.573557Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.573809Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.574031Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.574117Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.574365Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=271] log sequence number 7759933750 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.574572Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=301] log sequence number 7759933788 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.574812Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.575054Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=33] log sequence number 7759933674 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.575292Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.575531Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:49.576216Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'innodb_undo_001' Page [page id: space=4294967279, page number=141] log sequence number 7759933674 is in the future! Current system log sequence number 7759915625.
2025-01-07T04:59:49.576290Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html for information about forcing recovery.
2025-01-07T04:59:50.387964Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2025-01-07T04:59:51.025178Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2025-01-07T04:59:51.032719Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2025-01-07T04:59:51.093674Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: trx0purge.cc:175:purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no thread 3836
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/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
04:59:51 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x2269df91020
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...
2025-01-07T04:59:51.299429Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2025-01-07T04:59:51.299604Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-01-07T04:59:51.346856Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2025-01-07T04:59:51.347199Z 0 [System] [MY-010931] [Server] F:\TBC\mysql-server\bin\mysqld.exe: ready for connections. Version: '8.0.28'  socket: ''  port: 3310  MySQL Community Server - GPL.
7ff6c775fd48    mysqld.exe!my_print_stacktrace()[stacktrace.cc:429]
7ff6c699004b    mysqld.exe!print_fatal_signal()[signal_handler.cc:130]
7ff6c698fe13    mysqld.exe!my_server_abort()[signal_handler.cc:241]
7ff6c774643a    mysqld.exe!my_abort()[my_init.cc:263]
7ff6c797c579    mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:99]
7ff6c78dab28    mysqld.exe!TrxUndoRsegsIterator::set_next()[trx0purge.cc:175]
7ff6c78dbf7c    mysqld.exe!trx_purge_choose_next_log()[trx0purge.cc:1866]
7ff6c78dc6ef    mysqld.exe!trx_purge_get_next_rec()[trx0purge.cc:1968]
7ff6c78dba73    mysqld.exe!trx_purge_attach_undo_recs()[trx0purge.cc:2293]
7ff6c78db1a8    mysqld.exe!trx_purge()[trx0purge.cc:2424]
7ff6c78447d0    mysqld.exe!srv_do_purge()[srv0srv.cc:2974]
7ff6c784834c    mysqld.exe!srv_purge_coordinator_thread()[srv0srv.cc:3147]
7ff6c78925c3    mysqld.exe!Detached_thread::operator()<void (__cdecl*)(void)>()[os0thread-create.h:195]
7ff6c7892775    mysqld.exe!std::thread::_Invoke<std::tuple<Detached_thread,void (__cdecl*)(void)>,0,1>()[thread:55]
7ffeb8711542    ucrtbase.dll!_configthreadlocale()
7ffeb9986fd4    KERNEL32.DLL!BaseThreadInitThunk()
7ffebb0fcec1    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0):
Connection ID (thread ID): 0
Status: NOT_KILLED

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.
MySQL server is now stopped.
请按任意键继续. . .

lijiangyan1983

skybin2006 发表于 2025-1-7 12:57
和上面的一样，数据库运行不了

请先参考论坛内的基础教学知识，认真学习。

lijiangyan1983

skybin2006 发表于 2025-1-7 13:00
2025-01-07T04:59:47.979017Z 0 [System] [MY-010116] [Server] F:\TBC\mysql-server\bin\mysqld.exe (mysq ...

不要乱改设置。不会出问题的

skybin2006

我就直接下载下来解压，没有动任何东西

lijiangyan1983

skybin2006 发表于 2025-1-7 13:24
我就直接下载下来解压，没有动任何东西

TODesl 码，我给你远程看看
就发在论坛里

skybin2006

运行start-sever 出现                    ***************************
                    * MySQL for CMaNGOS cores *
                    * PORT : 3310             *
                    ***************************

MySQL for CMaNGOS is currently running.
Do not close this windows before your CORE server!
You can use '.server shutdown 1' on your server console for that.
You can also close this windows by pressing CTRL + C.


2025-01-07T06:11:31.197198Z 0 [System] [MY-010116] [Server] D:\TBC\mysql-server\bin\mysqld.exe (mysqld 8.0.28) starting as process 7216
2025-01-07T06:11:31.230217Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-01-07T06:11:33.270001Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2025-01-07T06:11:33.797023Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2025-01-07T06:11:33.801855Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2025-01-07T06:11:33.849512Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: trx0purge.cc:175:purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no thread 7464
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/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
06:11:33 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x22660ba6bb0
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...
2025-01-07T06:11:33.968081Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2025-01-07T06:11:33.968239Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-01-07T06:11:34.011089Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2025-01-07T06:11:34.011413Z 0 [System] [MY-010931] [Server] D:\TBC\mysql-server\bin\mysqld.exe: ready for connections. Version: '8.0.28'  socket: ''  port: 3310  MySQL Community Server - GPL.
7ff6dc4ffd48    mysqld.exe!my_print_stacktrace()[stacktrace.cc:429]
7ff6db73004b    mysqld.exe!print_fatal_signal()[signal_handler.cc:130]
7ff6db72fe13    mysqld.exe!my_server_abort()[signal_handler.cc:241]
7ff6dc4e643a    mysqld.exe!my_abort()[my_init.cc:263]
7ff6dc71c579    mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:99]
7ff6dc67ab28    mysqld.exe!TrxUndoRsegsIterator::set_next()[trx0purge.cc:175]
7ff6dc67bf7c    mysqld.exe!trx_purge_choose_next_log()[trx0purge.cc:1866]
7ff6dc67c6ef    mysqld.exe!trx_purge_get_next_rec()[trx0purge.cc:1968]
7ff6dc67ba73    mysqld.exe!trx_purge_attach_undo_recs()[trx0purge.cc:2293]
7ff6dc67b1a8    mysqld.exe!trx_purge()[trx0purge.cc:2424]
7ff6dc5e47d0    mysqld.exe!srv_do_purge()[srv0srv.cc:2974]
7ff6dc5e834c    mysqld.exe!srv_purge_coordinator_thread()[srv0srv.cc:3147]
7ff6dc6325c3    mysqld.exe!Detached_thread::operator()<void (__cdecl*)(void)>()[os0thread-create.h:195]
7ff6dc632775    mysqld.exe!std::thread::_Invoke<std::tuple<Detached_thread,void (__cdecl*)(void)>,0,1>()[thread:55]
7ff9a6b31542    ucrtbase.dll!_configthreadlocale()
7ff9a8b06fd4    KERNEL32.DLL!BaseThreadInitThunk()
7ff9a975cec1    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0):
Connection ID (thread ID): 0
Status: NOT_KILLED

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.
MySQL server is now stopped.
请按任意键继续. . .

lijiangyan1983

skybin2006 发表于 2025-1-7 14:12
运行start-sever 出现                    ***************************
                    * MySQL for  ...

是不是开杀毒了，数据库文件不全

lijiangyan1983

skybin2006 发表于 2025-1-7 14:12
运行start-sever 出现                    ***************************
                    * MySQL for  ...

杀毒防火墙关掉，重新下载解压缩

skybin2006

卸载掉杀毒软件，关掉了防火墙，重新下载试试看