From owner-freebsd-questions@FreeBSD.ORG Thu Sep 11 04:57:50 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2572916A4BF for ; Thu, 11 Sep 2003 04:57:50 -0700 (PDT) Received: from mordrede.visionsix.com (mordrede.visionsix.com [65.202.119.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EDD43FCB for ; Thu, 11 Sep 2003 04:57:47 -0700 (PDT) (envelope-from lists@visionsix.com) Received: from vsis169 (unverified [65.202.119.169]) by mordrede.visionsix.com (Vircom SMTPRS 2.1.258) with SMTP id ; Thu, 11 Sep 2003 06:57:45 -0500 Message-ID: <009701c3785b$e03bfa50$df0a0a0a@vsis169> From: "Lewis Watson" To: "culley harrelson" References: <3F5FB1B3.708@mac.com> Date: Thu, 11 Sep 2003 06:57:29 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-questions@freebsd.org Subject: Re: apache13 to apache13-modssl port migration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2003 11:57:50 -0000 > culley harrelson wrote: > > I am a little shaky in the knees at this prospect. This is on a > > production web server getting over 1 million page views per day. I use > > mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports > > installed like squirrelmail, mnogosearch, a bunch of pear libraries (not > > even sure if they are dependent on apache13), phpMyAdmin and probably a > > few other things I haven't even thought of. > > You have complete backups, right? You probably should have a test server where > you can test the software upgrade under non-production conditions... > If you have another machine you can do this with much less stress. 1.Build the second machine (aka "new" server); 2. Rsync the files over (or from a backup). 3. Pull the network plug on the original; 4. Run a script to fire off any extra ip addresses for your "new" server. 5. Apachectl startssl on the "new" server. Now it should be running and you can do spot checks to see how your crucial sites are doing... If everything is ok thats great! If not then pull the network plug on the "new" server and plug the old one back in while you see where the problems are on the new one... HTH, Lewis