Cron-Reschedule-Event-Fehler

  • Getting this Error:
    [25-Jul-2023 07:54:04 UTC] Cron-Reschedule-Event-Fehler für Hook: wf_scan_monitor, Fehlercode: could_not_set, Fehlermeldung: Die Cron-Ereignisliste konnte nicht gespeichert werden., Daten: {“schedule”:”wf_scan_monitor_interval”,”args”:[],”interval”:60}

    PHP: 8.0.29 / WP 6.2.2
    what to do??

    • This topic was modified 1 year, 4 months ago by treibstoff.
Viewing 4 replies - 1 through 4 (of 4 total)

  • Thanks for reaching out.

    ?I suspect because this messaging has been added in WordPress 6.1.1. It would be prudent to add that this is not a Wordfence specific issue. It can happen with any plugin or theme (see this search for reference). 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 particular cron job mentioned 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. Check to see if subsequent automatic scans are completing. If they are, you can likely ignore this error. If not you may have to set up manual crons. Most hosting companies have specific instructions on how to do this so googling the hosting company name and ‘wordpress manual cron’ will likely get you the instructions to do this.

    Mia

    Thread Starter treibstoff

    (@treibstoff)

    thanx Mia,
    I was expecting something like that. But unsure if I take it serious or not.
    Expecting, ’cause the backend here is working quite slow (in opposite to the frontend), might be caused due to the hosting companie (DomainFactory) or by the wordfence firewall.
    So far it just happend while updating the plug…and no further messages in the log…

    Try checking the PHP memory_limit variable and increasing that if necessary. Anything less than 256M is probably going to be sluggish. If you do increase it make sure that the max_execution_ time variable is set between 30 and 90.

    Mia

    Thread Starter treibstoff

    (@treibstoff)

    thanx Mia, but memory_limit is 256 and max_excecution is set to120.
    so that is quite fine….

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Cron-Reschedule-Event-Fehler’ is closed to new replies.