ao_cachechecker – too many?

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

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.

@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.

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

Thanks. I’ll give it a try.

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

–George

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

Same here – works, thank you

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

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

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