-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cron not running #1456
Comments
This has been discussed in several issues here before with explanation how to make the change to Drush based cron permanent and why it can be dangerous in some scenarios. It’s better to investigate why web based method doesn’t work. But first please check the docs at: https://learn.omega8.cc/running-scheduled-sites-cron-in-aegir-118 Sent with GitHawk |
Thank you for the hint with #746 I will have a look at it. |
302 is probably CloudFlare not BOA/Aegir response. If that happens, it simply means that local request is not working for some reason. We would have to see the relevant access log snippet to determine what is going on. |
I switched it back to wget cron method in order to check the log entries again, but on all servers the wget cron seems to be working again. There have been no changes to CloudFlare or Aegir site settings recently, so I am not sure why the issue is now not appearing anymore. I'll keep on eye on it. |
I am having issues with cron not running for multiple websites on multiple BOA servers running v.BOA-4.0.1
When running cron via drush or in the Drupal backend it completes without errors.
It also appears that changing the cron method in Aegir to "Drush" instead of "Wget" improves the cron execution. It is not executed every hour, but successfully runs every couple of hours. However, BOA resets it periodically (once a day) to "Wget" in the Aegir backend.
The text was updated successfully, but these errors were encountered: