You know what? Deactivate the Sucuri plugin (temporarily).
We identified an issue with the server that is storing the audit logs, the disk is full 😛 so we will start compressing the data before storing to save some space, but while we do this new logs will be (probably) rejected. The current code of the plugin (even after the update released today) will not understand this rejection and will (instead) throw some warnings which may affect other extensions that rely on events triggered during the initialization of the site like the traffic monitoring that you mentioned.
I will leave this ticket open until I get more information from my co-workers, the compression of current logs stored in the server may take a while, but I will update this thread when everything is working correctly once again.
Thread Starter
Luis
(@lemoreno)
Thanks Yorman.
I tested my solution in another WP install that is live and my fix didn’t work. With Securi disabled, Wordfence didn’t finish its scan. I disable live traffic and that didn’t work either to help Wordfence complete the scan.
Let me go post to Wordfence now…
Thanks!
Okay, can you paste the link to the thread that you will create in the Wordfence forums so I can follow the discussion and (maybe) find a solution to this inconsistency?
Thread Starter
Luis
(@lemoreno)
Hello, I read the comments in the Wordfence thread, I have an vague idea of what the issue is but I want to confirm before making more changes to the Sucuri plugin’s code.
Three weeks ago I added a new action interceptor for Ajax requests [1] after a suggestion in this thread [2] yesterday people started to report an increment in the CPU cycles of their servers after the release of version “1.7.12”. I modified the code once again here [3] to fix a minor bug.
After some minutes checking the commits associated with version “1.7.12” I submitted some changes to the development branch with two new options to disable the DNS lookups (used when the reverse proxy option is enabled) and the comment monitor recently added, but people did not notice much improvement with this.
Going back to Wordfence I realized that they make heavy use of Ajax requests to perform multiple tasks including the file system scans, if every request is monitored by this code [3] then that is where the issue is. I will disable this, in a few minutes will submit the changeset and would appreciate if you can test the development version of the plugin [4] when this is in the WordPress repository.
[1] https://plugins.trac.wordpress.org/changeset/1194820
[2] https://wordpress.org/support/topic/unknown-ajax-actions
[3] https://plugins.trac.wordpress.org/changeset/1209752
[4] https://downloads.wordpress.org/plugin/sucuri-scanner.zip
Thread Starter
Luis
(@lemoreno)
Hi Yorman,
Thanks for your deep research in this issue.
I downloaded [4], deactivated and deleted Sucuri plugin (my old settings are gone 🙁 now)
The WordFence scan is still going on but it is progressing a bit more. So that is a good thing. I reverted the slow down option from 15 secs back to default (8 secs maybe? IDK).
The Wordfence scan time log shows is still on the same task since 4:06 PM. Still a bit better but not completing yet.
Thank you!
I see, thanks for testing the new code. Some people have confirmed [1] that a new option added in version “1.7.13” to allow the deactivation of a feature named “XHR Monitor” included in the Sucuri plugin in version “1.7.12” helped them to keep the speed of their sites in a normal state, I thought it could help you too.
I will leave this open until your other thread is resolved.
[1] https://wordpress.org/support/topic/version-1712-update-affecting-site-performance?replies=22#post-7242615
Thread Starter
Luis
(@lemoreno)
Hi Yorman,
Apologies I forgot to mark this topic as solved. I think the “XHR Monitor” option has an affect depending what version of PHP your host is using.
I recently had this issue:
https://wordpress.org/support/topic/php-5511?replies=7
Thanks for your help!
