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?

CommentFileSizeAuthor
#1 baracuda_log.txt4.17 KBmuschpusch
#1 barracuda_cnf.txt1.87 KBmuschpusch
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

muschpusch’s picture

FileSize
1.87 KB
4.17 KB
muschpusch’s picture

Issue summary: View changes
muschpusch’s picture

Ok 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.

muschpusch’s picture

hm... ok running: octopus up-stable o1 fixed it. Even thought i had run octopus up-stable all... Anyways.. Closing this...

muschpusch’s picture

Status: Active » Fixed
omega8cc’s picture

Project: Barracuda » Octopus
Version: 6.x-2.0-rc22 » 6.x-2.x-dev
Category: Bug report » Support request
Status: Fixed » Closed (duplicate)