ib_actionscheduler_logs gigantic size

  • hi there,

    within just 3 days of a 750 product development page without traffic and work on products our table ib_actionscheduler_logs grew to enormous 3gb / 33 mio entries. why and how to stop this?

    plugins:
    classic editor
    crelly slider
    easy image sizes (we only use 4 image sizes)
    font waesome
    force login
    gallery custom links
    germanized for woocommerce
    media library categories
    product slider and carousel
    soliloquy lite
    simple lightbox
    woocommerce
    wp sort order
    wp super cache
    yoast seo

    all plugins and wordpress run on recent version.
    theme is a 2021 copy.

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hi @ffwebdesigner,

    Wow! That’s a huge number of actions. With that kind of growth, I would expect there is some function that’s run amok.

    If you go to WooCommerce > Status > Scheduled Actions are you seeing a huge number of actions here? Look for any “hooks” that are repeated over and over again and copy them and paste them here in your reply. That’ll help us track down the source of the trouble.

    Thanks!

    Thread Starter ffwebdesigner

    (@ffwebdesigner)

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes) in /wp-content/plugins/woocommerce/packages/action-scheduler/functions.php on line 272

    btw…with germanized installed i always got fatal errors after migrating to a different server. unresolvable after reading and trying more than 20 threads. thus, i edited

    /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionSchedulerHybridStore.php line 242

    //return $this->primary_store->save_action( $action, $date );

    this line threw the fatal error. everything looking good with that line commented out. the gigantic size appeared also before i edited that line.

    may i just empty wp_actionscheduler_logs in phpmyadmin?

    Thread Starter ffwebdesigner

    (@ffwebdesigner)

    most lines are

    0″,”212″,”Aktion über Async Request ignoriert”,”2021-02-18 10:51:33″,”2021-02-18 11:51:33

    action over async request ignored.

    i love all in one security which might block async requests. in this case: not. no idea where the blocked async request comes from.

    as like with the enormous variety of woocommerce images sizes (standard 2021 theme 8000 images x 8 sizes = 64000 images) i’d try to reduce server load to the max. which actions do we really need?

    Thread Starter ffwebdesigner

    (@ffwebdesigner)

    table up to 2,7gb after just 5 days again… emptied the table.
    as soon as i take the comment out from /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionSchedulerHybridStore.php line 242
    return $this->primary_store->save_action( $action, $date );
    i get errors again:

    Fatal error: Uncaught RuntimeException: Fehler beim Speichern der Aktion: Fehler beim Speichern der Aktion: Datenbankfehler. in /wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44 Stack trace: #0 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(243): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL) #1 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action)) #2 /wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Action)) #3 /wp-content/plugi in /wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘ib_actionscheduler_logs gigantic size’ is closed to new replies.