Open thomasfeichter opened 4 years ago
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
Then please check: https://github.com/omega8cc/boa/issues/746
Sent with GitHawk
Thank you for the hint with #746 I will have a look at it. None of the cases mentioned in the docs seem to match my scenario. I use CloudFlare, but the alias redirect in Aegir is not enabled. However, when checking the nginx access logs, I noticed that the internal call on cron.php gets a 302 response code. I'm not entirely sure if that's expected or not. The Aegir alias redirect would return a 301 response code I assume.
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.