Wordfence Crashed MySQL!

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

Wordfence Crashed MySQL!

Postby neoxphuse » 27. July 2023 04:14

So I was trying to do a scan with Wordfence... first time I've ever used it. My internet dropped, and I reconnected the WiFi. The scan was stuck for the longest time, and WordPress wouldn't load. So I had to shut down all applications and restart. That's when I couldn't get start Xampp and MySQL gave me the following errors. Someone please help me!!! I usually am able to use the backup folder and it would work. But it seems this time it won't work!

2023-07-26 20:03:22 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 9648
2023-07-26 20:03:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-07-26 20:03:23 0 [Note] InnoDB: Uses event mutexes
2023-07-26 20:03:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-26 20:03:23 0 [Note] InnoDB: Number of pools: 1
2023-07-26 20:03:23 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-07-26 20:03:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-07-26 20:03:23 0 [Note] InnoDB: Completed initialization of buffer pool
2023-07-26 20:03:23 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1178878299
2023-07-26 20:03:23 0 [Note] InnoDB: Ignoring data file '.\theraco\#sql-ib317.ibd' with space ID 302. Another data file called .\theraco\wp_wfhoover.ibd exists with the same space ID.
2023-07-26 20:03:23 0 [ERROR] InnoDB: Tablespace 322 was not found at .\theraco\wp_wffilemods.ibd.
2023-07-26 20:03:23 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2023-07-26 20:03:23 0 [ERROR] InnoDB: Tablespace 325 was not found at .\theraco\wp_wfhoover.ibd.
2023-07-26 20:03:23 0 [ERROR] InnoDB: Plugin initialization aborted with error Tablespace not found
2023-07-26 20:03:23 0 [Note] InnoDB: Starting shutdown...
2023-07-26 20:03:23 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-07-26 20:03:23 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-07-26 20:03:23 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-07-26 20:03:23 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-07-26 20:03:23 0 [ERROR] Aborting
2023-07-26 20:05:57 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 14976
2023-07-26 20:05:57 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-07-26 20:05:57 0 [Note] InnoDB: Uses event mutexes
2023-07-26 20:05:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-26 20:05:57 0 [Note] InnoDB: Number of pools: 1
2023-07-26 20:05:57 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-07-26 20:05:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-07-26 20:05:57 0 [Note] InnoDB: Completed initialization of buffer pool
2023-07-26 20:05:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1178878299
2023-07-26 20:05:57 0 [ERROR] InnoDB: Tablespace 322 was not found at .\theraco\wp_wffilemods.ibd.
2023-07-26 20:05:57 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2023-07-26 20:05:57 0 [ERROR] InnoDB: Plugin initialization aborted with error Tablespace not found
2023-07-26 20:05:57 0 [Note] InnoDB: Starting shutdown...
2023-07-26 20:05:57 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-07-26 20:05:57 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-07-26 20:05:57 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-07-26 20:05:57 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-07-26 20:05:57 0 [ERROR] Aborting

I'm not sure what can I do... please note I was doing this in a localhost environment and was close to getting this live. The backup doesn't work.

Fortunately my database is backed up with UpdraftPlus in Wordpres but I can't even get MySQL to start.
neoxphuse
 
Posts: 1
Joined: 27. July 2023 04:08
XAMPP version: 3.3
Operating System: window 11

Re: Wordfence Crashed MySQL!

Postby Nobbie » 27. July 2023 18:18

Killing MariaSQL server instead of a clean shutdown mostly results in a corrupted database. If you have a backup, reinstall a new MariaDB and import your backup. It would have been save to create a copy of the whole data folder before cracking it with Wordfence.
Nobbie
 
Posts: 13176
Joined: 09. March 2008 13:04


Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 58 guests