jetpack_sync_cron failed to run

Hi

I have uninstalled Jetpack and reinstalled it again. Same problem.

I also notice the sharing buttons now no longer appear at the bottom of each blog even though they are properly configured.

I forgot to include my site URL :

• https://www.weatherdiary.uk

Bruce.

Hi @xmetman

The issue is likely being caused by how Jetpack uses the WordPress cron system. Can you reach out to your host to have them check to see if cron is enabled and working correctly on your site?

Could you also check your site’s wp-config.php file, and let me know if cron is currently disabled? If it is disabled, you’ll see this bit of code somewhere in that file:

define( 'DISABLE_WP_CRON', true );

Please remove this if it’s present.

Another thing you might try is installing this plugin:

https://www.ads-software.com/plugins/wp-crontrol/

… which should let you see if there’s anything wrong with your site’s cron system.

Hi

Thanks for your help.

My Host says the CRON is enabled and working.

They also say that the config does not contain the disable command.

I’ve installed wp-control and that’s reporting very long times on some of the cron kobs it runs:-

wp_cache_gc
Edit | Run Now | Delete
None	2022-11-24 11:08:55
now	wp_cache_gc_cron()	Non-repeating
Select this row	jetpack_sync_full_cron

None	2022-11-24 11:10:09
now	Automattic\Jetpack\Sync\Actions::do_cron_full_sync()	Every 5 minutes
Select this row	jetpack_sync_cron

None	2022-11-24 11:10:12
now	Automattic\Jetpack\Sync\Actions::do_cron_sync()	Every 5 minutes
Select this row	jetpack_scan_refresh_states_event

None	2022-11-24 11:13:53
now	Automattic\Jetpack\Scan\Admin_Sidebar_Link->refresh_state_cache()	Non-repeating
This is a WordPress core event and cannot be deleted	wp_privacy_delete_old_export_files

None	2022-11-24 11:35:49
21 minutes 55 seconds	wp_privacy_delete_old_export_files()	Once Hourly
Select this row	jetpack_clean_nonces

None	2022-11-24 11:40:35
26 minutes 41 seconds	Automattic\Jetpack\Connection\Nonce_Handler::clean_scheduled()	Once Hourly
This is a WordPress core event and cannot be deleted	wp_site_health_scheduled_check

None	2022-11-24 14:35:47
3 hours 21 minutes	WP_Site_Health->wp_cron_scheduled_check()	Once Weekly
This is a WordPress core event and cannot be deleted	recovery_mode_clean_expired_keys

None	2022-11-24 14:35:47
3 hours 21 minutes	WP_Recovery_Mode->clean_expired_keys()	Once Daily
This is a WordPress core event and cannot be deleted	wp_version_check

None	2022-11-24 14:35:47
3 hours 21 minutes	wp_version_check()	Twice Daily
This is a WordPress core event and cannot be deleted	wp_update_plugins

None	2022-11-24 14:35:47
3 hours 21 minutes	wp_update_plugins()	Twice Daily
This is a WordPress core event and cannot be deleted	wp_update_themes

None	2022-11-24 14:35:47
3 hours 21 minutes	wp_update_themes()	Twice Daily
This is a WordPress core event and cannot be deleted	wp_https_detection

None	2022-11-24 14:35:49
3 hours 21 minutes	wp_update_https_detection_errors()	Twice Daily
This is a WordPress core event and cannot be deleted	wp_scheduled_delete

None	2022-11-24 14:37:12
3 hours 23 minutes	wp_scheduled_delete()
Grunion_Contact_Form_Plugin->daily_akismet_meta_cleanup()	Once Daily
This is a WordPress core event and cannot be deleted	delete_expired_transients

None	2022-11-24 14:37:12
3 hours 23 minutes	delete_expired_transients()	Once Daily
This is a WordPress core event and cannot be deleted	wp_update_user_counts

None	2022-11-24 14:37:12
3 hours 23 minutes	wp_schedule_update_user_counts()	Twice Daily
This is a WordPress core event and cannot be deleted	wp_scheduled_auto_draft_delete

None	2022-11-24 14:37:13
3 hours 23 minutes	wp_delete_auto_drafts()

Bruce.

Hi @xmetman

I’ve just now made a small change and started a full sync of your site again to see if it helps things.

It may take a few hours for the sync to complete.

Hi

Thanks for trying that but I’m afraid it hasn’t fixed the problem!

“One or more (5) cron events missed their schedule”

Bruce.

Hi @xmetman

At this point, I’d like to run some more tests with you on your site to try to figure out what’s happening.

Could you contact us via this contact form and mention this thread?

Seeing this also…something in the 6.x code base isn’t right, because I never saw these errors and warning about caching before. No one wants to see errors on their site health page they can’t resolve or understand. I know cron is working fine on my site (I self-host and many other jobs that use cron work fine). Not sure how wp-cron works or how it interacts with system cron.

Hi Paul

I installed it because the people that host my WP site said that my processes were maxing out. I think their threshold for what I pay is 75%. I contacted a forum and they said it would be a good idea to install wp-cron and then I saw load of amber ! events. My site is slow to save changes that I make to a list in the sidebar, it gets slower the more I add, and get take a couple of minutes to come back and say it’s saved. Changes to my Astra theme in contrast are fine though.

All I can think is that there is a lot of processing being wasted trying to run these cron jobs.

I have had to relent and install Jetpack.
A message to say I’ve posted a new blog to any subscribers still takes days though as it did before.

By the way I have only one subscriber – me.

Latest stat show my site is getting a handful of views a day.

My other two sites are fine.

I’ve never had a WP misbehave like this one does.

Bruce.

As I say outwardly to me the site seems fast.

Perhaps it’s the the 75% resource throttling by my host that’s causing cron jobs to fail?
Surely they wouldn’t put that much load on the servers processor if they didn’t run concurrently?

My server is very lightly loaded and the wordpress stack (php-fpm, mariadb, nginx) is the main thing it runs. Something happened in this latest release that’s not right and I wonder why it’s taking so long to find it/figure it out. I have been seeing a lot of these errors:

[02-Dec-2022 20:49:28] WARNING: [pool www] child 9811, script '/usr/local/www/wordpress/index.php' (request: "GET /wordpress/index.php") executing too slow (10.738534 sec), logging
[02-Dec-2022 23:27:20] WARNING: [pool www] child 10035, script '/usr/local/www/wordpress/index.php' (request: "GET /wordpress/index.php") executing too slow (10.893408 sec), logging

Adding caching seems to have helped but I never needed that before. Not sure why I need to now add a redis process for a low traffic site just to get pages to load.

Howdy @paul,

If you’re still having trouble with this, could you please start your own thread, as per the Forum Welcome?

If you have a paid plan with us, you can reach out via our Contact Form.

Thank you!

Also, @xmetman – since we’re working with you on this via email now, I’m going to go ahead and mark this thread as resolved. ??