Replies: 0
Hello,
I’ve got Wordfence 7.1.3 running on WP 4.9.5, CentOS 7 with SELinux.
I’ve been having issues with scans causing HTTPD threads to max out the CPU and hang there. So I disabled the automatic scans. But this morning I got an alert that the same issue had cropped up – and when I look at my HTTPD logs, I do see the WP cron triggering a Wordfence scan:
/wp-cron.php?doing_wp_cron=…
/wp-admin/admin-ajax.php?action=wordfence_testAjax
/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=standard&cronKey=…
All of the above requests are originating with the server’s internal IP address.
When I look at Wordfence diagnostics, I do see three Wordfence cron jobs listed: wordfence_hourly_cron, wordfence_daily_cron, wordfence_email_activity_report
Interestingly, I don’t see anything in the scan logs for this recent scan.
I did find this support thread from about a year ago and I don’t know if the issue was ever resolved:
https://wordpress.org/support/topic/wp-cron-events-says/
Please help!