• Resolved Robert

    (@rsterry48)


    Since we updated to WP 6.1.1 we are getting this cron event appearing as an error in our PHP Error Log on the Dashboard [we are using Error Log Monitor to display in the Dashboard]. I assume it refers to Wordfence?

    Cron reschedule event error for hook: wf_scan_monitor, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”wf_scan_monitor_interval”,”args”:[],”interval”:60}

    This has never appeared in the PHP Error Log before. This cron event doesn’t appear in the list of events [in WP Crontrol].

    Any idea why this is happening? I can set Error Log Monitor to ignore the error so it doesn’t appear in the Dashboard, but is this a good idea? Do we need it?

    Many thanks
    Robert

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @rsterry48, thanks for your message.

    Sometimes with tools such as the one you’ve been using, or Query Monitor to name another, errors can crop up that would have normally gone unnoticed and not caused fatal errors in the running of your site or Wordfence.

    If the job mentioned does not appear in your list of cron jobs any more, things should be fine so long as your scans are completing. This cron job just watches a running scan to ensure the scan finishes, and it does not need to be rescheduled when it ends. This looks like it could be caused by a race condition where two hits occurring at the same time are both trying to update cron jobs, which has been a long-standing issue in WordPress. It’s likely that one of the hits succeeded, and this error is the result of the second.

    Thanks,

    Peter.

    Thread Starter Robert

    (@rsterry48)

    Thank you Peter. Most helpful advice.

    Plugin Support wfpeter

    (@wfpeter)

    No worries @rsterry48. If you have any Wordfence questions in future, by all means start a new topic and we’ll always be happy to help out!

    Peter.

    Got the same error too with WP6.2.2.

    [26-May-2023 09:21:32 UTC] Cron reschedule event error for hook: wf_scan_monitor, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”wf_scan_monitor_interval”,”args”:[],”interval”:60}

    The events continue to run. Probably database or WP related.

    Didier.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PHP Log error-wf_scan_monitor’ is closed to new replies.