Posted by ar-jan on December 5, 2012 at 12:31am
I just updated a Debian 6 BOA 2.04 system using "aptitude upgrade". I was under the impression that this is OK after the initial install. When prompted during the upgrade I chose to keep locally modified php.ini files (two times), thinking this would preserve any BOA-specific settings.
Then my Octopus web control panel started throwing occasional errors: 502 Bad Gateway - nginx.
My php53-fpm-error.log showed this: ERROR: unable to bind listening socket for address '127.0.0.1:9090': Address already in use (98)
I then updated again using barracuda up-stable and all seems to be working again. I guess some configuration file got changed erroneously with the update. So did I do something wrong here, what's the correct way to update packages?
Comments
Upgrading BOA OS
Rather than using apt-get update, you should run
barracuda up-stable
There are some extra things that BOA does when it updates the OS. I have crashed my system by running the updates directly.
You may also consider updating the Octopus instances afterwards
octopus up-stable o1
I don't know if anyone else has had this problem, by my crond use to stop so I always run
service cron restart
as well
barracuda up-stable
barracuda up-stable is sufficient to update you server.
"Barracuda is the main script for the Aegir Master Instance system install and upgrades, including OS env and main Aegir instance..."
http://drupalcode.org/project/barracuda.git/blob/HEAD:/README.txt
@ JimSmith or anyone - is
@ JimSmith or anyone - is there some difference between
$ barracuda up-stable
mentioned in this thread and also at eg https://wiki.thingsandstuff.org/BOA and
$ barracuda up-stable system
which is advised by the apticron report email?
Thanks
"System" will only upgrade the system.
"System" will only upgrade the system. It will not upgrade the Aegir Master Instance.
See http://drupalcode.org/project/barracuda.git/blob/HEAD:/docs/UPGRADE.txt.
We also use the BOA scripts
We also use the BOA scripts for upgrading our servers. One quirk I discovered was that the scripts overwrote customizations to /etc/csf/csf.conf so our developers were unable to update subversion projects because our custom port settings were overridden.
what about the new security update 7.18
I also use barracuda up-stable and octopus up-stable but it still does not give me new platforms with 7.18 instead of the old 7.17. Is that by design or am i doing something wrong ? Do we need to follow HEAD instead of STABLE to get the security updates faster.
@hafnius
You may want to follow updates we post on Twitter: https://twitter.com/omega8cc
[EDIT] I have added this info in the group header.
how often do you run barracuda up-stable?
I often run these commands.
screen (because I often work from cafes with flaky WIFI)
wget -q -U iCab http://files.aegir.cc/versions/BOA.sh.txt
bash BOA.sh.txt
barracuda up-stable
Maybe I should change my approach. What do you do?
Do you wait for an "apticron report" e-mail to arrive?
Do you put these commands into cron, to run every day automatically?
Do you use apt-get update and upgrade instead, and wait for new BOA releases?
Many thanks,
Nick
Don't apt-get upgrade
As pointed out above, don't use
apt-get upgrade, this can mess up the installation.barracuda up-stablewill also update your packages.I run this manually when needed (just one 'friends and family' vps); does anyone automate this?