WordFence error in PHP Log

  • Resolved dogwomble

    (@dogwomble)


    8 months, 1 week ago

    Hey guys,

    This is possibly something fairly trivial but thought I’d put something in here. This is possibly user error.

    I’ve got a site that I’ve recently set up, running WordPress on PHP 8.3. I’ve deliberately set the hosting up to only use the extensions that WordPress requires – which is possibly where user error comes into it because there’s possibly something I need to enable. This was set based on what the WordPress Site Health tool asks me to enable.

    I do notice though that I get the following in my PHP error log:

    Cron unschedule event error for hook: wordfence_start_scheduled_scan, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[1720706400]}

    It seems the error is not critical – it seems the scan still runs, as I get the usual email I would expect giving me the outcome of that scan. It would still be nice to try and resolve it.

    Is this likely caused by me being a bit too aggressive with what extensions I’ve culled, or is there possibly another explanation?

    • This topic was modified 8 months, 1 week ago by dogwomble.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfmargaret

    (@wfmargaret)

    Hi @dogwomble,

    When you look at?Wordfence > Tools > Diagnostics > Cron Jobs, do you see anything reporting as overdue, or does everything seem to be running? If it’s the latter, there’s a chance the error came from a double-hit rather than an outright failure.

    WordPress can sometimes start two copies of wp-cron to run the same jobs, triggered by multiple hits on the site starting close together. As wp-cron’s locking is imperfect, the jobs may run twice. When one finishes, it updates the list of cron jobs, and then when the other finishes, it’s unable to make the same update, because it’s already done. There was previously no log to report it, but now it’s intentionally logged in WordPress.

    As long as cron jobs run normally, the error can be disregarded and there is nothing to worry about!

    Thanks,
    Margaret

    Thread Starter dogwomble

    (@dogwomble)

    Thanks for your reply. Checking the cron jobs and there seem to be done overdue, so I think what you’re describing is exactly what’s happening.

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