Fatal error – Uncaught RuntimeException

  • Resolved N33D

    (@n33d)


    4 years, 5 months ago

    Hi there,

    The plugin causes some troubles (takes it offline) in my site with these errors:

    `Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Duplicate entry ‘0’ for key ‘PRIMARY’ in

    /var/www/nldepop-newfield/wordpress/current/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44

    Stack trace: #0

    /var/www/nldepop-newfield/wordpress/current/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242):

    ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL) #1

    /var/www/nldepop-newfield/wordpress/current/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(177):

    ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action)) #2

    /var/www/nldepop-newfield/wordpress/current/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Action)) #3 /var/w in

    /var/www/nldepop-newfield/wordpress/current/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44

    Any idea?

    Best regards,
    Justin

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Gregor Capuder

    (@capuderg)

    Hi Justin,

    it looks like the Action Scheduler library (that we use in our plugin) can’t save new actions to the database. It looks like there is an issue with IDs for the primary key of the action scheduler DB table.

    Could you please please check in your database and see if you have these 4 DB tables there:

    
wp_actionscheduler_actions
wp_actionscheduler_claims
wp_actionscheduler_groups
wp_actionscheduler_logs

    Note: you might have a different table name prefix than in the example above (wp_).

    If you do, then these tables or at least the wp_actionscheduler_actions table might be corrupted and would need to be repaired.

    Are you maybe also using some other plugins that are using Action Scheduler? Maybe WooCommerce?

    Is this error occurring all the time, or was this only a few isolated issues?

    Take care!

    Hi @n33d – We haven’t heard from you in about a week, so I’m going to go ahead and mark this ticket resolved. If you still have questions, though, please feel welcome to continue the conversation.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal error – Uncaught RuntimeException’ is closed to new replies.