Wordfence Crons

  • Resolved yrzhn

    (@yrzhn)


    9 months ago

    Hello ??

    I am trying to optimize cronjobs on multiple sites. Surprisingly to me, Wordfence cronjobs are not the same on all sites, so I want to understand how they appeared, whether some are missing or obsolete (and therefore it’s safe to delete or reschedule them, for example). I am using WP Crontrol.

    The question why I decided to start the thread is actually the following: The wordfence_start_scheduled_scan cron job appears twice on 4 sites and thrice on 1 site, do I need all of them if they exist or is one for each site enough? The action is the same, but the arguments are different.

    Currently there are 5 sites in consideration:

    1. wordfence_daily_cron runs on all 5 sites
    2. wordfence_hourly_cron runs on all 5 sites
    3. wordfence_start_scheduled_scan runs on all 5 sites multiple times.
    4. wordfence_processAttackData runs on a single site (1*) with Wordfence Premium (so I guess that’s from a premium feature)
    5. wordfence_ls_ntp_cron runs on 4 other sites
    6. wordfence_daily_autoUpdate runs on 4 sites (not sure why not all 5 then)
    7. wordfence_batchReportFailedAttempts on one site

    Maybe I should leave them the way they are but just tell me that then (There are slow downs in the backend of all sites as they’re located on the same server, the slow downs happen regularly at around the same time during the day, as a result I am trying optimize the cron jobs which has never been done before with these sites, not even sure if this helps but should be worth investing the time in it I guess).

    Thank you ??

    • This topic was modified 9 months ago by yrzhn.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @yrzhn, thanks for your questions.

    When wordfence_start_scheduled_scan is scheduled multiple times, the wordfence_daily_cron job has added them for future scans. As they run every 3 days on the free plugin, it’s not unusual to have 2 or 3 at one time.

    Scheduling is coordinated with our servers to avoid too many scans starting at the same time. The “different” arguments are just UNIX timestamps.

    If cron jobs are overdue and are all starting at the same time for too many sites on the same server, slow performance can happen. Scheduling them yourself to run every 1 or 5 minutes might help as we recommend at the bottom of this page: https://www.wordfence.com/help/scan/options/#advanced-options

    Ensure you’re not using the same free key on multiple sites, as they can be rate limited for making too many requests to our servers and/or schedule the exact same scan start times due to them being seen as the same single site. Multiple sites with the exact same scan times will naturally use more resources all at once.

    Thanks,
    Peter.

    Thread Starter yrzhn

    (@yrzhn)

    Hi Peter, thank you very much for advice.

    We have like 10+ sites using the same key, we’ll optimize it by using several keys.

    Stay well!

    • This reply was modified 8 months, 4 weeks ago by yrzhn.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Wordfence Crons’ is closed to new replies.