Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I had some problems with cron but i'm not pretty sure when it started. At some point cron stopped working due to a wrong path in /data/disk/o1/aegir.sh
#wrong since php is not over there:
/opt/local/bin/php /data/disk/o1/tools/drush/drush.php '@hostmaster' hosting-dispatch
#right
/opt/php53/bin/php /data/disk/rhizom/tools/drush/drush.php '@hostmaster' hosting-dispatch
For new octopus instances it's no problem. Some update paths problem?
Comment | File | Size | Author |
---|---|---|---|
#1 | baracuda_log.txt | 4.17 KB | muschpusch |
#1 | barracuda_cnf.txt | 1.87 KB | muschpusch |
Comments
Comment #1
muschpusch CreditAttribution: muschpusch commentedComment #2
muschpusch CreditAttribution: muschpusch commentedComment #3
muschpusch CreditAttribution: muschpusch commentedOk there are some problems: the aegir.sh of a new account looks differently from the older account. The root of the problem is most likely that my octopus instances haven't been updated for a while 2.0.6 while barracuda was on 2.0.9 already . After i realized that a couple of months ago i updated both but obviously that was to late.
i'm running: "octopus up-stable o1" right now... Maybe it will fix the issue.
Comment #4
muschpusch CreditAttribution: muschpusch commentedhm... ok running: octopus up-stable o1 fixed it. Even thought i had run octopus up-stable all... Anyways.. Closing this...
Comment #5
muschpusch CreditAttribution: muschpusch commentedComment #6
omega8cc CreditAttribution: omega8cc commentedDuplicate of: #2238261: Aegir tasks not running due to incomplete barracuda+octopus upgrade