Action_scheduler error + crash + database getting huge
-
Hi guys,
For the past 3 days I looked everywhere for a solution. I see people having the same problem yet no clear answer on what to do:
PROBLEMS CURRENTLY FACING:
1. I can’t add any post (I can only see them)
2. I can’t add any product (I can only see them)
3. Woocommerce database was impossible to get updated -> host devs updated it through CLI or some command -> I kept getting the action_scheduler error
4. My action_scheduler_log or that table is getting huge -> last time I cleared 15 gb or errorsNow I have this error:
Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Duplicate entry ‘0’ for key ‘PRIMARY’ in /home/customer/www/site.com/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44 Stack trace: #0 /home/customer/www/site.com/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL) #1 /home/customer/www/site.com/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action)) #2 /home/customer/www/site.com/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->sto in /home/customer/www/site.com/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44
I TRIED:
– Installing the action scheduler separately -> still get the error + the database action_scheduler stuff still gets filled up
– various database optimization plugins (I have a backup)This is driving me nuts. I saw some threads on github and here but no clear answer on what to do. What’s wrong with woocommerce?
The topic ‘Action_scheduler error + crash + database getting huge’ is closed to new replies.