>Number: 5168 >Category: general >Synopsis: HTTPD gets broken pipe when error 404 >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Oct 19 01:40:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.9 >Environment: Linux (redhat 6.0), kernel 2.2.12 SMP (x2), egcs 1.1.2 >Description: HTTPD runs perfectly until 8-10 in the morning when INFOSEEK searches for /robots.txt on one of my virtual hosts. I have no error-document, and the log files from apache says:
SIGHUP received, attempting to restart... then..... Broken Pipe (client socket), Error 32 (about 70 pcs.) The silly thing is, I haven't send the SIGHUP. Does apache do that itself ? httpd doesn't restart, and I have to do it. A apachestl start won't do... >How-To-Repeat: ariel.globecom.net:8080/error.html >Fix: No, but Apache 1.3.6 works fine with same configure-options and httpd.conf. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
