www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Lilienberg ...@globecom.se>
Subject general/5168: HTTPD gets broken pipe when error 404
Date Tue, 19 Oct 1999 08:36:29 GMT

>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
>Originator:     dl@globecom.se
>Release:        1.3.9
Linux (redhat 6.0), kernel 2.2.12 SMP (x2), egcs 1.1.2
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...
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...
No, but Apache 1.3.6 works fine with same configure-options and httpd.conf.
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> 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!     ]

View raw message