Cron unschedule event error for hook:

  • Resolved XyZed

    (@xyzed)


    2 years ago

    Hi, I’ve seen a few similar reports before, but none specifically mentioning _start_scheduled_scan. I’m getting the following php_error every day for the last 7 days –

    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

    The error is repeating each day at exactly 9:00 pm, and has only recently started. However, I can see Wordfence did a successful scan last night at 9:00 pm, but there is still an error logged.

    I have cron job set up on server and changed to PHP 7.4.33 last week as I was getting errors elswhere on php 8*

    • This topic was modified 2 years ago by XyZed.
    • This topic was modified 2 years ago by XyZed.
Viewing 3 replies - 1 through 3 (of 3 total)
  • wfjoshc

    (@wfjoshc)

    Hi @xyzed ,

    Thanks for reaching out!

    While you may have downgraded back to 7.4.33, the actual php version running on your site may still be set to 8

    Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. Then export the txt and attach it in the email. Also, can you please attach your php.ini file as well?


    Please be sure to add your forum username so I can take a look.

    Once you do so please reach back out here!
    Thanks,

    Joshua

    Thread Starter XyZed

    (@xyzed)

    Hi Joshua. Thank you for your reply. My site health page reports that my site is using PHP version 7.4.33. Also, the multitude of errors that I was getting from my theme when on version 8* have ceased. So it’s pretty safe to assume PHP version 7.4.33 is running okay.

    I decided to change the Wordfence scan settings from the default, “let Wordfence decide the best time”, to manual. I set it to 1 scan per day (which I assume is all that is needed?) And moved the time from 1 AM to 2 AM.

    This morning I checked the error logs and there were no further additions. I will monitor it over the next couple of days, but it does appear as if for some reason something was happening at 1 AM that interfered with the scan. Albeit that the scan appeared to complete very quickly afterwards anyway. However, I do not like entries in my PHP error log and would prefer no errors at all.

    I’ll report back if anything changes, but for now it does appear that if I have solved the problem.

    wfjoshc

    (@wfjoshc)

    Hi @xyzed

    Glad to hear!

    Let us know if you need anything else and I will be happy to help

    Thanks,

    Josh

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cron unschedule event error for hook:’ is closed to new replies.