Rate That Rescue
Forum Replies Created
-
Problem appears resolved for me now. Thanks for the fix.
Forum: Plugins
In reply to: [Truncate Comments] Plugin not working for me?Thank you for your reply. It is working again for me now, with WP 4.5.2 and Truncate Comments 1.0.2.
I don’t know after which upgrade it started working again; I didn’t change anything. But it’s all good now with latest WP.
It’s not the PHP memory limit. It just reoccurred on one of the WordPress installs. Now using 6.1.5.
My hosting provider says they scan with ClamAV each week, and all the malicious-like files are quarantined. However, they also say that the MySQL databases are not scanned, so no tables can end up in quarantine.
I’ve not had any problems since they increased the PHP memory limit – so far, at least.
As previously mentioned, MyISAM for me.
Sounds like the same MySQL wp_wfConfig.MYD table corruption unresolved problem as here:
https://ww.wp.xz.cn/support/topic/upgrade-to-wordpress-45-wordfence-613-broken-in-subdirectory-installThanks. My shared hosting provider does not keep MySQL logs, so they couldn’t see any MySQL user activity or crashes.
However, they did see 3 error logs per second being caused by a PHP script memory limit, caused by the file /wp/wp-content/plugins/wp-security-audit-log/classes/Connector/MySQLDBConnector.php
This is from a different security plug-in, WP Security Audit Log, https://ww.wp.xz.cn/support/plugin/wp-security-audit-log. But it does seem to be related to the PHP connection to MySQL database, at least.
They have now increased the PHP memory limit to 368M from 128M, which should resolve that memory limit error. I have now dropped Wordfence’s config tables and reactivated it, to see if the problem reoccurs with the increased PHP memory limit.
Sounds like the same unresolved problem as here:
https://ww.wp.xz.cn/support/topic/upgrade-to-wordpress-45-wordfence-613-broken-in-subdirectory-install?replies=10Sounds like the same unresolved problem here:
https://ww.wp.xz.cn/support/topic/upgrade-to-wordpress-45-wordfence-613-broken-in-subdirectory-install?replies=10Thanks. Both installs are now reporting the exact same problem again, so there’s something that is intermittently deleting the wp_wfConfig.MYD file. So Wordfence keeps losing its configuration and stops working.
Running a database check on each database shows that only this table on each database is corrupted. Everything else is fine.
Yes, both these installs are on the same shared hosting server. I don’t have control of the MySQL install, I just have access to the databases I own.
MySQL is 5.5.45-cll-lve on x86_64 on Linux. It looks like tables are defaulting to MyISAM.
Thanks. However, given the wp_wfConfig table was corrupted (due to the missing MYD file), it was impossible to save the option to delete wordfence tables and data on deactivation.
More concerning, I have just had the exact same corruption on the other WordPress installation (in the root). The same error “wp_wfConfig.MYD not found (Errcode: 2)” was occurring. The fix again was “DROP TABLE wp_wfConfig;”, then deactivate and reactivate Wordfence, which recreates this table.
But, no other MySQL tables are corrupted so far as I’m aware. I can’t think of anything on the hardware or server software that would cause just the wp_wfConfig.MYD file to be lost on two separate MySQL databases.
It seems like a systemic problem with Wordfence, or its interaction with MySQL on the latest update. What do you think could have caused this problem? Has anyone else reported it?
Thanks. I enabled logging and found that it was a MySQL problem. Specifically, MySQL was returning ‘wp_wfConfig.MYD file was not found (Errcode: 2)’. So this table was corrupted in MySQL, and all references to it was throwing this error, including clearing it on uninstall.
I manually did a DROP TABLE in MySQL, and on reinstalling WordFence, it recreated it which fixed the problem.
I’ve no idea how the MYD file got lost on the upgrade (I never touched MySQL or files on the server) but it’s fixed now. It might be nice if WordFence detected problems like this, and allowed you to clear configuration tables with DROP TABLE, which fixes it.
Thanks again.
Thanks for your reply!
It’s Linux 2.6.32. Both are simple single site installs. Everything was working normally until the WordPress 4.5 upgrade, then suddenly Wordfence could not save any options.
All other functionality and plugins are working fine after the upgrade.
Forum: Plugins
In reply to: [Truncate Comments] Plugin not working for me?It was working for me, but it seems to have stopped working after the WordPress 4.4 upgrade.