Hi,
Are you using InnoDB with MySQL? We’ve heard of issues with that combination that aren’t Wordfence related.
If not, you may want to try Options -> Other options -> Delete Wordfence tables and data on deactivation to remove Wordfence completely. After that, do a new install of Wordfence and the tables will be created.
-Brian
Thank you.
I have done this.
But
1) it shows an error in the Wordfence plugin which spoils th DB and prevent backup and so on;
2) it is bad (wrong) way to fix…
@vedavrat: If reinstalling Wordfence did not work when using the option that Brian mentioned, then this is a MySQL problem that the host will need to fix. They should be able to help if you show them the messages above, and mention that dropping and re-creating the tables (when reinstalling Wordfence) did not help.
-Matt R
… then this is a MySQL problem that the host will need to fix.
No-no!
The MySQL works fine months and months without any error with all other sites and databases.
But from-time-to-time the Tables of “Wordfence Security” plugin spoils… 🙁
Now again:
mysqlcheck --user=root --host=localhost --check -all-database
gopak_odessa.wp_wfNet404s
Warning : Tablespace is missing for table ‘gopak_odessa/wp_wfNet404s’
Error : Table ‘gopak_odessa.wp_wfNet404s’ doesn’t exist in engine
status : Operation failed
gopak_odessa.wp_wfVulnScanners
Warning : Tablespace is missing for table ‘gopak_odessa/wp_wfVulnScanners’
Error : Table ‘gopak_odessa.wp_wfVulnScanners’ doesn’t exist in engine
status : Operation failed
This problem occures again and again
# mysqlcheck –user=root –check –all-database
vtosik_vedavrat_org.wp_wfNet404s
Error : Table ‘vtosik_vedavrat_org.wp_wfNet404s’ doesn’t exist
…
I am having the same problem. It is amazing how the authors insist it is everyone’s problem and not the plugin. It consistently happens with those two tables and there’s heaps of people reporting the same issue from years ago. Always the same tables and just WF.
Yes it’s really amazing. I’ve seen the problem hundreds of times and my customers point at me but it’s a WF fuckup imo.
Delete the database files from the server with this:
rm -rf /var/lib/mysql/database/wp_wfNet404s.*
rm -rf /var/lib/mysql/database/wp_wfVulnScanners.*
rm -rf /var/lib/mysql/database/wp_wfBadLeechers.*
rm -rf /var/lib/mysql/database/wp_wfHoover.*
After this you might be able to make succesfull .sql backups again!
I had the same problem.
Options -> Other options -> Delete Wordfence tables and data on deactivation to remove Wordfence completely
and a re-installation did not help.
Finally, I found out that the InnoDB files where internally somehow corrupted and I couldn’t find any way to repair this. My mysql_errorlog showed the following messages on reactivation of the Wordfence plugin:
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2016-07-31 17:01:34 1332 [ERROR] InnoDB: Could not find a valid tablespace file for 'wpm/wp_mu_wfNet404s'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2016-07-31 17:01:34 1332 [ERROR] InnoDB: Tablespace open failed for '"wpm"."wp_mu_wfNet404s"', ignored.
2016-07-31 17:01:34 802c06400 InnoDB: Operating system error number 2 in a file operation.
The only way to recover was to completely dump all databases, then stopping the mysql server and removing all database files in the file system. Then I restarted the server which created fresh InnoDB files and finally I imported all data again.
wow… this kinda makes me feel much better about things, but at the same time… UGH!!!
i host several hundred wordpress sites on my server. we had a major DB corruption that totally took the entire server down. we had to rebuild and restore each DB individually. now that i’m monitoring it much more closely now, i’m watching these exact tables corrupt on each wordpress install that has wordfence activated.
out of curiousity, those of you on here with this issue… how often does it happen again?
We are having the exact same problem with the same tables.
Wordfence is banned from our servers now.
