Deleted Cron immediately replaced by exact replicate

  • Resolved markb

    (@markbignell)


    3 years, 12 months ago

    I have a cron created by some code added to my theme’s fucntions.php file. The code has since been deleted, yet the database (options ? cron) is totally bloated with duplicate/redundant Crons (54,000+). I can’t delete them! I have tried emptying the cron table in the database directly — they all regenerate immediately. I have tried this plugin and they all regenerate immediately after deleting them.

    This also applies to 27 crons set up by Monster Insights plugin. I have deleted Monster Insights, removed all DB tables according to their documentation yet still the crons automatically regenerate.

    So frustrating.

    The bigger picture is that these 10s of thousands of Crons are seizing all CPU on the web server and (intermittently) slowing it to a crawl. How can I finally and completely delete these crons? Thanks!

Viewing 1 replies (of 1 total)
  • Thread Starter markb

    (@markbignell)

    Well, I’ve spent hours on this problem and finally I came up with a solution! For anyone else experiencing this issue the fix is relatively straightforward: I cloned the database; renamed it to something unique; uploaded the new DB to the account; emptied the Cron table in the new DB; then and replaced the old db details in wp-config.php with the new DB credentials. Now these rascally crons are no longer regenerating and I have a speedy site with low CPU load on the web server. Problem solved!

Viewing 1 replies (of 1 total)
  • The topic ‘Deleted Cron immediately replaced by exact replicate’ is closed to new replies.