Thanks for the report.
Could you create a phpinfo file on your site, and contact us through this contact form with a link to this thread as well as a link to the phpinfo file so we can know more about your site’s setup?
Thanks!
Could you also tell me more about that script you’re running, and what it does?
Ultimately, it will be hard to debug without more information. This error either means the server timed out, or the mysql packet is too big. None of this is necessarily tied to Jetpack; it could be because you have a lot of options in that table, or because you have limited resources on that server.
I’d suggest trying the suggestions here to increase wait_timeout and/or max_allowed_packet in your my.cnf config. It could help.
Hi, thanks for your feedback.
Yes there are 1.2M options in the table … what i don’t get is why WordPress is trying to update them all and it’s seems to be triggered by jetpack construct ?
why WordPress is trying to update them all and it’s seems to be triggered by jetpack construct ?
That’s most likely triggered by this function in Jetpack:
https://github.com/Automattic/jetpack/blob/3.7.2/class.jetpack.php#L571
Jetpack uses cron (via wp_schedule_event #) to clean after itself every hour, and delete all old nonces. The SQL query can be found here:
https://github.com/Automattic/jetpack/blob/3.7.2/class.jetpack.php#L5146
Did you make any changes to the way cron is set on your server?
