[KLUG Members] Oh, the joys of upgrading!

[Robert G. Brown]

Doc Rea <rea@docrea.net>wrote:
>On Fri, 2002-12-27 at 01:20, Justin Buist wrote:
>>On Fri, Dec 27, 2002 at 12:56:02AM -0500, Robert G. Brown wrote:
>>>
>>>Moving things along to Apache2/PHP, I couldn't help but notice that 
>>>expressions like:
>>Oh, Crikey.... Apache2 + PHP?
I've elided content from this message where I have already addressed issues
in this thread. Anyone who is interested in previous answers is encouraged to
use the KLUG mailing list archives and the search tools.

>>...In her defense, she's a CIS major, not a CS one :). 
>Justin..don't get me started on this debate ;}
Is this the CS vs. CIS debate? If so, it's off-topic, but I'm interested
in it for another reason. I'll take it up in private e-mail.

>>Once we had Apache2 and PHP installed and everything seemily configured just
>>fine a restart of apache left nothing bound to port 80.  Odd.  After
>>inspecting the log files Apache2 was segfaulting upon startup!
Not my problem at all. I've not observed this, on reflection.

>This happened with a few folks depending on what they had on their
>machines prior to this assignment. I had everyone do an Apache source
>install. Some folks who had a binary ran into some gotchas if they
>hadn't cleaned up beforehand.
Without claiming perfection for it in cleanups or upgrades, this has been a 
straight binary RPM install and upgrade so far. My focus has been in migrating
sites (in many cases to new directories), and making sure the content (static
or dymanic) is working right.

The install for source is a good exercise, especially if you're installing
both Apache and PHP from scratch. I was thinking about doing it, and I may
do so, if the problems are more severe than they appear to be now, such as
may be revealed by volume testing.

>Modules are definitely not quite there in Apache 2 for sure, but they
>will be.
We would certainly hope so, Doc! :) I think the less "glamorous" modules
may be the less stable, but a lot of them have to get there. 

I don't understand how Apache 2.0.x could be released without all the
authentication modules being redone and tested, in light of the new 
module API, but that's just me. To the extent this is true, Apache 2
is not ready for prime time.

I ALSO don't understand why Adam had such trouble with compiling PHP,
but I don't want to preview my reply to his posting to this thread :).

>I haven't had any problems with Apache 2.0.43 and PHP 4.3.0, but the
>server isn't doing much but running development stuff I'm working on.
OK, I'm a wee bit behind ya, with 2.0.40 and 4.2.2, and I have not seen any
problems with Apache operations or php per se; but I'm going to do some volume
testing in the next few days. The problems themselves relate to threading,
so the issue would seem to be that Apache 2, php, and the underlying libs
are thread-safe. If so, no amount of pounding will reveal problems, if not,
I should be in for many segfaults, and perhaps a move forward to the 
versions you are using. After that, it may be fall back to the latest 1.3.x,
and see how THAT fares.

							Regards,
							---> RGB <---