www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey Baker <...@tamu.edu>
Subject os-linux/2723: HTTPD dies complaining "error getting accept lock"
Date Tue, 28 Jul 1998 04:47:04 GMT

>Number:         2723
>Category:       os-linux
>Synopsis:       HTTPD dies complaining "error getting accept lock"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jul 27 21:50:00 PDT 1998
>Last-Modified:
>Originator:     jwb@tamu.edu
>Organization:
apache
>Release:        1.3.1
>Environment:
Linux 2.0.34 i686 pgcc/egcs 2.90.29 glibc 5.4.44, also a problem with straight
egcs.
>Description:
Apache 1.3.1 dies unexpectedly with the following error:
[emerg] (9)Bad file number: flock: LOCK_EX: Error getting accept lock. Exiting!
[alert] Child nnnnn returned a Fatal error

This brings down the entire httpd.  There are no other error messages, console
output, or core dumps.

My apache is configured very minimally: it does not include cgi, actions, include, or any
non-standard module except for mod_perl 1.15.
>How-To-Repeat:
Compile and install Apache 1.3.1 + mod_perl 1.15 + Apache::Session, then use ab
to hammer example.perl until it dies.
>Fix:
Nope
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]




Mime
View raw message