Corrupted MySQL table on 6.3.5 auto-update

  • Resolved superchargernyc

    (@superchargernyc)


    7 years, 8 months ago

    Today my MySQL server crashed. You can see response times going higher before it crashed: https://cl.ly/0k0L2p0p1h0e

    I tried restarting MySQL but it would not start. I checked the MySQL error log and saw that the table wp_wfFileChanges.ibd was corrupted. Once I removed this file I was able to start MySQL again.

    It appears that today’s auto-update release triggered some kind of feedback loop which caused the Wordfence file change detection feature to break. Have you ever seen this kind of problem before?

    Is there any way to prevent it from happening in the future? I would like to keep auto-updates active, and I would like to use the file change detection feature, but I am not concerned that it could lead to outages in the future as new updates are released.

    Thanks for your time!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter superchargernyc

    (@superchargernyc)

    Also, this seems to be a new db table, as I do not see it in sites where I have previous versions of Wordfence. At this point I am unable to create the table again since I don’t have the schema. I had to delete the .ibd file once it was corrupted.

    Can you provide the schema for this table so I can recreate it?

    My mysql also crashed on my server. I suspect this update to be the cause because I only updated this today…

    Plugin Support wfphil

    (@wfphil)

    Hello,

    A colleague suggested to ask if you are using MyISAM or InnoDB storage engine and recommends that if you are using MyISAM, you should try to change to InnoDB since it’s more stable and less prone to crashes.

    The wfFileChanges is an old table that should not exist in current setups. It is possible that the database that WordPress is running with does not have full/correct permissions. Can you check the MySQL section in the Diagnostics tab on the Tools page. Verify that the database user has all the permissions it needs. If it is lacking ‘drop’ privileges for example, old tables like the one that you have seen will remain in the database when Wordfence tries to upgrade itself. Also, the table currently being used for tracking modified files is called wfFileMods

    Hope this helps.

    Thread Starter superchargernyc

    (@superchargernyc)

    Thanks for the reply, I really appreciate it. These are InnoDB tables and I verified the MySQL user has all the correct permissions. However, I will delete that table since it is no longer needed. Thanks again…

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Corrupted MySQL table on 6.3.5 auto-update’ is closed to new replies.