wabetainfo

Hi @alinclamba,

Unfortunately, the issue is back:

[24-Jan-2024 16:44:12 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_options WHERE option_name = 'jpsq_sync_checkout' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_sync, Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, Automattic\Jetpack\Sync\Queue->is_locked, Automattic\Jetpack\Sync\Queue->get_checkout_id


[24-Jan-2024 16:44:12 UTC] WordPress database error Commands out of sync; you can't run this command now for querySELECT count() FROM wp_jetpack_sync_queue WHERE queue_id = 'sync' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_sync, Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, Automattic\Jetpack\Sync\Queue->size, Automattic\Jetpack\Sync\Queue\Queue_Storage_Table->get_item_count

[24-Jan-2024 16:44:12 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_options WHERE option_name = 'jetpack_sync_full_status' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_full_sync, Automattic\Jetpack\Sync\Modules\Full_Sync_Immediately->get_status, Jetpack_Options::get_raw_option

[24-Jan-2024 16:44:12 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_options WHERE option_name = 'jpsq_sync_checkout' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_sync, Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, Automattic\Jetpack\Sync\Queue->is_locked, Automattic\Jetpack\Sync\Queue->get_checkout_id

[24-Jan-2024 16:44:12 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT count() FROM wp_jetpack_sync_queue WHERE queue_id = 'sync' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_sync, Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, Automattic\Jetpack\Sync\Queue->size, Automattic\Jetpack\Sync\Queue\Queue_Storage_Table->get_item_count


[24-Jan-2024 16:44:12 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_options WHERE option_name = 'jetpack_sync_full_status' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_full_sync, Automattic\Jetpack\Sync\Modules\Full_Sync_Immediately->get_status, Jetpack_Options::get_raw_option

It seems it is fixed with the recent updates as this error no longer appears in the log file

Hi @ireeps, my website experiences a similar issue since a few days. Have you found a solution?

Done, thanks!

website: https://wabetainfo.com

Hi,

Thank you for your interest. I experienced the timeout issue for each page until I decided to delete those files. I had to delete them manually because I couldn’t deactivate the plugin from the admin panel, as I experienced the timeout there as well.

In the past, I frequently faced timeout issues, some quite significant, which I resolved with the 1.3.7 update and moving the database to a local path and setting the timeout variable.

I completely understand the situation and acknowledge that isolating such a problem can be complicated, but is it possible to explore any workarounds? For instance, when the database is busy with another PHP process, a direct query could be made to the Maria database until the plugin-generated database is available again. This could be an optional feature that users can activate if they encounter similar issues. I understand this might be drastic, but it could potentially resolve these timeout problems. What do you think about? Or can you study any other workarounds, please? Your plugin is very useful and important, I would love to keep using it…

Hi @olliejones,

I’ve been using the plugin for a week, and I haven’t experienced any timeout issues. The new update was really effective. Thank you. In case I experience similar problems in the future, I will open a new discussion here. Thanks again!

Thanks for your message, @olliejones.
I will install the plugin in the next few days to test the new version. I will share feedback with you.
I will also make sure to add these lines to my wp-config.php file:

define('WP_SQLITE_OBJECT_CACHE_DB_FILE', '/var/tmp/.object-cache.sqlite');
define('WP_SQLITE_OBJECT_CACHE_TIMEOUT', 15000);

Since I will add the cache database to the tmp folder, and it seems this folder is not accessible, I believe it would be useful to add the size of the cache database to the plugin settings page.

Thanks @vupdraft. Is there any news regarding a fix for this issue? It’s still happening with the latest update.

@olliejones thank you for your interest in fixing this issue. I will be happy to reinstall the plugin in case you are able to isolate the issue and push a fix in a new release. I think it’s the best plugin that helps improve performance while preserving CPU resources. It was truly unfortunate to have to uninstall it. If you’re interested in some data on how I used the plugin, I had chosen a 40MB cached data size. However, I frequently noticed the cached database size reaching up to 60-62MB.

Thanks for your answer. I appreciate it!

Unfortunately, I won’t be able to provide any feedback since I had to install your plugin. I was experiencing critical interruptions, very similar and worse than the one mentioned in this request, despite not receiving any significant logs in my server. For many days, my website was inaccessible at certain times of the day (usually mostly in the morning), causing continuous timeout errors for several hours. After finding that discussion and reading that someone was facing the same timeout issue, I decided to permanently remove the plugin, and the issue has finally disappeared. In fact, prior to uninstalling the plugin, my website was consistently inaccessible for several hours each day. After removing the plugin, I no longer experience the issue (for 4 days now).

I really don’t know what the cause could be, but I think the site becomes unreachable when an operation to clean up old data within the database created by the plugin is supposed to occur. I can’t be certain of it, but I haven’t found another explanation that makes sense. I am very sorry because I loved this plugin, and the benefits it provided were very significant for me. However, I cannot allow my website to be unreachable for over 3 hours every day

Hi @nawawijamili

I experience the same issue with the mobile menu plugin. Unfortunately, when attempting to replace “unserialize” with “maybe_unserialize”, I get this error:
Call to undefined function maybe_unserialize().

Hi @pbevanudp,

Pastebin URL: https://pastebin.com/BJU2pagN
Password: wpo

Hi @alinclamba,
Thank you so much for your interest in assisting me. I can confirm that the issue is fixed and I have now 579-day streak. I’d like to provide you with more information about what might have caused the problem, in the hope that it could be of help in similar situations in the future. Even after reinstalling WordPress, I continued to encounter some errors related to the reported issue: https://www.ads-software.com/support/topic/unable-to-use-jetpack-outbound-http-and-wpcom-connection-test

The outbound http issue was fixed after some time when adding some configuration in the wp-config file, but it’s possible that I shared a new post while the issue was ongoing and this may have caused the reset.

Thank you again!

Hi @bruceallen,

Thanks for your interest in helping me. Yes, I’ve fixed my issues by reinstalling WordPress and Jetpack. In addition, I’ve included some changes in my wp-config file:

define('FORCE_SSL_ADMIN', true);
$_SERVER['SERVER_PORT'] = 443;


I’ve followed this guide: https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/

It seems it’s finally fixed. Thanks again!

• This reply was modified 1 year, 5 months ago by wabetainfo.