Jetpack Sync - Options Table Overload - jetpack_callables_sync_checksum

[rickalee]

The option_name jetpack_callables_sync_checksum is adding a row to wp_options every minute with same values.

Running Multisite WordPress 4.8.3 Jetpack 5.4

XMLRPC blocked but Automattic IPs whitelisted.

[jeherve]

Could you tell us more about your site setup? Do you use something custom to handle Cron on your site?

[GreenLondon]

I face exactly the same issue. I had to remove 80000+ row which clogged the wp_options table on my site and in turn increasing the resources mysql needs in order to execute a query.

Wordpress 4.9.1 Jetpack 5.6.1 I use a cron job to handle the wp-cron.php every five minutes.

@jeherve do you need any other details?

[jeherve]

I use a cron job to handle the wp-cron.php every five minutes.

Could you tell me more about how you set that up?

[GreenLondon]

using bash and the crontab command I added the following

`/5 * /usr/bin/wget --spider "http://example.com/wp-cron.php"

`

[jeherve]

Did you also deactivate the Cron module in WordPress, with the 2 constants mentioned here? https://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron

[GreenLondon]

Apparently not. I cleaned the wp_options and I will report back to you if any multiple records are found

[jeherve]

@GreenLondon How do things look like now on your end?

[anonymopt]

i have a large website and checked for this and had (96545 total, Query took 0.0044 seconds.) just WoW

[GreenLondon]

@jeherve Sorry for the late reply. I was out of the office.

Just checked and I found 13812 entries in my options table. So it seems that the two declarations in wp-config didn't help.

[jeherve]

@anonymopt @GreenLondon If you're willing to run more tests with us, could you contact us via this contact form and mention this issue? We'll dig into this with you to try to understand why the cleanup does not work on your sites.

Thanks!

[bengreeley]

I'm also experiencing this issue @jeherve . The site is a multisite network and one of the sites' options tables was filed with jpsq_ records to the point that the options admin screen no longer renders. WP 4.9.1, Jetpack 5.5

Not all of the sites have this issue - it's just specific to the one site.

[jeherve]

Also in 883270-zen

[GreenLondon]

Hi @jeherve sorry for the late reply. I just created a support request on the form you have sent us.

[georgestephanis]

Seems like an @Automattic/poseidon issue re: Sync maybe?

[lezama]

It would be great to have access to a site experiencing this 🥇 so we could debug what's going wrong.

[ParitoshBh]

Any updates on this and/or possible temporary solution? I am experiencing a similar issue wherein the jpsq_ records have flooded the options table. The table size for me is whopping 495 MB (and growing)! Any help will be appreciated, its killing my linode server :(

[jeherve]

@ParitoshBh Could you contact us via this contact form? If you're willing to give us access to your site so we can run some tests, it would be great!

[ParitoshBh]

@jeherve Done. Unfortunately, I will not be able to give access to the dashboard but can certainly help with troubleshooting.

[enejb]

@jeherve What do we have any additional info here? I am leaving this open since I would love to get to the bottom of this.

[jeherve]

@enejb I think this can be closed until we receive more details about this.

[htdat]

Another case 1549128-zen

[annezazu]

@enejb re-opening this in light of 1549128-zen We have access to help troubleshoot this more listed in the ticket. Let me know if you have any issues.

[lezama]

WordPress from 10 years ago used to not have the constraint for option_name on wp_options to be unique https://codex.wordpress.org/Database_Description#Table:_wp_options.

We are adding a check in https://github.com/Automattic/jetpack/pull/12011 to avoid multiple inserts of jetpack_callables_sync_checksum but we would recommend that these sites fix their db schemas.