“Deadlock found” “for query UPDATE {prefix}_actionscheduler_actions”

  • Resolved isarisar

    (@isarisar)


    2 years, 7 months ago

    Since a week or so (I’d pin it on either the 6.8.2 update) we’ve been intermittently (2-3x a day) seeing this error in debug.log:

    WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE prefix_actionscheduler_actions SET attempts = attempts+1, status='in-progress', last_attempt_gmt = '2022-08-30 08:19:19', last_attempt_local = '2022-08-30 10:19:19' WHERE action_id = 80936 von do_action('wp_ajax_nopriv_as_async_request_queue_runner'), WP_Hook->do_action, WP_Hook->apply_filters, WP_Async_Request->maybe_handle, ActionScheduler_AsyncRequest_QueueRunner->handle, do_action('action_scheduler_run_queue'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_QueueRunner->do_batch, ActionScheduler_Abstract_QueueRunner->process_action, ActionScheduler_DBStore->log_execution

    WC’s Scheduled Actions shows no failures, just action_scheduler/migration_hook as created & cancelled on 08-16.

    Annoyingly this is neither reproducible nor has it ever occurred on our identical dev system, and disabling plugins on our shop’s production one is not an option.

    More annoyingly, I don’t see other recent reports of this issue.

    Is there any way to add/get more debug info? For me the error message contains no info to even start searching.

    (Also: Is there a non-public way to share the WC status report with you?)

    WC 6.8.2
    Divi 4.18.0
    WP 6.0.1
    PHP 8.1

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter isarisar

    (@isarisar)

    grep‘ing for the SQL query, other than WC there are two plugins containing the same code:

    • WP Rocket 3.12.0.4
    • WPForms Lite 1.7.6
    Thread Starter isarisar

    (@isarisar)

    Happened 6 times in less than 40 minutes now.

    For now I’ve shuffled the SET parameters (while retaining the placeholder order, ofc) in the hopes of at least getting to know whether it’s a bug particular to one of the three plugins.

    edit: It’s with Woocommerce itself. Though I guess the other two don’t actually run their own ActionScheduler anyway if WC is running.

    • This reply was modified 2 years, 7 months ago by isarisar.
    • This reply was modified 2 years, 7 months ago by isarisar.
    Mirko P.

    (@rainfallnixfig)

    Hi @isarisar,

    Thanks for reaching out.

    WordPress database error Deadlock found when trying to get lock

    This means there’s an application that has locked the database table because it didn’t finish updating a record. Deadlocks happen mostly when an application tries to write more than one record at the same time to the database.

    If this happens consistently, you would need to try to debug and find out which tool, probably a plugin or theme, is locking the table.

    I’d start by creating a staging site and running a conflict test by following our guide here: https://docs.woocommerce.com/document/how-to-test-for-conflicts/.

    Please let us know how that goes.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘“Deadlock found” “for query UPDATE {prefix}_actionscheduler_actions”’ is closed to new replies.