Douglas Allan Tutty <[EMAIL PROTECTED]> writes: > On Fri, Jun 01, 2007 at 12:07:23AM -0400, Scott Gifford wrote: >> Andrew Sackville-West <[EMAIL PROTECTED]> writes: >> > On Wed, May 30, 2007 at 12:23:46AM -0400, Scott Gifford wrote: >> >> Kamaraju S Kusumanchi <[EMAIL PROTECTED]> writes: >> >> Our upgrade from Woody to Sarge was so disastrous, I will need more >> >> time for this client to forget about it before I can propose another >> >> upgrade. :-) >> > >> > what were the woody -> sarge issues? perhaps they've been addressed... >> >> Postgres completely fell apart, and it took many hours to piece things >> back together. > > Did you have a postgres dump just prior to the upgrade? In what way did > it fall apart? What did you have to do to piece things back together; > didn't restoring from the dump work?
The data was OK, but it lost all the user accounts. It's been a few months now and my memory is a bit hazy, but IIRC, the format of the Postgres password file changed between versions. When the upgrade failed (probably because of our unusual Postgres configuration), the password file had to be re-created by hand. Which all sounds pretty straightforward, except there weren't any clear messages to indicate this, and it took me quite a few hours to figure out the problem. The change in the file format wasn't documented clearly anywhere that I could find, which I found very frustrating. Eventually we found the problem, deleted the password file, and re-created the accounts by hand (fortunately nobody took our advice to reset their password), but our server was down for several hours. There were also a bunch of changes to PHP that wreaked havoc for us. We were running PHP through CGI (not embedded in the Web server), and Sarge changed how all that worked, and broke all of our existing configurations. If the server hadn't been down and I'd had a paper and pen, I would have kept better track of exactly what happened. :-) This is the only upgrade to Sarge I did that had significant problems, but I will admit the experience left me much less confident in the upgrade process. ----Scott. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
