WP Cron Events Says…

  • Resolved OFS

    (@ep2012)


    9 years ago

    Hi,

    So we’ve been in contact with you a few times re: issues with Wordfence causing memory issues ever since we moved from a reseller shared environment over to a VPS.

    This has caused my sites to go down over & over again.

    Nothing you suggested helped solve the problem. We even had to deactivate WF on one site just to see if it stopped core dump files.

    Now our hoster asked us about what WP cron jobs are running, so we installed WP Crontrol & we looked at the report for just one site out of 30. Even though we turned off WF’s automatic scans, it’s showing a cron job to scan twice a day.

    So something is seriously wrong here.

    Please help.

    Thanks

Viewing 10 replies - 1 through 10 (of 10 total)
  • menken

    (@menken)

    9 years ago

    I have a stopgap solution for you:

    Go to Wordfence -> Scan -> Options and all the way down to “Time limit that a scan can run in seconds” (right before the SAVE OPTIONS) button.

    set the time limit on your scans to 2 seconds, and save. You’ll get an email that the scan ran over and aborted, but it won’t take your site down.

    Thread Starter OFS

    (@ep2012)

    9 years ago

    Ok, thanks for that, but why should we have to do that? Why doesn’t WF know NOT to do something we tell it not to do?

    Someone is now saying WP Cerber is better. I’m going to research that one.

    I’ve gone thru hell b/c of these issues : (

    Thanks again

    wfyann

    (@wfyann)

    9 years ago

    Hi @ep2012,

    When you deactivated Wordfence, was the “Delete Wordfence tables and data on deactivation” box ticked?

    Alternatively you can also install the Wordfence Assistant plugin in order to remove all Wordfence data in your database.

    Thread Starter OFS

    (@ep2012)

    9 years ago

    Hi wfyann,

    No we didn’t deactivate it (I mean we did, but that’s not what the issue was). We unchecked live scan I think it was. My website coder is off now, so I can’t double check the exact feature we unchecked. Whatever it is that scans the site 24/7.

    The minute I turned it back on 2 days ago my sites started freaking out. My sites have been down more than they’ve been up & the only reason I haven’t deactivated it again is b/c I need them to finally tell me what the issue is, not just mask the symptoms by deactivating WF.

    Thanks for getting back to me.

    Thread Starter OFS

    (@ep2012)

    9 years ago

    Hi @wfyann,

    To be clear, one site we did deactivate WF on & then the other day I turned it back on. When we did that, even though automatic scans WAS turned off, it will still running via a WP cron job. Why?

    No we didn’t delete the tables or data b/c we wanted to turn it back on once the issue of why it’s creating the problems was resolved.

    These issues have been happening on 2-3 different sites, not just one.

    Please LMK

    wfyann

    (@wfyann)

    9 years ago

    Hi @ep2012,

    Indeed, even though the automatic scheduled scans feature is disabled, Wordfence scheduled scans cron jobs still appear in the Tools –> Diagnostics –> Cron Jobs list.

    Even though those scans won’t actually be launched, it makes sense that they be removed altogether once the “Enable automatic scheduled scans” box is unchecked.

    I created an internal request so our development team can look into this issue and implement a solution in a future release.

    In the meantime I suggest you use WP Crontrol to delete those jobs manually.

    Thread Starter OFS

    (@ep2012)

    9 years ago

    Hi @wfyann,

    The problem is, they weren’t just showing up, I was told they were scanning & using up tons of memory causing my server to overload.

    Plus if we delete it from the cron job area, what if I want to turn the automatic scans back on?

    wfyann

    (@wfyann)

    9 years ago

    Hi @ep2012,

    I’m still trying to reproduce the behavior you’re describing; so far when I disable the automatic scheduled scans functionality, even though cron jobs still appear, scans do not run.
    Could it be that the scanning activity you saw was related to another Wordfence instance running on the same host?

    Regarding the manual deletion of the cron jobs: you will need to deactivate/re-activate Wordfence for new wordfence_start_scheduled_scan cron jobs to be created.

    For reference purpose the internal request related to this issue is #FB5400

    Thread Starter OFS

    (@ep2012)

    8 years, 12 months ago

    Hi,

    So based on all the issues with my hoster (I’m leaving them asap as my sites have been down non stop for months now), & someone else saying they have also had issues with WordFence, I removed it from all my sites.

    I really wanted to keep it & it may not be the only reason for the issues on the server, but the fact that it leaves that WP Cron behind & the geeks at the hosting company were blaming Wordfence, I thought it would be safer to just delete it.

    wfyann

    (@wfyann)

    8 years, 11 months ago

    Hi @ep2012,

    I’m sorry you had to remove Wordfence from your sites.

    I regret we didn’t get to further investigate but I understand that experiencing performance issues with a plugin is the last thing you’d want.

    However should you decide to give Wordfence another try at some point in the future, we’ll be happy to help you get things up and running.

    As I previously mentioned the automatic deletion of Wordfence related cron jobs will be implemented in a future version. Thanks again for bringing this behavior to our attention.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘WP Cron Events Says…’ is closed to new replies.