Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 19 Jan 2004 09:50:04 -0000
Message-ID: <20040119095004.28862.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 26233]  -
    Server Crashed By Odd Query String

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26233

Server Crashed By Odd Query String


------- Additional Comments From trawick@apache.org  2004-01-19 09:50 -------
These odd URLs and error log entries for default.ida are very common.
Also, it is extremely rare for a request that is logged in access log to
subsequently cause a crash.

In all likelihood, this is all the information that can be gleaned from the logs:

[Sun Jan 18 04:12:11 2004] [notice] SIGHUP received.  Attempting to restart
[Sun Jan 18 04:12:11 2004] [notice] seg fault or similar nasty error detected in
the parent process

The best way to debug this is from a core file written when the parent crashed.

Possibly there is some module in your configuration that will always cause a
crash with apachectl restart.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org