ao_cachechecker – too many?

  • Resolved richard

    (@rich_smc)


    5 years, 5 months ago

    Hi there,

    Great plugin, thank you.

    I installed a cron job plugin the other day, i noticed that the schedule looks a bit odd:

    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:40:07 (8 hours 12 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:40:14 (8 hours 12 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:40:46 (8 hours 13 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:41:07 (8 hours 13 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:42:07 (8 hours 14 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:44:07 (8 hours 16 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:46:07 (8 hours 18 minutes) Twice Daily Edit | Run Now | Delete
    ao_cachechecker None

    autoptimizeCacheChecker->cronjob()

    2018-11-28 20:47:07 (8 hours 19 minutes) Twice Daily Edit | Run Now | Delete

    Looks like theres 8, doing the same thing, almost the same time? What should we do – delete 7 perhaps? Or leave it be? Thank you

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    5 years, 5 months ago

    That’s too many indeed. I have seen this on some occasions but have no idea why this would happen so I might add some scheduled-event-cleanup code to the next version of AO. in the mean time feel free to clean up indeed, you just need one twicedaily event 🙂

    frank

    gandrews711

    (@gandrews711)

    5 years, 4 months ago

    It appears your plugin is actually spawning hundreds of cron jobs, filling up MySQL logs, and–potentially–crashing servers. I installed WP-Crontrol and it’s showing some real issues, even with the plugin deactivated, the ao_cachechecker jobs continue to re-spawn.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    5 years, 4 months ago

    @gandrews711 as a workaround: removing the ao_cachechecker job with schedule = daily (there will be one) should stop the spawning (as at that point AO will see the schedule = twicedaily and be satisfied).

    I’m working on a fix, will commit to github soon and then you can test said fix which would be part of AO 2.4.3.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    5 years, 4 months ago

    OK, pushed a commit to github that should remove all but one scheduled ao_cachechecker scheduled jobs. could you download https://github.com/futtta/autoptimize/archive/master.zip, install (deactivate the old version) and test?

    frank

    gandrews711

    (@gandrews711)

    5 years, 4 months ago

    Thanks. I’ll give it a try.

    gandrews711

    (@gandrews711)

    5 years, 4 months ago

    Looks good. Now I just have one ao_cachechecker job according to the cron plugin. Thanks for your quick fix on this!

    –George

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    5 years, 4 months ago

    thanks for the confirmation George! feel free to leave a review of the plugin and support here! 🙂

    Thread Starter richard

    (@rich_smc)

    5 years, 4 months ago

    Same here – works, thank you

    Anon M. Verte

    (@mverte)

    5 years, 4 months ago

    checking why I stopped working my cron jobs, I found that I had 4500 ao_cachechecker, cron jobs but I can not delete them by hand since every time they appear more, I had to uninstall the plugin.

    My question is what query can I run in mysql console to delete these entries, thanks

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    5 years, 4 months ago

    have you upgraded to 2.4.4 @mverte, that should (have) remove(d) those cron jobs?

    if not the alternative could indeed be a SQL query;

    
DELETE FROM wp_options WHERE option_name = 'cron';

    or

    UPDATE wp_options SET option_value = '' WHERE option_name = 'cron';

    Do take into account that all WordPress crons are in one entry, so each plugin will have to re-create it’s scheduled job (which _should_ not be a problem).

    hope this helps,
    frank

    Anon M. Verte

    (@mverte)

    5 years, 4 months ago

    thank you for answering me, I work well, I will try the new version

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘ao_cachechecker – too many?’ is closed to new replies.