Posted by leelive on May 31, 2014 at 12:44am
This is a Linode install on Debian 6 64 (3.14.4).
While this upgrade appeared to run smoothly using:
$ cd;wget -q -U iCab http://files.aegir.cc/BOA.sh.txt;bash BOA.sh.txt
$ barracuda up-stable
$ octopus up-stable all both
all verifies are waiting in the queue and not executing.
Anyone know how to fix this?
An addendum:
It gets even stranger. When I tried to ssh back in I discovered the port had reverted to the default 22 instead of the port specified in my .barracuda.cnf.
Thanks

Comments
Did you try to run as o1 :
Did you try to run as o1 : bash /var/xdrago/run-o1
I have found that the port
I have found that the port also reverts to 22 when I tried to change mine
Check your username - I had 'sites' as the octopus name and that has since been hardened and the queue failed.
I had to transition all sites to a new username.
Need "legacy upgrade" clarification
As you can see below from my March 30 post, my last attempt to upgrade failed. Thanks to charos and geoff for their suggestions. Maybe it was too late but running xdragon didn't help and my octopus name is still the default.
Anyway, I restored the entire Linode from backup so am still running BOA 2.1.3 which is screaming for updates. Obviously I'm hesitant to upgrade BOA beyond 2.1 given my experience but I'm confused by this statement:
"These special 'legacy' commands allow you to install and/or upgrade the 'old stable', once the 'new stable' is released. But only until another 'stable' is released, of course."
This implies that it's too late to use the "up-legacy" commands given there has been additional releases since 2.1.3. Is this true or am I over-thinking?
Also, Given my Linode is Debian 6 64 (3.14.4) and all my sites are using Drupal 7.26, MariaDB (5.5.36) and PHP 5.3.28 I still don't understand why the "stable" upgrade had issues. Been using BOA for over 2 years and all prior upgrades were flawless. So, I'm considering creating another Linode, doing a fresh BOA install of latest stable and migrating the sites between servers.
Is this the best approach, or should I go boldly forth and try the normal upgrade again?
As ever, thanks for your responses.