Apache Friends Support Forum

Unable to Run XAMPP Control Panel on my Windows 64bit OS ( XAMPP Version:8.2.12

I am getting MySQL error ( Error:MySQL shutdown unexpectedly. This may be due to a blocked port, missing dependencies)
I tried replacing the corrupted data file with a new one still not working.I have the Log errors which is pasted below:-
Would appreciate a reply

2024-05-16 18:50:57 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14020
2024-05-16 18:50:57 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:50:57 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:50:57 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:50:57 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:50:57 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:50:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:50:57 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:50:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-05-16 18:50:57 0 [Warning] InnoDB: Are you sure you are using the right ib_logfiles to start up the database? Log sequence number in the ib_logfiles is 300288, less than the log sequence number in the first system tablespace file header, 300522.
2024-05-16 18:50:57 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:50:57 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 18:50:57 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:50:57 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:50:57 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:50:57 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-05-16 18:50:57 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:50:57 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:50:57 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 0 [Note] InnoDB: Buffer pool(s) load completed at 240516 18:50:57
2024-05-16 18:50:57 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:02 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 11044
2024-05-16 18:51:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:02 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:02 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:02 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:02 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:02 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:02 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 2 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 0 [Note] InnoDB: 10.4.32 started; log sequence number 300306; transaction id 170
2024-05-16 18:51:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:02 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:04 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 9324
2024-05-16 18:51:04 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:04 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:04 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:04 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:04 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:04 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:04 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:04 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:04 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:04 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:04 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:05 0 [Note] InnoDB: 10.4.32 started; log sequence number 300315; transaction id 170
2024-05-16 18:51:05 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:05 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:05 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:05 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:12 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2360
2024-05-16 18:51:12 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:12 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:12 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:12 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:12 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:12 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:12 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:12 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:12 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:12 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:12 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:12 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 2 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 0 [Note] InnoDB: 10.4.32 started; log sequence number 300324; transaction id 170
2024-05-16 18:51:12 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:12 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:15 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4868
2024-05-16 18:51:15 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:15 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:15 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:15 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:15 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:15 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:15 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:15 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:15 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:15 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 0 [Note] InnoDB: 10.4.32 started; log sequence number 300333; transaction id 170
2024-05-16 18:51:15 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:15 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:25 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6888
2024-05-16 18:51:25 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:25 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:25 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:25 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:25 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:25 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:25 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:25 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:25 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 0 [Note] InnoDB: 10.4.32 started; log sequence number 300342; transaction id 170
2024-05-16 18:51:25 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:25 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:45 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 12396
2024-05-16 18:51:45 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:45 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:45 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:45 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:45 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:45 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:45 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:45 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:45 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:45 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:45 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 300351; transaction id 170
2024-05-16 18:51:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:46 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:46 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:50 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7060
2024-05-16 18:51:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:50 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:50 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:50 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:50 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 18:51:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:50 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 0 [Note] InnoDB: 10.4.32 started; log sequence number 300351; transaction id 170
2024-05-16 18:51:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:50 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:53 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6548
2024-05-16 18:51:53 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:53 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:53 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:53 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:53 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:53 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:53 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:53 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:53 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:54 0 [Note] InnoDB: 10.4.32 started; log sequence number 300360; transaction id 170
2024-05-16 18:51:54 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:54 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:54 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:54 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:54 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:59 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3908
2024-05-16 18:51:59 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:59 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:59 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:59 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:59 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:59 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:59 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:59 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:59 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 0 [Note] InnoDB: 10.4.32 started; log sequence number 300369; transaction id 170
2024-05-16 18:51:59 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:59 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:52:02 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 17684
2024-05-16 18:52:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:52:02 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:52:02 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:52:02 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:52:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:52:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:52:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:52:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:52:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:52:02 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:52:02 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:52:02 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 0 [Note] InnoDB: 10.4.32 started; log sequence number 300378; transaction id 170
2024-05-16 18:52:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:52:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:52:02 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:52:36 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18332
2024-05-16 18:52:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:52:36 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:52:36 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:52:36 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:52:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:52:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:52:36 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:52:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:52:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:52:36 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:52:36 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:52:36 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 0 [Note] InnoDB: 10.4.32 started; log sequence number 300387; transaction id 170
2024-05-16 18:52:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:52:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:52:36 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 0 [Note] Server socket created on IP: '::'.

Dear all,

I do so need your help, please!

I have impemented an offline Wordpress installation via Xampp 8.2.12 (+ Apache 2.4.58 + MariaDB 10.4.32 + PHP 8.2.12 (VS16 X86 64bit thread safe) + PEAR + phpMyAdmin 5.2.1).

It worked nicely for 3 months, but now the MySQL has crashed somehow and I cannot access phpMy Admin anymore. The MySQL ErrorLog actually says it's a bug:

...2024-04-16 9:46:44 0 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2024-04-16 9:46:44 0 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2024-04-16 9:46:44 0 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2024-04-16 9:46:44 0 [Note] InnoDB: 000000000000000000000000000000000000000000000000d21fe19709142bc5
2024-04-16 9:46:44 0 [Note] InnoDB: End of page dump
2024-04-16 9:46:44 0 [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 https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-16 9:46:44 0 [ERROR] [FATAL] InnoDB: Unable to read page [page id: space=33, page number=1] into the buffer pool after 100. The most probable cause of this error may be that the table has been corrupted. See https://mariadb.com/kb/en/library/innodb-recovery-modes/
240416 9:46:44 [ERROR] mysqld got exception 0x80000003 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data
Minidump written to C:\xampp\mysql\data\mysqld.dmp

Does anyone have an idea what to do to save the installation?

Best regard, Astrid

Hallo zusammen,

habe das selbe Problem. Über den Befehl (mysqld --console --skip-grant-tables --skip-external-locking) kann ich Ihn wunderbar notstarten. Ist aber leider keine Dauerlösung.
Folgender Fehler wird beim Notstart angezeigt:
2024-02-13 13:33:37 0 [Note] InnoDB: End of page dump
2024-02-13 13:33:37 0 [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 https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-02-13 13:33:37 0 [ERROR] InnoDB: Background Page read failed to read or decrypt [page id: space=3, page number=0]
2024-02-13 13:33:37 0 [Note] InnoDB: Buffer pool(s) load completed at 240213 13:33:37

Wenn ich dann den Befehl (mysqlcheck -r --databases mysql --use-frm) für die Reparatur einleite. Wurstelt er eine Weile druch und bricht mit einer Fehlermeldung, Datenbank nicht erreichbar weieder ab und der Datenbank-Dienst ist wieder gestoppt).

Windows 11 Home 64Bit
Xampp Version: 8.2.4
Xampp CP Version: v3.3.0
MySQL Version: 5.x
Server wird manuell gestartet, keine Dienste installiert.

Liebe Grüße und danke für die Hilfe,
Seppel

Good day everyone. It is my first time installing xampp on my windows 8.1 64 bit laptop. I installed it successfully, but when I start Apache I got an error regarding the procedure entry point "isspace" could not be located in the dynamic link library d:\xampp\apache\bin\pcre2-8.dll how do I fix this? Please help me I really need to have Xampp on my windows so that I can do my School Project. What should I do? Even when I install newer/latest version I still got the same error.

There is no 64bit Xampp 7.0.

Xampp for Windows was only compiled for 32bit, it has switched to 64bit later (i dont remember the first 64bit Windows Xampp, it was announced here a couple years ago).

Start httpd.exe (Apache) in a Terminal and look for error messages. The httpd.exe should be in f:\software\xampp-portable-win32-7.0.33-0-vc14\xampp\apache\bin\httpd.exe

P.S.: As i can see from the folder name, Xampp 7.0 is a 32bit(!) Installation, but you are running Vista 64bit! Windows can run 32bit Applications, but you need to have a proper environment installed. Maybe some C-libraries or so are missing, when starting httpd.exe manually in a CMD Shell it should tell you about. Anyway, Vista is also pretty old and maybe its not supported by Xampp 7.0. I dont know, but its everything very outdated.

Hello I stopped using xampp for some time because when they went to 64bit ( I use windows 10) it was OK to install and run but it would always have a fault/issues when trying to stop or Exit the xampp. It's been a couple years so would like to think this issue have been fixed after so long.

Can anyone tell me if this issue has been fixed yet or been brushed under the carpet - still having same problems?

It's a shame they never seem to try and fix small issues as it was such a good/useful bit of software.

I just dont really want to download 'n' install to find since going from 32bit to 64bit no-one seem to have fixed this issue.

many thanks for any infomation (and lets hope it's fixed)

thanks for reading

Thank you for your fast and quick response.

Many Kind Regards

Pete

There is no XAMPP version available for ARM processors.

I'm installing Xampp on a Raspberry Pi running Ubuntu.

I'm getting the error as below, I've checked the OS and I'm running the 64bit version.
See my terminal installation string and evidence of 64bit OS.


<hiddenname>@pi4:~/Downloads$ chmod 755 xampp-linux-x64-8.2.4-0-installer.run

<hiddenname>@pi4:~/Downloads$ sudo ./xampp-linux-x64-8.2.4-0-installer.run
./xampp-linux-x64-8.2.4-0-installer.run: 2: Syntax error: Unterminated quoted string

<hiddenname>@pi4:~/Downloads$ uname -a
Linux pi4 5.15.0-1012-raspi #14-Ubuntu SMP PREEMPT Fri Jun 24 13:10:28 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

Can anyone give me any pointers, please?

You are mixing 64bit Xampp installation with 32bit DLLs from your download, that does not work.

This is the version I downloaded,

php-5.6.40-Win32-VC11-x64

This is the 64 bit version correct?

You are mixing 64bit Xampp installation with 32bit DLLs from your download, that does not work.

Nobbie wrote:Alles.
Welche Software hast Du installiert?
In welches Verzeichnis hast Du sie installiert?
Wie rufst Du sie im Browser auf?
Was genau passiert dann?
Wie lautet die vollständige, exakte Fehlermeldung?
Wie hast Du die entsprechende Software installiert?

Vorab: Inzwischen ist klar, es sind nur WordPress Sites, die nicht erreichbar sind.

Software und Verzeichnisse:
Wo soll ich anfangen, da sind ur viele Progs. Von welchen Rechner soll ich die nennen?
Also da wäre bei allen Rechnern bloß Win 10 64bit mit dessen Defender und bordeigener Firewall; Chrome, und am "XAMPP-PC": XAMPP Version: 7.4.29 ... und ... ja was wäre noch wichtig? "Alles" ist mit Verlaub a bisserl viel.

Aufruf: erfolgt (vom "XAMPP-PC") eben wie üblich, per http://localhost/ oder http://127.0.0.1/ und von anderen Geräten aus entweder per deren IP oder über deren Rechnernamen.
Was passiert / Fehlermeldung: wie gesagt, dashboard öffnet und alles (außer WP Sites) ist aufrufbar. Sites auf WP Basis melden "Website nicht erreichbar"

Wie ich welche Software installiere? Naja, wie jeder andere auch. Nein ich gehöre nicht zu denen, die irgendwas selbst zusammenstellen oder "kompilieren" oder wie das heißt. Alles wird per Setup, weiter, ok, fertig aus installiert. Ich verstehe die Frage nicht ganz und noch weniger warum es wichtig ist, hier alle Setup-Vorgänge, die tw. viele Jahre zurückliegen anzugeben.

Hi

Installed xampp on Windows 10 64bit. Local development working fine on port 80. If I change it to anything like 8080 for remote access, the local website cannot be accessed. Only apachefriends and phpmyadmin pages are visible.

Let me know please what information do I need to share.

Hi,

ich vermute, dass ich durch ein doppeltes Starten der MySQL-Datenbank in kurzer Zeit über das XAMPP Control Panel meine Konfiguration zerschossen habe. Jedenfalls habe ich seit der letzten Nutzung vor wenigen Tagen keine Änderungen vorgenommen, die den nun auftretenden Fehler sonst erklären können:

Die Datenbank lässt sich ganz normal über das XAMPP Control Panel starten, jedoch wird jeder Zugriff auf die Datenbanken (via php-script in einem Browser) mit solchen Fehlermeldungen verweigert:

Warning: mysqli::__construct(): (HY000/1044): Access denied for user 'MBGucky'@'localhost' to database 'mbgucky' in Y:\access.php on line 39
Keine Verbindung zur Datenbank (1044) Access denied for user 'MBGucky'@'localhost' to database 'mbgucky'

Daraufhin habe ich phpmyadmin über den Admin-Button im Control Panel aufgerufen und hier finde ich auch ganz unten schon eine Fehlermeldung:

Der phpMyAdmin-Konfigurationsspeicher ist nicht vollständig konfiguriert, einige erweiterte Funktionen wurden deaktiviert. Finden Sie heraus warum.
Oder wechseln Sie in einer beliebigen Datenbank zum Tab „Operationen“, um die Einstellung dort vorzunehmen.

Ein Klick auf "Finden Sie heraus warum" zeigt dann folgendes:

Konfiguration des pmadb… fehlerhaftDokumentation
Allgemeine Verknüpfungsfunktionen Deaktiviert
Eine Datenbank mit Namen „phpmyadmin“ anlegen und dort die phpMyAdmin-Konfigurationsspeicher-Tabellen einrichten.
Neues phpMyAdmin-Fenster

Eine Datenbank namens phpmyadmin existiert aber, wird jedenfalls links in der Spalte mit angezeigt.

Mein nächster Versuch war es, den Benutzer wieder anzulegen. Dazu habe ich auf der Startseite von phpmyadmin oben auf "Benutzerkonten" geklickt.
Hier erscheint jedoch nur die Fehlermeldung:

#1034 - Fehlerhafte Index-Datei für Tabelle 'db'; versuche zu reparieren

An der Stelle bin ich leider mit meinem Latein am Ende. Könnt ihr mir sagen, was ich versuchen kann um wieder auf die DB zugreifen zu können?
Oder bleibt mir nur eine komplette Neuinstallation? (Datenbanken konnte ich exportieren. Notfalls wäre das also eine Option. Es geht mir aber auch ein bisschen um den Lerneffekt. Deshalb wäre eine Reparatur sodenn möglich von mir bevorzugt.)

Ich nutze folgende Versionen unter Windows 11 Pro:

ApacheFriends XAMPP Version 7.4.26
+ Apache 2.4.51
+ MariaDB 10.4.22
+ PHP 7.4.26 (VC15 X86 64bit thread safe) + PEAR
+ phpMyAdmin 5.1.1
+ OpenSSL 1.1.0g
+ ADOdb 518a
+ Mercury Mail Transport System v4.62 (nicht in der Portable Version)
+ FileZilla FTP Server 0.9.41 (nicht in der Portable Version)
+ Webalizer 2.23-04 (nicht in der Portable Version)
+ Strawberry Perl 5.32.1.1 Portable
+ Tomcat 8.5.73
+ XAMPP Control Panel Version 3.3.0.
+ XAMPP mailToDisk 1.0 (schreibt verdendete Mails über PHP auf die Festplatte unter <xampp>\mailoutput. In der php.ini als Mail Default aktiviert.)


(Hab das jetzt mal so aus der Readme kopiert. Hoffe das stimmt alles so)

Gruß

MBGucky