Sorry, I'm only familiar with what happens on the linux side of things. What happens on Windows may be different, but if it helps, mod_php will cause apache processes to segmentation fault after a random amount of load (usually after 2-3 days). At this point, anything that apache sends off to php will segfault, but apache will continue to serve other file types (html, images, css, js, etc) without a problem. Apache itself doesn't crash. A graceful restart of the apache master process fixes the problem (for another 2-3 days).
fcgid should prevent apache from segfaulting in the first place, so you would not need to worry about being able to gracefully recover. Hope that helps. --Victor On 8/14/07, Stephen Johnston <[EMAIL PROTECTED]> wrote: > > Victor, > > Just to be clear. Are you saying they all end up crashing Apache, or > causing Aache not to gracefully recover from crashes? There are two issues > here and I'd like to know for which FastCGI is a typical solution. We've > already been investigating fcgid as an option. > > -Stephen > > > On 8/13/07, Victor Trac <[EMAIL PROTECTED]> wrote: > > > > On 8/13/07, Stephen Johnston < [EMAIL PROTECTED]> wrote: > > > > > Greetings, > > > > > > We have an Apache 2.0.59 server on Windows 2003 running PHP 5.2.3. We > > > are also running eaccelerator. Sometimes, PHP faults and brings down > > > Apache > > > with it. Considering this happens a few times a week, it's not the end of > > > the world. The bad thing is that Apache "restarts", the logs show it > > > spinning up new threads to serve pages, but it doesn't actually respond to > > > any requests. > > > > > > On a similar, maybe related, note we have tried setting > > > MaxRequestsPerChild on this system and when it is reached it exhibits > > > simliar behavior. The logs say "Restarting apache. Starting X threads." > > > etc. > > > but it actually serves no pages. > > > > > > Anyone have any ideas? > > > > > > -Stephen > > > > > > > On the linux side, mod_php plus any sort of op-code caching > > (eaccelerator, APC, etc) all end up doing this after a little load. The > > only long term "fix" I know of is to run php using fastcgi. However, > > another solution is to have a script monitor the apache error logs for the > > segmentation faults, at which point it restarts apache completely. I do > > this now, and it works well. You can probably script a similar thing on > > windows. > > > > --Victor > > > > -- > > http://www.victortrac.com > > > > > -- > Stephen Johnston > President/CEO > Guild Launch, LLC > http://www.guildlaunch.com/ > > Communities for online gamers, guilds and clans. -- http://www.victortrac.com
