Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 32223 invoked from network); 14 Jul 2006 17:42:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Jul 2006 17:42:27 -0000 Received: (qmail 32020 invoked by uid 500); 14 Jul 2006 17:42:22 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 31606 invoked by uid 500); 14 Jul 2006 17:42:21 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 31595 invoked by uid 99); 14 Jul 2006 17:42:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jul 2006 10:42:21 -0700 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,PLING_QUERY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [12.11.148.122] (HELO relay2.ptc.com) (12.11.148.122) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jul 2006 10:42:19 -0700 Received: from hq-ex3fe2.ptcnet.ptc.com ([132.253.201.63]) by relay2.ptc.com with ESMTP; 14 Jul 2006 13:41:58 -0400 X-IronPort-AV: i="4.06,244,1149480000"; d="scan'208,217"; a="146380070:sNHT28980140" Received: from [132.253.11.178] ([132.253.11.178]) by HQ-EX3FE2.ptcnet.ptc.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Jul 2006 13:41:58 -0400 Message-ID: <44B7D765.6030001@ptc.com> Date: Fri, 14 Jul 2006 12:41:57 -0500 From: Jess Holle User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: dev@httpd.apache.org CC: "Fenlason, Josh" Subject: Re: Apache 2.2.2 + CGI -> Child Exit?!? References: <44B797CB.9030909@ptc.com> <44B7A4C9.6010401@ptc.com> In-Reply-To: <44B7A4C9.6010401@ptc.com> Content-Type: multipart/alternative; boundary="------------080708020400060601080703" X-OriginalArrivalTime: 14 Jul 2006 17:41:58.0254 (UTC) FILETIME=[CE16B8E0:01C6A76C] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. --------------080708020400060601080703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit A little more troubleshooting shows that this is likely not an issue with the particular CGI in question. I say this because the issue goes away when we reorder several of our conf files. Even if this is our error, a child death without any warning or debug output due to a conf file ordering issue seems like a serious bug! We'll do more troubleshooting and hopefully narrow down to what the issue is, but these are not terribly complex conf files overall. The CGI conf file does a bit of ScriptAlias, Alias, Directory, AuthnProviderAlias, AuthLDAPURL, usage. The other conf files (those whose inclusion prior to the CGI conf file causes the issue) contain similar things except no ScriptAlias usage plus Location and some mod_rewrite usage. -- Jess Holle Jess Holle wrote: > Note: In case anyone thinks I posted to the wrong group, I'm really > looking for: > > * Developer-level info as to if/how a CGI program could cause an > Apache worker process death in 2.2.2 > * Developer-level pointers on where in mod_cgi we should place > breakpoints, logging, or the like to try to determine what's > going wrong -- or if this even makes sense > > Of course if there is some out-of-the-box verbosity option I'm missing > to help with this, I'm all ears. I used LogLevel debug, of course, > but it told me nothing new. > > -- > Jess Holle > > Jess Holle wrote: >> With Apache 2.2.2 on Windows, we're getting the following error: >> >> Parent: child process exited with status 3221225477 -- Restarting. >> >> Whenever URLs are requested that execute CGI that was working 100% >> fine in Apache 2.0.x. >> >> This leads me to ask: >> >> * How can a CGI program kill an Apache worker process? >> * How can this happen only in Apache 2.2.2, but not in any 2.0.x >> that we've tried. >> >> The CGI in question is a 3rd-party application for which we have >> neither source nor official Apache 2.2.2 support. Yet I would think >> that CGI should just work irrespective, right? Or at least it >> shouldn't kill the Apache worker processes, right? Could this be an >> issue in 2.2.2's mod_cgi? >> >> To make matters weirder the issue went away for one developer, but he >> does not know what he did to make it go away nor can anyone else seem >> to reproduce this. >> >> -- >> Jess Holle --------------080708020400060601080703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit A little more troubleshooting shows that this is likely not an issue with the particular CGI in question.

I say this because the issue goes away when we reorder several of our conf files.  Even if this is our error, a child death without any warning or debug output due to a conf file ordering issue seems like a serious bug!

We'll do more troubleshooting and hopefully narrow down to what the issue is, but these are not terribly complex conf files overall.  The CGI conf file does a bit of ScriptAlias, Alias, Directory, AuthnProviderAlias, AuthLDAPURL, usage.  The other conf files (those whose inclusion prior to the CGI conf file causes the issue) contain similar things except no ScriptAlias usage plus Location and some mod_rewrite usage.

--
Jess Holle

Jess Holle wrote:
Note: In case anyone thinks I posted to the wrong group, I'm really looking for:
  • Developer-level info as to if/how a CGI program could cause an Apache worker process death in 2.2.2
  • Developer-level pointers on where in mod_cgi we should place breakpoints, logging, or the like to try to determine what's going wrong -- or if this even makes sense
Of course if there is some out-of-the-box verbosity option I'm missing to help with this, I'm all ears.  I used LogLevel debug, of course, but it told me nothing new.

--
Jess Holle

Jess Holle wrote:
With Apache 2.2.2 on Windows, we're getting the following error:

  Parent: child process exited with status 3221225477 -- Restarting.

Whenever URLs are requested that execute CGI that was working 100% fine in Apache 2.0.x.

This leads me to ask:
  • How can a CGI program kill an Apache worker process?
  • How can this happen only in Apache 2.2.2, but not in any 2.0.x that we've tried.
The CGI in question is a 3rd-party application for which we have neither source nor official Apache 2.2.2 support.  Yet I would think that CGI should just work irrespective, right?  Or at least it shouldn't kill the Apache worker processes, right?  Could this be an issue in 2.2.2's mod_cgi?

To make matters weirder the issue went away for one developer, but he does not know what he did to make it go away nor can anyone else seem to reproduce this.

--
Jess Holle
--------------080708020400060601080703--