Datebase errors after update (hpos, LegacyDataCleanup, Commands out of sync)

  • Resolved codings

    (@codings)


    2 months ago

    Hi, since updating WP and WC, the server has exceeded resources (it has plenty of resources available that never come close to being reached) and the site has been throwing a consistent 503 error. Hosting company claims nothing changed on their end.

    Every few minutes, the error logs report:

    "WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM wp_12345_options WHERE option_name = 'woocommerce_hpos_legacy_data_cleanup_in_progress' LIMIT 1 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->__call, call_user_func_array, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->maybe_reset_state, Automattic\WooCommerce\Internal\DataStores\Orders\LegacyDataCleanup->is_flag_set, get_option"

    Tried clearing LiteSpeed cache, server cache, disabling plugins, all of the typical WP troubleshooting.

    Site Health Critical Issues: an active PHP session was detected and the REST API encountered an error.

    Something that seemed to fix it for a few minutes was the instructions here to install the repair Action Scheduler plugin… but after about 15 minutes, the errors started again and access has been restricted to constant 503 and now I’m wondering if that plugin is legit.

Viewing 9 replies - 16 through 24 (of 24 total)
1 2
  • Plugin Support Shameem (woo-hc)

    (@shameemreza)

    1 month, 3 weeks ago

    Hi @codings

    The “Commands out of sync” error is usually related to the MySQL server and not directly caused by WooCommerce. This error generally happens when calling stored procedures that return a result set which is not fully consumed before executing another command.

    The LegacyDataCleanup and WooCommerce Blocks scripts are part of the WooCommerce core and are designed to run in the background to ensure the smooth operation of your store. They shouldn’t be causing your site to go down. If they are, there’s likely a conflict or an issue with your hosting environment.

    As for your Jetpack query, the reference to Jetpack in the error messages is related to the WooCommerce Autoloader, which is a part of the WooCommerce core and not specifically tied to the Jetpack plugin.

    To help resolve these issues, I recommend the following steps:

    1. Contact your hosting provider. They can check for any server-related issues that might be causing the “Commands out of sync” error.
    2. Disable all plugins except WooCommerce. This will help determine if there’s a conflict with another plugin. If the errors stop, you can reactivate your plugins one by one to identify the culprit.
    3. Reinstall WooCommerce. If the issue persists, try reinstalling WooCommerce. This will ensure all files are up-to-date and correctly installed.

    Remember to backup your site before making any changes.

    I hope this helps! Please let us know how it goes or if you need further assistance.

    Thread Starter codings

    (@codings)

    1 month, 2 weeks ago

    I haven’t replied because there is not much to report back and the errors in the log still persist. I did step 1 and 2, but not step 3. As for contacting the host, they had no server-related issues and they directed me to php documentation that explains Commands Out of Sync. Basically they said it’s a WC issue.

    Noticed the WooCommerce plugin update today (9.0.1):

    • Fix – Check WC_Legacy_API instead of WC_API as that seems to be cached by lightspeed servers

    Since my server is a Lightspeed server and I am using the Lightspeed caching plugin (even though I did test with is disabled), maybe this update will resolve the errors.

    Plugin Support omarfpg (woo-hc)

    (@omarfpg)

    1 month, 2 weeks ago

    Hi @codings,

    Since my server is a Lightspeed server and I am using the Lightspeed caching plugin (even though I did test with is disabled), maybe this update will resolve the errors.

    It’s worth giving it a try! You can take a full backup of your site before doing that or try the updates on a staging site to make sure nothing breaks while doing so.
     
    Please let us know how it goes.

    Thanks!
    -OP

    Plugin Support omarfpg (woo-hc)

    (@omarfpg)

    1 month ago

    Hi there 👋 ,

    We haven’t heard from you in a while; this is to check if you’ve been able to proceed with the troubleshooting steps provided before and if you still need help.

    Thanks!
    -OP

    Thread Starter codings

    (@codings)

    1 month ago

    Thanks for checking in! The errors still show, although the site is not throwing 403s anymore after restoring the server to a previous date and updating everything again.

    Shared this thread with the host and they redirected me to PHP documentation related to the “Commands out of sync” error, and basically inferred that it’s a WC issue as nothing changed in the hosting environment.

    Plugin Author Barry

    (@barryhughes-1)

    1 month ago

    I’m not sure what documentation they pointed to, but this is a MySQL error rather than a PHP one … though it is certainly possible it could be triggered by PHP code interacting with the database.

    Unfortunately, though, I cannot replicate this problem. However, some improvements to the relevant system (legacy order cleanup) are shipping in 9.1.0 (our next release, which is expected to land next week, on July 10th).

    Since the worst of the problem has passed, in the sense you are not experiencing 403s, it may be worth pausing and waiting for that update and seeing what it brings.

    Noticed the WooCommerce plugin update today (9.0.1):

    • Fix – Check WC_Legacy_API instead of WC_API as that seems to be cached by lightspeed servers

    As I guess you found, this was unrelated. Actually, the problem was not with LiteSpeed, but rather was an issue some customers experienced when a third-party update utility performed the plugin update.

    Thread Starter codings

    (@codings)

    4 weeks, 1 day ago

    I’m not sure what documentation they pointed to, but this is a MySQL error rather than a PHP one … though it is certainly possible it could be triggered by PHP code interacting with the database.

    @barryhughes-1

    Sorry for the confusion, I meant MySQL. Must have had PHP on my mind 😛

    Thank you for the info about the upcoming update. Looking forward to seeing if that stops the errors. But, yes, as you pointed out, at least reverted the previous update stopped the 403s.

    I appreciate your time on this and thanks to the entire WC team for the work you all do.

    Plugin Support Paulo P – a11n

    (@paulostp)

    3 weeks, 4 days ago

    Hey @codings,

    I’ll go ahead and close this topic for now. Please let us know if the issue persists after the latest update.

    Thanks

    Thread Starter codings

    (@codings)

    2 weeks, 5 days ago

    Will do. Just updated core and plugins. Will see how it goes. Thanks for everyone’s attention on this thread.

Viewing 9 replies - 16 through 24 (of 24 total)
1 2
  • You must be logged in to reply to this topic.