advice on upgrading production FreeBSD 5.4
illoai at gmail.com
illoai at gmail.com
Sun Feb 26 21:33:33 PST 2006
On 2/26/06, Andrew Pantyukhin <infofarmer at gmail.com> wrote:
> On 2/26/06, pobox at verysmall.org <pobox at verysmall.org> wrote:
> > I inherited a production FreeBSD 5.4 used as a web/mail server (Apache,
> > PostgreSQL, php, qmail, vpopmail, Courier). Could anybody help me with
> > information about a web resource on upgrading such system (all, OS only
> > or component by component) with minimum downtime. I looked into cvsup
> > and portupgrade - is this the right way for production systems or is
> > there another one? For example is it possible to have the older version
> > running until the new one downloads/compiles and then to replace it
> > within seconds? Also - what if the new version does not work correctly -
> > is it possible to keep the old and revert to it.
> First, you'd better upgrade to 6.1. Read /usr/src/UPDATING
> and handbook for that.
I'm not sure if I had a working machine that was up on its security patches
that I would upgrade, where admittedly 5.4 to 6.x is not a huge jump
(compared to 4 -> 5 or even 3 -> 4). Assuming all goes well your down-
time should be the time it takes the server to reboot, but if (very big)
your buildworld has some hidden fault (personal experience when /bin/sh
would dump core on every invocation, very difficult to fix) you could be
looking at a couple of days of downtime.
Whereas I believe that the 6.x series is much better than 5.x, I'm not
convinced that the risk/reward payoff is that great, doubly so given
that it's a production machine. 5.4, while obsolete from a numerical
standpoint, will be useable for a long while: years, probably.
If the hardware itself is nothing special, or replaceable for less than the
cost of downtime, you might look into putting up a second server
running the new software, test carefully for a week or so, and then
All of this is speculation.
As a postscript: the tales of 5.x to 6.x upgrades have been for the most
part very painless, but in production systems conservatism leads to
More information about the freebsd-questions