Fatal error found in log

  • Resolved ArcticFritid

    (@metuza)


    2 years, 7 months ago

    Hello,

    When new orders are registered i can find the below fatal error in my debug-log:

    [04-Aug-2022 07:32:17 UTC] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE wp_actionscheduler_actions SET attempts = attempts+1, status='in-progress', last_attempt_gmt = '2022-08-04 07:32:17', last_attempt_local = '2022-08-04 09:32:17' WHERE action_id = 3389034 made by 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
[04-Aug-2022 07:32:19 UTC] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE wp_actionscheduler_actions SET claim_id=1465506, last_attempt_gmt='2022-08-04 07:32:19', last_attempt_local='2022-08-04 09:32:19' WHERE claim_id = 0 AND scheduled_date_gmt <= '2022-08-04 07:32:19' AND status='pending' ORDER BY attempts ASC, scheduled_date_gmt ASC, action_id ASC LIMIT 10 made by 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_DBStore->stake_claim, ActionScheduler_DBStore->claim_actions
[04-Aug-2022 07:32:19 UTC] PHP Fatal error:  Uncaught RuntimeException: Unable to claim actions. Database error. in /www/XXXXX/public/wp-content/plugins/mailchimp-for-woocommerce/includes/vendor/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:683
Stack trace:
#0 /www/XXXXX/public/wp-content/plugins/mailchimp-for-woocommerce/includes/vendor/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php(597): ActionScheduler_DBStore->claim_actions(1465506, 10, NULL, Array, '')
#1 /www/XXXXX/public/wp-content/plugins/mailchimp-for-woocommerce/includes/vendor/action-scheduler/classes/ActionScheduler_QueueRunner.php(153): ActionScheduler_DBStore->stake_claim(10)
#2 /www/XXXXX/public/wp-content/plugins/mailchimp-for-woocommerce/includes/vendor/action-scheduler/classes/ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(10, 'Async Request')
#3 /www/XXXXX/public/wp-includes/class-wp-hook.php(307): ActionScheduler_QueueRunner->run('Async Request')
#4 /www/ in /www/XXXXX/public/wp-content/plugins/mailchimp-for-woocommerce/includes/vendor/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 683

    Brgds

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

    (@khungate)

    Hi @metuza, sorry to hear you’re having issues with the plugin, we definitely want to try to help out. Just to get a handle on the situation you’re experiencing, could you provide a few more pieces of information to help us understand the issue?

    – What plugin version are you using?
    – What version of PHP are you using?
    – Are there any fatal errors in WooCommerce? (Log into your store admin area, click WooCommerce -> Status -> Logs)
    – If you have a large number of plugins being used, you may need to bump up your memory limit on your server (1GB for example) to accommodate the initial sync.
    – If you haven’t already, please browse through our Wiki to find documentation on the most common issues and how to resolve them: ?https://github.com/mailchimp/mc-woocommerce/wiki.

    Thanks in advance for these details. I’ll keep an eye out for your reply.

    Plugin Support khungate

    (@khungate)

    Hi @metuza, we just wanted to check back with you to see if this was still a problem with our latest plugin (v2.7.2 at the time of this post). Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

    Thread Starter ArcticFritid

    (@metuza)

    Hello,

    Sorry for the delay. The fatal error i have not seen again. The deadlock error is still there when i deactivate Mailchimp plugin so i have to dig deeper into that issue.

    [19-Aug-2022 17:47:04 UTC] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE wp_actionscheduler_actions SET attempts = attempts+1, status='in-progress', last_attempt_gmt = '2022-08-19 17:47:04', last_attempt_local = '2022-08-19 19:47:04' WHERE action_id = 3680822 made by 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

    But i noticed that when i deactivate Mailchimp plugin i got rid of all the below notices in which i actually find many of when Mailchimp is active.

    [19-Aug-2022 20:13:16 UTC] post was called incorrectly. Produktegenskaper skal ikke aksesseres direkte. Backtrace: require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array('parse_request'), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, WC_REST_Stock_Sync_Controller->update_item, WC_REST_Stock_Sync_Controller->save_object, WC_Product->save, WC_Data_Store->update, WC_Product_Data_Store_CPT->update, WC_Product_Data_Store_CPT->handle_updated_props, do_action('woocommerce_product_object_updated_props'), WP_Hook->do_action, WP_Hook->apply_filters, MailChimp_Service->handleProcessProductMeta, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Otherwise it seems like everything works ok.

    Brgds
    Rune

    Plugin Author ryanhungate

    (@ryanhungate)

    @metuza The plugin makes use of the “Action Scheduler” which is a queue system for WordPress/WooCommerce and very commonly used with plugins that require many “jobs” to be handled. Your orders being synced require us to “queue up many jobs” in order to get them pushed to Mailchimp.

    The deadlock errors would indicate you should reach out to your web host and consider upgrading your database to handle better throughput. However what you’re experiencing is not ideal, and we will try to consider this in a future release for these types of server setups.

    If you have any other questions about this please feel free to reach back out.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error found in log’ is closed to new replies.