LiteSpeed 6.3 update – Action Scheduler, commands out of sync

  • Resolved grevillea859

    (@grevillea859)


    4 months ago

    Hello LS Support,

    Following updating to LiteSpeed Cache version 6.3 today I saw the following in the PHP error log:

    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 = ‘action_scheduler_lock_async-request-runner’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_Lock->is_locked, ActionScheduler_OptionLock->get_expiration, ActionScheduler_OptionLock->get_existing_lock

    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 = ‘action_scheduler_lock_async-request-runner’ made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set, ActionScheduler_OptionLock->get_existing_lock

    WordPress database error Commands out of sync; you can’t run this command now for query INSERT INTO wp_options (option_name, option_value, autoload) VALUES (‘action_scheduler_lock_async-request-runner’, ‘669ed78cb38156.04979945|1721685960’, ‘no’) made by shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set

    I don’t what these entries mean – what causes the commands to be ‘out of sync’ and not so not work?

    I am on a LiteSpeed shared server, use a small amount of my 4GB physical memory, all plugins and themes are up to date, Site Health reports “Great job, everything is running smoothly”.

    I have setup cron jobs in cPanel (disabled wp cron) to run half-hourly. There are often some overdue cron jobs. In the overdue crons today I note the following: action_scheduler_run_queue; litespeed_task_imgoptm_pull and litespeed_task_lqip.

    Are these overdue crons the cause of the above PHP errors? Does this mis-timing affect the Plugin’s performance? When the crons eventually run will that fix the above errors and I don’t need to do anything?

    I am confused and would greatly appreciate any help. Thank you in advance for your time.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support qtwrk

    (@qtwrk)

    no , I don’t know where these out of sync error come from , but I am firmly sure it wasn’t caused by our plugin , you can find a lot of reports like that on the internet even without using our plugin

    I once saw a discussion somewhere about this out of sync error , which some people belive it was caused by bot crawling , as some bot may close connection before page returns , and if connection is closed, the PHP process may also be aborted and killed , that leave to some unfinished command

    and no , I don’t think cron overdue will create error like that.

    Oleksandr

    (@track77)

    Try to check Database summaries (find this option on the Lite Speed Settings)
    Autoload Size should be less than 2 MB
    I don’t receive this messages after I decreased this to 500K,
    Database Summary
    Autoload size:?531.21K
    Autoload entries:?1937

    Thread Starter grevillea859

    (@grevillea859)

    Thank you for your prompt replies and reassuring not from your plugin and not from overdue cron jobs. Yes I have also seen reports of various commands out of sync errors (but different to those above) while searching for possible solutions. Everything seems to be working alright otherwise.

    Thank you for raising the options table issue. The LS Database Summary shows my Autoload size is 314.78K with 753 Autoload entries, which was the case before the above errors occurred. Recently I reduced the size and number of entries following a warning in SiteHealth. But still got the Commands out of sync errors anyway.

    Thank you both for your time. I will close the ticket for the time being until further information sheds light on the problem.

    I have the same issues and i think it’s because the “Persistent Connection” option is activated and the php option “memcached.sess_persistent” is not activated. In your documentation it says:

    To ensure consistent results, be sure that the value of this setting matches that of memcached.sess_persistent in PHP ini. If one of these settings is disabled while the other is enabled, it can result in intermittent connection test failures.

    Can you please add a warning when the 2 options are not the same ?

    Thanks,

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