josephs8 Posted January 19, 2023 Posted January 19, 2023 I am not getting an error that scheduled tasks are not running, but I have a very large number of background tasks that appear on the widget on the dashboard. It shows I can run them manually, but I am afraid of what that could do to the board's performance with that many. What are my possible options here to fix this?
teraßyte Posted January 19, 2023 Posted January 19, 2023 Do you have a Cronjob setup to run the tasks or are you running them "manually" with user activity? As long as you're using a Cronjob and it's properly setup it should clear up background tasks quickly.
Daniel F Posted January 19, 2023 Posted January 19, 2023 AND if you're using the cron, make sure it's using the same PHP version as your webserver.
josephs8 Posted January 19, 2023 Author Posted January 19, 2023 We are using a cronjob and yes it is using the same version of php. We've always used a cronjob and it has not gotten any better just appears to be increasing.
Jim M Posted January 19, 2023 Posted January 19, 2023 You will need to check that your cron job is getting processed by your server appropriately, ran every minute without errors. If you have not verified the cron job since upgrading PHP, this would be worth while.
josephs8 Posted January 20, 2023 Author Posted January 20, 2023 No errors are reported in the cronlog (and it is showing it is being executed every minute), the messages log, or the PHP log. I also was able to execute the command that crontab runs manually and it did not produce any errors. I've also set up a log on the cronjob output and checked for output errors from that and nothing. Finally, I also switched it to traffic based and it didn't seem to impact it.
Marc Posted January 20, 2023 Posted January 20, 2023 7 hours ago, josephs8 said: No errors are reported in the cronlog (and it is showing it is being executed every minute), the messages log, or the PHP log. I also was able to execute the command that crontab runs manually and it did not produce any errors. I've also set up a log on the cronjob output and checked for output errors from that and nothing. Finally, I also switched it to traffic based and it didn't seem to impact it. Your problem here is you are doing many thing sat ones and not actually giving them chance to run. If you make a change to correct the issue, you need to leave it 24 hours and dismiss the task. If you know them to be running, the message will not return
Recommended Posts