You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Brad Cox <bc...@virtualschool.edu> on 1998/12/15 00:25:27 UTC
os-linux/3531: Bad file number: flock; Exiting
>Number: 3531
>Category: os-linux
>Synopsis: Bad file number: flock; Exiting
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Mon Dec 14 15:30:01 PST 1998
>Last-Modified:
>Originator: bcox@virtualschool.edu
>Organization:
apache
>Release: 1.3.3
>Environment:
Linux www.virtualschool.edu 2.0.30 #1 Sun Jul 19 14:49:01 EDT 1998 i586 unknown
Server Version: Apache/1.3.3
Server Built: Dec 14 1998 18:52:42
>Description:
After working flawlessly for months, apache has started crashing (several times a day) with this in the error log
[Mon Dec 14 18:12:26 1998] [emerg] (9)Bad file number: flock: LOCK_EX: Error getting accept lock. Exiting!
Nothing had changed; no recompiles, installs, etc. I've rebooted, fsck'd, etc, but nothing helped.
>How-To-Repeat:
I don't see how you can. This worked great for months, then kaboom.
>Fix:
Lincoln Stein reports he's encountered the very same problem and that this has been reported several times in this DB. On his suggestion, I've made this change to include/ap_config.h and am trying it out now. Too soon to say whether this fixes it.
/* flock is faster ... but hasn't been tested on 1.x systems */
/* bjc: #define USE_FLOCK_SERIALIZED_ACCEPT */
#define USE_FCNTL_SERIALIZED_ACCEPT
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[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! ]