CRON Events 51 years ago

  • Resolved VSOC Webmaster

    (@vsoc-webmaster)


    3 years, 1 month ago

    Hi. I have 5 events that are unable to be run, edited or deleted and are probably due to a deleted plugin or something… Now I have installed your plugin I can see them but cannot do anything with them. There is no Action, no Arguments, they are non-repeating and all have their Next Run set to the current time. Each one has “51 years 8 months ago”. If I refresh the Cron Events page the Next Run time just updates to the current date and time. If I click on Delete or Edit the page just says the link has expired or does not exist.
    Basically I am asking if there is a way to tidy up the 5 cron jobs that must simply be errors in the WP database that I cannot find at the moment.

    Hook 1439930405
    Edit | Run Now | Delete
    None 2021-09-01 16:52:58
    51 years 8 months ago None Non-repeating
    Hook 1439930335
    Edit | Run Now | Delete
    None 2021-09-01 16:52:58
    51 years 8 months ago None Non-repeating
    Hook 1439930353
    Edit | Run Now | Delete
    None 2021-09-01 16:52:58
    51 years 8 months ago None Non-repeating
    Hook 1439930350
    Edit | Run Now | Delete
    None 2021-09-01 16:52:58
    51 years 8 months ago None Non-repeating
    Hook 1439930347
    Edit | Run Now | Delete
    None 2021-09-01 16:52:58
    51 years 8 months ago None Non-repeating`

    Thanks for any help coming.
    Nick

Viewing 3 replies - 1 through 3 (of 3 total)

  • Same issue here. Got it resolved?

    I’m not the plugin author, so this is strictly guesswork, but it looks to me like something somewhere is expecting a date that isn’t set properly. The time/date on UNIX & Linux servers is, at its heart, a count of the seconds that have elapsed since midnight, Jan. 1, 1970. So if a piece of code is expecting a date and getting a null or invalid value, then it’s possible it would decide that the date in question is 1970-01-01 00:00:00.

    (Which is 51 years, 8 months, and some days ago.)

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    If you try to delete one of these events and you get an error message saying the link is no longer valid, that suggests a problem with the object cache (eg. Redis or Memcached) on your site that’s unrelated to WP Crontrol. I would try clearing your object cache and if that doesn’t allow you to delete the events then get in contact with your webmaster or web host.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CRON Events 51 years ago’ is closed to new replies.