• Resolved hoodvisions

    (@hoodvisions)


    Hi there,

    so I crawled the internet and tons of threads here that deal with the similar issue, but to no avail. I am running the latest (7.2.2) version of Woocommerce at one.com and for some reason my database – or rather the table www_actionscheduler_logs – fills with GigaBytes (!) of logs within a day. One.com claims this is an issue with WooCommerce and not with them. They don’t allow any time limit settings, by the way.

    I see there’s two past-due actions constantly that do not get shown in the scheduled actions overview…

    Also I constantly see “Action Scheduler migration in progress. The list of scheduled actions may be incomplete.”

    And if not enough I get this fatal error in the logs (truncated the absolute path to the website):

    2022-12-22T15:40:12+00:00 CRITICAL Uncaught RuntimeException: Unable to claim actions. Database error. in /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:683
    Stack trace:
    #0 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php(597): ActionScheduler_DBStore->claim_actions(40227417, 25, NULL, Array, '')
    #1 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(221): ActionScheduler_DBStore->stake_claim(25, NULL, Array, '')
    #2 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(153): ActionScheduler_HybridStore->stake_claim(25)
    #3 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(25, 'Async Request')
    #4 /wp-includes/class-wp-hook.php(308): ActionScheduler_QueueRunner->run('Async Request')
    #5 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
    #6 /wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #7 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_AsyncRequest_QueueRunner.php(52): do_action('action_schedule...', 'Async Request')
    #8 /wp-content/plugins/woocommerce/includes/libraries/wp-async-request.php(147): ActionScheduler_AsyncRequest_QueueRunner->handle()
    #9 /wp-includes/class-wp-hook.php(308): WP_Async_Request->maybe_handle('')
    #10 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
    #11 /wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #12 /wp-admin/admin-ajax.php(188): do_action('wp_ajax_as_asyn...')
    #13 {main}
      thrown in /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 683
    

    There’s even more errors all related to

    ActionScheduler

    The only way to stop filling the database with thousands of errors right now is to deactivate Woocommerce entirely. I also uninstalled WC completely (via wp-config.php) and reinstalled it fresh. No change.

    Here’s the WC report:

    WordPress Environment
    
    WordPress address (URL): 
    Site address (URL): 
    WC Version: 7.2.2
    REST API Version: ? 7.2.2
    WC Blocks Version: ? 8.9.2
    Action Scheduler Version: ? 3.5.3
    Log Directory Writable: ?
    WP Version: 6.1.1
    WP Multisite: –
    WP Memory Limit: 205 MB
    WP Debug Mode: –
    WP Cron: ?
    Language: de_DE
    External object cache: –
    
    Server Environment
    
    Server Info: Apache
    PHP Version: 8.0.26
    PHP Post Max Size: 256 MB
    PHP Time Limit: 300
    PHP Max Input Vars: 5000
    cURL Version: 7.68.0
    OpenSSL/1.1.1f
    
    SUHOSIN Installed: –
    MySQL Version: 10.3.36-MariaDB-1:10.3.36+maria~ubu2004
    Max Upload Size: 256 MB
    Default Timezone is UTC: ?
    fsockopen/cURL: ?
    SoapClient: ?
    DOMDocument: ?
    GZip: ?
    Multibyte String: ?
    Remote Post: ?
    Remote Get: ?
    
    Database
    
    WC Database Version: 7.2.2
    WC Database Prefix: www_
    Datenbank-Gesamtgr??e: 182.63MB
    Datenbank-Datengr??e: 160.35MB
    Datenbank-Indexgr??e: 22.28MB
    www_woocommerce_sessions: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_woocommerce_api_keys: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_woocommerce_attribute_taxonomies: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_woocommerce_downloadable_product_permissions: Daten: 0.02MB + Index: 0.06MB + Engine InnoDB
    www_woocommerce_order_items: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_woocommerce_order_itemmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_woocommerce_tax_rates: Daten: 0.02MB + Index: 0.06MB + Engine InnoDB
    www_woocommerce_tax_rate_locations: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_woocommerce_shipping_zones: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_woocommerce_shipping_zone_locations: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_woocommerce_shipping_zone_methods: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_woocommerce_payment_tokens: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_woocommerce_payment_tokenmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_woocommerce_log: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    sp_commentmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    sp_comments: Daten: 0.02MB + Index: 0.08MB + Engine InnoDB
    sp_links: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    sp_options: Daten: 1.50MB + Index: 0.03MB + Engine InnoDB
    sp_postmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    sp_posts: Daten: 0.02MB + Index: 0.06MB + Engine InnoDB
    sp_termmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    sp_terms: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    sp_term_relationships: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    sp_term_taxonomy: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    sp_usermeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    sp_users: Daten: 0.02MB + Index: 0.05MB + Engine InnoDB
    www_actionscheduler_actions: Daten: 0.02MB + Index: 0.11MB + Engine InnoDB
    www_actionscheduler_claims: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_actionscheduler_groups: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_actionscheduler_logs: Daten: 54.59MB + Index: 16.03MB + Engine InnoDB
    www_borlabs_cookie_consent_log: Daten: 0.13MB + Index: 0.02MB + Engine InnoDB
    www_borlabs_cookie_content_blocker: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_borlabs_cookie_cookies: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_borlabs_cookie_groups: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_borlabs_cookie_script_blocker: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_borlabs_cookie_statistics: Daten: 0.08MB + Index: 0.13MB + Engine InnoDB
    www_commentmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_comments: Daten: 0.02MB + Index: 0.09MB + Engine InnoDB
    www_e_events: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_e_notes: Daten: 0.02MB + Index: 0.17MB + Engine InnoDB
    www_e_notes_users_relations: Daten: 0.02MB + Index: 0.05MB + Engine InnoDB
    www_e_submissions: Daten: 0.02MB + Index: 0.27MB + Engine InnoDB
    www_e_submissions_actions_log: Daten: 0.02MB + Index: 0.11MB + Engine InnoDB
    www_e_submissions_values: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_links: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_options: Daten: 4.31MB + Index: 0.08MB + Engine InnoDB
    www_postmeta: Daten: 45.38MB + Index: 1.78MB + Engine InnoDB
    www_posts: Daten: 31.36MB + Index: 0.33MB + Engine InnoDB
    www_revslider_css: Daten: 0.13MB + Index: 0.02MB + Engine InnoDB
    www_revslider_css_bkp: Daten: 0.05MB + Index: 0.02MB + Engine InnoDB
    www_revslider_layer_animations: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_revslider_layer_animations_bkp: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_revslider_navigations: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_revslider_navigations_bkp: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_revslider_sliders: Daten: 0.05MB + Index: 0.02MB + Engine InnoDB
    www_revslider_sliders_bkp: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_revslider_slides: Daten: 0.08MB + Index: 0.02MB + Engine InnoDB
    www_revslider_slides_bkp: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_revslider_static_slides: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_revslider_static_slides_bkp: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_termmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_terms: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_term_relationships: Daten: 0.05MB + Index: 0.02MB + Engine InnoDB
    www_term_taxonomy: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_tm_taskmeta: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_tm_tasks: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_usermeta: Daten: 0.05MB + Index: 0.03MB + Engine InnoDB
    www_users: Daten: 0.02MB + Index: 0.05MB + Engine InnoDB
    www_wc_admin_notes: Daten: 0.05MB + Index: 0.00MB + Engine InnoDB
    www_wc_admin_note_actions: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wc_category_lookup: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wc_customer_lookup: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_wc_download_log: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_wc_order_coupon_lookup: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_wc_order_product_lookup: Daten: 0.02MB + Index: 0.06MB + Engine InnoDB
    www_wc_order_stats: Daten: 0.02MB + Index: 0.05MB + Engine InnoDB
    www_wc_order_tax_lookup: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_wc_product_attributes_lookup: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wc_product_download_directories: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wc_product_meta_lookup: Daten: 0.02MB + Index: 0.09MB + Engine InnoDB
    www_wc_rate_limits: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wc_reserved_stock: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wc_tax_rate_classes: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wc_webhooks: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wf301_404_logs: Daten: 1.52MB + Index: 0.00MB + Engine InnoDB
    www_wf301_linkhero: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wf301_redirect_logs: Daten: 0.08MB + Index: 0.00MB + Engine InnoDB
    www_wf301_redirect_rules: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wfblockediplog: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wfblocks7: Daten: 0.02MB + Index: 0.05MB + Engine InnoDB
    www_wfconfig: Daten: 0.47MB + Index: 0.00MB + Engine InnoDB
    www_wfcrawlers: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wffilechanges: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wffilemods: Daten: 10.52MB + Index: 0.00MB + Engine InnoDB
    www_wfhits: Daten: 1.50MB + Index: 0.19MB + Engine InnoDB
    www_wfhoover: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wfissues: Daten: 0.02MB + Index: 0.06MB + Engine InnoDB
    www_wfknownfilelist: Daten: 4.52MB + Index: 0.00MB + Engine InnoDB
    www_wflivetraffichuman: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wflocs: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wflogins: Daten: 0.19MB + Index: 0.06MB + Engine InnoDB
    www_wfls_2fa_secrets: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_wfls_settings: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wfnotifications: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wfpendingissues: Daten: 0.02MB + Index: 0.06MB + Engine InnoDB
    www_wfreversecache: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wfsnipcache: Daten: 0.02MB + Index: 0.05MB + Engine InnoDB
    www_wfstatus: Daten: 0.13MB + Index: 0.11MB + Engine InnoDB
    www_wftrafficrates: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_wpstg_queue: Daten: 0.02MB + Index: 0.00MB + Engine InnoDB
    www_yoast_indexable: Daten: 1.50MB + Index: 0.34MB + Engine InnoDB
    www_yoast_indexable_hierarchy: Daten: 0.06MB + Index: 0.05MB + Engine InnoDB
    www_yoast_migrations: Daten: 0.02MB + Index: 0.02MB + Engine InnoDB
    www_yoast_primary_term: Daten: 0.02MB + Index: 0.03MB + Engine InnoDB
    www_yoast_seo_links: Daten: 0.25MB + Index: 0.13MB + Engine InnoDB
    
    Post Type Counts
    
    attachment: 586
    client: 12
    customize_changeset: 1
    elementor_library: 17
    nav_menu_item: 91
    oembed_cache: 1
    page: 47
    polylang_mo: 2
    post: 79
    revision: 800
    template: 14
    wpcf7_contact_form: 12
    wpplugin_don_button: 1
    wpplugin_don_order: 7
    
    Security
    
    Secure connection (HTTPS): ?
    Hide errors from visitors: ?
    
    Active Plugins (25)
    
    Polylang: von WP SYNTEX – 3.3
    301 Redirects Pro: von WebFactory Ltd – 6.04
    Action Scheduler: von Automattic – 3.5.3
    Borlabs Cookie - Cookie Opt-in: von Borlabs GmbH – 2.2.61
    Add-On: Polylang mit Elementor verbinden: von Creame – 2.3.3
    Contact Form 7 Image Captcha: von KC Computing – 3.3.2
    Contact Form 7: von Takayuki Miyoshi – 5.7.1
    Yoast Duplicate Post: von Enrico Battocchi & Team Yoast – 4.5
    Accept Donations with PayPal: von Scott Paterson – 1.3.4
    Elementor Pro: von Elementor.com – 3.9.2
    Elementor: von Elementor.com – 3.9.2
    OMGF Pro: von Daan from Daan.dev – 3.7.3
    OMGF: von Daan from Daan.dev – 5.5.2
    Loco Translate: von Tim Whitlock – 2.6.3
    one.com Spam Protection: von one.com – 1.0.8
    one.com: von one.com – 4.2.0
    one.com Maintenance Mode: von one.com – 2.1.4
    Performance Cache: von one.com – 3.0.6
    Slider Revolution: von ThemePunch – 6.6.7
    WooCommerce: von Automattic – 7.2.2
    Wordfence Security: von Wordfence – 7.8.2
    WordPress Importer: von wordpressdotorg – 0.8
    Yoast SEO: von Team Yoast – 19.13
    WP Crontrol: von John Blackbourn & Mitwirkende – 1.15.0
    WP STAGING PRO - Backup Duplicator & Migration: von WP-STAGING – 4.4.0
    
    Inactive Plugins (1)
    
    Better Search Replace: von Delicious Brains – 1.4.1
    
    Must Use Plugins (1)
    
    WP STAGING Optimizer: von René Hermenau – 1.5.1
    
    Settings
    
    API Enabled: –
    Force SSL: –
    Currency: EUR (€)
    Currency Position: right_space
    Thousand Separator: .
    Decimal Separator: ,
    Number of Decimals: 2
    Taxonomies: Product Types: external (external)
    grouped (grouped)
    simple (simple)
    variable (variable)
    
    Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
    exclude-from-search (exclude-from-search)
    featured (featured)
    outofstock (outofstock)
    rated-1 (rated-1)
    rated-2 (rated-2)
    rated-3 (rated-3)
    rated-4 (rated-4)
    rated-5 (rated-5)
    
    Connected to WooCommerce.com: –
    Enforce Approved Product Download Directories: ?
    Order datastore: WC_Order_Data_Store_CPT
    
    WC Pages
    
    Shop-Basis: #9651 - /shop/
    Warenkorb: #9652 - /warenkorb/
    Kasse: #9653 - /kasse/
    Mein Konto: #9654 - /mein-konto/
    Allgemeine Gesch?ftsbedingungen: ? Seite nicht festgelegt
    
    Theme
    
    Name: Betheme Child
    Version: 2.0
    Author URL: https://muffingroup.com
    Child Theme: ?
    Parent Theme Name: Betheme
    Parent Theme Version: 26.6.6
    Parent Theme Author URL: https://muffingroup.com/
    WooCommerce Support: ?
    
    Templates
    
    Archive Template: Dein Theme hat eine woocommerce.php-Datei
    was dazu führt
    dass du das Template woocommerce/archive-product.php nicht überschreiben kannst
    da woocommerce.php h?her gewichtet wird als archive-product.php. Das ist beabsichtigt
    um Darstellungsprobleme zu verhindern.
    
    Overrides: betheme/woocommerce/archive-product.php
    betheme/woocommerce/cart/cart-totals.php
    betheme/woocommerce/cart/cart.php
    betheme/woocommerce/cart/cross-sells.php
    betheme/woocommerce/cart/mini-cart.php
    betheme/woocommerce/checkout/form-checkout.php
    betheme/woocommerce/content-product.php
    betheme/woocommerce/content-single-product.php
    betheme/woocommerce/loop/loop-end.php
    betheme/woocommerce/loop/loop-start.php
    betheme/woocommerce/loop/no-products-found.php
    betheme/woocommerce/loop/pagination.php
    betheme/woocommerce/myaccount/downloads.php
    betheme/woocommerce/notices/error.php
    betheme/woocommerce/notices/success.php
    betheme/woocommerce/single-product/add-to-cart/external.php
    betheme/woocommerce/single-product/meta.php
    betheme/woocommerce/single-product/product-image.php
    betheme/woocommerce/single-product/product-thumbnails.php
    betheme/woocommerce/single-product/related.php
    betheme/woocommerce/single-product/sale-flash.php
    betheme/woocommerce/single-product/tabs/description.php
    betheme/woocommerce/single-product/tabs/tabs.php
    betheme/woocommerce/single-product/title.php
    betheme/woocommerce/single-product/up-sells.php
    betheme/woocommerce/single-product-reviews.php
    
    Admin
    
    Enabled Features: activity-panels
    analytics
    coupons
    customer-effort-score-tracks
    experimental-products-task
    experimental-import-products-task
    experimental-fashion-sample-products
    shipping-smart-defaults
    shipping-setting-tour
    homescreen
    marketing
    multichannel-marketing
    mobile-app-banner
    navigation
    onboarding
    onboarding-tasks
    remote-inbox-notifications
    remote-free-extensions
    payment-gateway-suggestions
    shipping-label-banner
    subscriptions
    store-alerts
    transient-notices
    woo-mobile-welcome
    wc-pay-promotion
    wc-pay-welcome-page
    
    Disabled Features: minified-js
    new-product-management-experience
    settings
    
    Daily Cron: ? Next scheduled: 2022-12-23 16:55:14 +01:00
    Options: ?
    Notes: 37
    Onboarding: completed
    `
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Barry

    (@barryhughes-1)

    Hi @hoodvisions,

    I’m sorry to hear you are experiencing difficulties.

    I think the origin of this problem may have been in our 7.2.1 release and, possibly, the reason you are still seeing issues and Action Scheduler-related failings when running 7.2.2 relates to the initial avalanche of scheduled actions that happened in that earlier release.

    Quick caveat/warning … my reply here is specifically for @hoodvisions. For anyone else, of course, feel free to follow along—but no one should follow the steps here unless they feel comfortable doing so, and if you encounter further problems you should definitely create a fresh thread of your own.

    I think it is worth running a couple of separate database queries. There are various ways to do this. For example, you noted that you host your website with one.com, and they provide access to a tool called phpMyAdmin.

    In the following snippets, I assume a database table prefix of www_ … that’s just based on what I see in the System Status Report you posted. If it has changed, or if you need to apply the same fix to other sites, update it as needed.

    This first query changes WooCommerce’s own record of the current database version. We’re going to change this first, to try and head off the possibility of fresh update actions being scheduled:

    UPDATE www_options
    SET    option_value = '7.2.2'
    WHERE  option_name IN (
        'woocommerce_version',
        'woocommerce_db_version'
    )

    This second query should help to clean-up the Action Scheduler tables:

    DELETE actions,
           action_logs
    
    FROM www_actionscheduler_actions AS actions
    JOIN www_actionscheduler_logs AS action_logs
         ON actions.action_id = action_logs.action_id
    
    WHERE actions.hook = 'woocommerce_run_update_callback'
          AND actions.status <> 'pending'

    Probably, you will have the greatest chance of success if you first deactivate WooCommerce before running the above queries then reactivate afterwards. If that’s unpalatable, you could try with WooCommerce active first and only if there continue to be difficulties you could deactivate it.

    Also I constantly see “Action Scheduler migration in progress. The list of scheduled actions may be incomplete.”

    If we can solve the core problem, via the above steps, this should clean itself up given some time.

    Action Scheduler migrations are actually triggered each time you deactivate a plugin, and of course you tried deactivating WooCommerce already. So it’s not unexpected that this notice has appeared, and the reason it is not going away is probably because there are an unusual number of scheduled actions in the queue—and so the migration task is not actually being executed.

    Last but not least:

    • Using database queries comes with some risk. Please, do take the time to make a backup of your site before trying this.
    • Backups are useless if you do not know how to restore them, so be sure to familiarize yourself with that process, too!

    I hope this helps, and we will monitor for further replies.

    • This reply was modified 2 years, 3 months ago by Barry. Reason: Remove stray img tag inserted by block editor
    Thread Starter hoodvisions

    (@hoodvisions)

    Thanks so much for your help! I tried both SQL commands, but unfortunately it didn’t help. The version numbers seem to be set already in the www_options table.

    Right now I regularly truncate the actionscheduler_logs via

    TRUNCATE www_actionscheduler_logs

    By the way, said logs are exclusively filled with (action_id 64)

    There was a failure fetching this action: Action [64] has invalid arguments. It cannot be JSON decoded to an array. $args = array (
    )

    and (action_id 58)

    action ignored via WP Cron

    I am quite certain this has something to do with the cronjobs not working properly on one.com or some restrictions, but I have no clue how approach this. Their support claims it’s not their “fault” and there’s no way to adjust any of the server settings, but moving to another provider is currently not an option for us either.

    Plugin Contributor Vedanshu – a11n

    (@vedjain)

    I see. Thanks for this extra context. This does not looks related to the recent update, and is possibly something else. It seems like there is an issue in the arguments where the action was scheduled.

    Can you post what hooks are actions attached to?

    If you are comfortable with PHP and running custom code, then for both these actions, perhaps you would be able to run them manually by executing do_action_ref_array( 'name_of_the_action_hook', array_values( 'args' ) );

    Caveat -> Below section is likely only relevant for specific case faced by @hoodvisions.

    If you can run them after fixing the error in arguments manually, then it would be safe to delete the actions so that you won’t have to truncate the table periodically. Alternatively, if you are confident that those actions are not important, or can be enqueued again, then you can delete them too (because they are not being processed anyway). <- But do this only if you are confident with PHP and WordPress/WooCommerce.

    Thread Starter hoodvisions

    (@hoodvisions)

    Big thanks for the support! Unfortunately I’m not really keen with PHP and I cannot really identify the hooks responsible. It seems, however, it’s all related to some kind of cronjob issue specifically on one.com – I am keeping the logs relatively clean right now with the Action Scheduler – Disable Default Queue Runner plugin. The one.com support isn’t helping and is pointing at a xmlrpc.php issue, though xmlrpc.php is restricted via htaccess and plugin.

    I don’t think this is a WooCommerce related issue, so I guess the thread can be closed. Thanks a lot though ??

    Hi @hoodvisions

    I don’t think this is a WooCommerce related issue, so I guess the thread can be closed. Thanks a lot though

    We totally understand.

    I will be marking this thread as resolved. Should you have further inquiries, kindly create a new topic here.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘actionscheduler_logs growing incredibly fast, database getting HUGE’ is closed to new replies.