Date: Thu, 11 Sep 2003 06:57:29 -0500 From: "Lewis Watson" <lists@visionsix.com> To: "culley harrelson" <culley@fastmail.fm> Cc: freebsd-questions@freebsd.org Subject: Re: apache13 to apache13-modssl port migration Message-ID: <009701c3785b$e03bfa50$df0a0a0a@vsis169> References: <bjm4dq$8a9$1@sea.gmane.org> <G9AotXLJUw@dmeyer.dinoex.sub.org><bjo82i$tir$1@sea.gmane.org> <3F5FB1B3.708@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. <gulp> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009701c3785b$e03bfa50$df0a0a0a>