XF 2.2 There are scheduled jobs outstanding which have not run. Jobs may not be getting triggered when expected.

Anatoliy

Well-known member
Upgraded yesterday. There is this warning in ACP. In tools->cron entries can see that most of entries have yesterday as next run date. Tried to run manually. Only few updated. But everyone had a message " Cron entry was run successfully. ".
 
that was funny ) I thought may be a production forum 2.1 and a duplicated upgraded to 2.2 in /test could somehow conflict, co I created subdomain test, replicated production one there and upgraded to 2.2. And I see the same problem.
Then I unchecked ' Enable board URL canonicalization' and the problem has gone.
Everything works. I forgot to disable add-ons before upgrade. )
 
  • Like
Reactions: jul
Upgraded yesterday. There is this warning in ACP. In tools->cron entries can see that most of entries have yesterday as next run date. Tried to run manually. Only few updated. But everyone had a message " Cron entry was run successfully. ".

Hey,
I am facing this problem so what is the actual fix?
I have upgraded to the latest version
Thank you.

Did anyone manage to find a fix?
 
i just fixed this by adding cron job to server
*/usr/local/bin/ea-php81 /home/example/public_html/cmd.php xf:run-jobs --wait
[td] [/td] [td] [/td]

ea-php81 is my php version replace with yours and cmd.php path i am using cpanel you can add according to your configration
Great!!
The same thing happened to me today. I simply created a cron task in /etc/cron.d/ with the name xf-run-jobs and inside I added:

Code:
* * * * * user /usr/bin/php8.2 /home/example/public_html/cmd.php xf:run-jobs --wait

Where user is the username of your site, the PHP path in my case was PHP 8.2, and then the full path to where that file is located. After that, I gave it 644 permissions with:

Code:
chmod 644 /etc/cron.d/xf-run-jobs

Then I restarted the cron service with:

Code:
sudo systemctl restart cron

And problem solved. In my case, the tables hadn’t been deleted, there wasn’t any stuck cron job, and enabling or disabling the cron task or any other task didn’t fix it either. The only thing that worked for me was this.

Thanks!
 
Back
Top Bottom