Still happening.
Since support is unresponsive, flagging this plugin as broken.
Hi
Actually I emailed our dev team when this case was created. Unfortunately, we have had a full plate for the last week and a half so it might have been missed in the deluge of emails I had to send in.
I realize you are having troubles and hope we can help solve them but it seems unfair to flag a plugin as broken when since I started here I have only seen three cases about the wf_hoover file, and the other two don’t seem to be what you are experiencing.
Let’s see if we can sort out whats going on. What version of the plugin are you running? What version of WordPress? Was the plugin working vbefore and stopped working? Was there any changes before it stopped? I see you are using InnoDB instead of myisam. Is this correct?
Thanks!
tim
Hi David,
(I edited this after posting it for clarity – see marked paragraph)
This looks like an issue with your server. Please read the following article on the mysql docs site:
http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting-datadict.html
It looks like your data dictionary is out of sync. Specifically you have a .frm file that exists in your schema for wfHoover but there is no corresponding data dictionary in the InnoDB file. (read the article to understand how mysql maintains two separate dictionaries)
Edit: (adding this for clarity) Please note that we don’t control how frm files are created or deleted or the integrity of the InnoDB and mysql data dictionary so this really can’t be our fault. We just run standard SQL create/delete statements and don’t even force a specific table type – we just use the default. And we’re using InnoDB on our own servers so there’s no known incompatibility there.
So I think there are a few possibilities:
1. You ran out of disk space and an frm file was created but the server could not update the innodb dictionary during update.
2. You have disk corruption and the innodb file was not updated or the frm was not deleted during plugin installation or deinstallation respectively.
3. You changed your storage engine from MyISAM to InnoDB and frm files were left behind that is confusing mysql.
4. Your server crashed, was suddenly rebooted or you had a memory or other issue that caused corruption in the innodb table file.
We have had no other reports of this, so for now please unmark our plugin as broken until you can either confirm that it is our plugin causing this or we figure out that it’s something else.
Let me know if you think it may be one of the above. Also let me know if you’re using the “innodb_file_per_table = 1” option in your my.cnf which will result in each table having it’s own file in innodb or whether you have one monolithic innodb file (the default).
Mark.
From last update, “It looks like your data dictionary is out of sync.”
This is what I thought + is incorrect.
When I first saw this problem I went through a repair cycle, which worked, meaning the .ibd file was regenerated.
Then a few minutes later, it’s gone again.
There are 100s of WP + WordFence installs on this physical server + only a few WordFence installs are acting like this.
Also be advised, because of this problem, WordFence breaks normal mysqldump backups, as mysqldump stops on the first data table error encountered.
So as long as this problem persists, anyone using mysqldump for backups without the –force option, doesn’t likely realize all their backups are likely broken.
This occurs because mysqldump stops when the first error is encountered.
Seriously this is an ugly bug + should be fixed.
David to me it’s fairly clear you have an issue with your database and one of the symptoms is that Wordfence is unable to create tables and/or store data in them on your server. I’m unsure how you’re making the leap that it’s Wordfence that’s the cause of your DB issues. We just use the MySQL API as it’s designed – on tens of thousands of sites every day and WF runs fine. Usually when there’s a serious issue you’ll see many other users piling onto this thread with “me too” posts.
So I think you need to investigate your DB. You’ve flagged WF as broken and you’re saying we have an ugly bug, but help me understand what makes you think this has anything to do with Wordfence.
As far as I’m aware, it’s not currently possible for an app using the PHP mysql interface to do something that produces low level table corruption – and if it were that would be a bug in MySQL or the PHP interface, not the PHP app itself.
Regards,
Mark.
Marking this resolved until we hear otherwise. David please feel free to mark this unresolved if you have any data to add that needs investigation by us. I’m happy to do a deep investigation into this but for now it appears to be a server issue of some sort.
Thanks,
Mark.
I am actually having this exact same issue, I’ll start a new thread, but thought a comment was necessary since it was actually noted that there weren’t “Me, too” comments 🙂
This started for us with the latest updates and became evident during backups not being able to complete, as described above.
Happening in at least 3 different server environments. (we manage a large number of sites, not just those we host)
I asure you, this is not a problem with the database.
I’ve repaired this over + over. Everytime WordFence runs, the data table is corrupted.
There is only one table being corrupted on this system. 100s of sites/databases.
Only one WordFence table corrupted.
Still occurring with latest version of WordFence.
I have just started seeing this, but with the wfVulnScanners table, across several WordPress databases on the same server.
Glad I have come across this thread! I too am experiencing the same issues but appears in wfHoover, wfNet404s and wfVulnScanners tables using the latest version of WordPress and Wordfence.
Only detected the issue on a handful of sites running on the same server so if it were a mysql bug going on I would be expecting it to affect everything?
Have tried deactivating and activating with no luck…
Any other ideas would be greatly appreciated!
I have had to ditch WordFence altogether because of this. I am now using iThemes Security (formerly Better WP Security).
