action_scheduler cPanel error log
-
I have an issue where the plugin appears to be creating an error that is being logged in cPanel every minute leading to very large error_log files over time. Had to delete a 400MB file. Installed the plugin on two different sites with same effect. Am I missing something in my server’s php settings?
Apart from this, the plugin is working exactly as I imagine it should.
I have the latest version of the plugin and WordPress, php 8.3.
[06-Aug-2024 03:31:41 UTC] PHP Fatal error: Uncaught RuntimeException: Unable to claim actions. Database error: Table ‘indevelopmentdiy_wp712.wpq3_actionscheduler_actions’ doesn’t exist. in /home/indevelopmentdiy/public_html/wp-content/plugins/simply-schedule-appointments/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:944 Stack trace: #0 /home/indevelopmentdiy/public_html/wp-content/plugins/simply-schedule-appointments/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php(801): ActionScheduler_DBStore->claim_actions() #1 /home/indevelopmentdiy/public_html/wp-content/plugins/simply-schedule-appointments/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(221): ActionScheduler_DBStore->stake_claim() #2 /home/indevelopmentdiy/public_html/wp-content/plugins/simply-schedule-appointments/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php(160): ActionScheduler_HybridStore->stake_claim() #3 /home/indevelopmentdiy/public_html/wp-content/plugins/simply-schedule-appointments/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php(139): ActionScheduler_QueueRunner->do_batch() #4 /home/indevelopmentdiy/public_html/wp-includes/class-wp-hook.php(324): ActionScheduler_QueueRunner->run() #5 /home/indevelopmentdiy/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #6 /home/indevelopmentdiy/public_html/wp-includes/plugin.php(565): WP_Hook->do_action() #7 /home/indevelopmentdiy/public_html/wp-cron.php(191): do_action_ref_array() #8 {main}
- You must be logged in to reply to this topic.