Wordfence Crashed and MySQL not starting

  • Resolved neoxphuse

    (@neoxphuse)


    1 year, 8 months ago

    First time setting up Wordfence and was doing a scan when my internet dropped… this caused the scan to pause and I finally realized this and reconnected, but it wouldn’t move. I tried to reconnect to WordPress but that didn’t work either so I closed everything including Xampp.

    After this, Xampp Mysql wouldn’t start and is now giving me this error. Typically I can just go to my backup folder and it will work. This time it’s not working and I was close to finishing the site. It was on a localhost environment. I added “innodb_force_recovery=1” to my.ini but it’s not working still. Someone, someone, please help me!

    2023-07-26 20:30:30 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 15496
    2023-07-26 20:30:30 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2023-07-26 20:30:30 0 [Note] InnoDB: Uses event mutexes
    2023-07-26 20:30:30 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
    2023-07-26 20:30:30 0 [Note] InnoDB: Number of pools: 1
    2023-07-26 20:30:30 0 [Note] InnoDB: Using SSE2 crc32 instructions
    2023-07-26 20:30:30 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
    2023-07-26 20:30:30 0 [Note] InnoDB: Completed initialization of buffer pool
    2023-07-26 20:30:30 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1178878299
    2023-07-26 20:30:30 0 [ERROR] InnoDB: Tablespace 322 was not found at .\theraco\wp_wffilemods.ibd.
    2023-07-26 20:30:30 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
    2023-07-26 20:30:30 0 [ERROR] InnoDB: Plugin initialization aborted with error Tablespace not found
    2023-07-26 20:30:30 0 [Note] InnoDB: Starting shutdown…
    2023-07-26 20:30:30 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
    2023-07-26 20:30:30 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
    2023-07-26 20:30:30 0 [Note] Plugin ‘FEEDBACK’ is disabled.
    2023-07-26 20:30:30 0 [ERROR] Unknown/unsupported storage engine: InnoDB
    2023-07-26 20:30:30 0 [ERROR] Aborting

Viewing 1 replies (of 1 total)

  • You might have to try reinstalling Wordfence. You can use the same license you were issued before. When you choose to deactivate the plugin you should see a pop up that asked what you want to delete. Delete all tables and data. Then when you reactivate Wordfence it should set the tables back up that it needs.

    We can’t offer support for your database question but someone else in the community might be able to. Windows isn’t officially supported.

    Mia

Viewing 1 replies (of 1 total)
  • The topic ‘Wordfence Crashed and MySQL not starting’ is closed to new replies.