Bug 30121 - apache crash on shell/cgi-bin commands.
Summary: apache crash on shell/cgi-bin commands.
Status: RESOLVED INVALID
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Build (show other bugs)
Version: 2.0.50
Hardware: PC other
: P3 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-15 12:58 UTC by Michael Dale
Modified: 2005-03-03 07:31 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Dale 2004-07-15 12:58:47 UTC
After I updated to Apache 2.0.50 on my Windows 2003 server every few days apache
seems to lockup when ever I try to run say awstats.pl (web stats program) or
some commands that take output from the windows cmd. Other pages html, php etc
seem to work fine. All I need to do is restart the apache service and it starts
working again. This didn't happen in version 2.0.49

Thanks for your time,
Michael Dale.
Comment 1 Michael Dale 2004-07-16 08:18:07 UTC
Okat the error I am getting is this:

[Wed Jul 14 23:22:06 2004] [error] [client 10.0.1.10] (70007)The timeout
specified has expired: ap_content_length_filter: apr_bucket_read() failed
[Wed Jul 14 23:22:06 2004] [error] [client 10.0.1.10] (70007)The timeout
specified has expired: ap_content_length_filter: apr_bucket_read() failed,
referer: http://forums.dalegroup.net/cgi-bin/awstats.pl
[Wed Jul 14 23:25:44 2004] [error] [client 10.0.1.10] (70007)The timeout
specified has expired: ap_content_length_filter: apr_bucket_read() failed
[Wed Jul 14 23:25:45 2004] [error] [client 10.0.1.10] (70007)The timeout
specified has expired: ap_content_length_filter: apr_bucket_read() failed,
referer: http://forums.dalegroup.net/cgi-bin/awstats.pl

I've only had this problem with apache 2.0.50 all other versions were fine.
Comment 2 Joe Orton 2005-03-03 16:31:50 UTC
That error message just means that the CGI script hung without producing any
output for a long while (configured by the Timeout setting).  So the first thing
to do is to ensure that there is no problem with the script (add debugging
output, etc); there's no real indication that there's a mod_cgi problem here.

The users@httpd mailing list could help with further questions:
http://httpd.apache.org/lists.html#http-users