config/1593: error_log is growing fast with a single error. Please see Full Description

[Thomas Richards <tr...@winkcomm.com>]

>Number:         1593
>Category:       config
>Synopsis:       error_log is growing fast with a single error. Please see Full Description
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          support
>Submitter-Id:   apache
>Arrival-Date:   Mon Dec 22 12:10:00 PST 1997
>Last-Modified:
>Originator:     trichard@winkcomm.com
>Organization:
apache
>Release:        1.2.4
>Environment:
SunOS arthur 5.5.1 Generic_103640-01 sun4u sparc SUNW,Ultra-1

I am running NFS & NIS if this may have something to do with it.
>Description:
Here is what is getting put in the error_log:

[Mon Dec 22 13:52:43 1997] fcntl: F_SETLKW: No record locks available
[Mon Dec 22 13:52:43 1997] - Error getting accept lock. Exiting!
[Mon Dec 22 13:52:43 1997] fcntl: F_SETLKW: No record locks available
[Mon Dec 22 13:52:43 1997] - Error getting accept lock. Exiting!
[Mon Dec 22 13:52:43 1997] fcntl: F_SETLKW: No record locks available
[Mon Dec 22 13:52:43 1997] - Error getting accept lock. Exiting!
[Mon Dec 22 13:52:43 1997] fcntl: F_SETLKW: No record locks available
[Mon Dec 22 13:52:43 1997] - Error getting accept lock. Exiting!
.
.
.
.
 
Every time we get a hit another error is added.  It's already filled up our
file system twice! This is a production site. Can you help me try and
track this down? What do I have to do to the configuration to cause apache
to stop this particular error?

I tried recompiling with these options, thinking it might have something
to do with the mutex problem (i.e. listener...):

-DUSE_FLOCK_SERIALIZED_ACCEPT

AND

-DUSE_FNCTL_SERIALIZED_ACCEPT

But it didn't solve the problem.

Please help.

This error never occured in previous versions.
>How-To-Repeat:
NA
>Fix:
I don't know. Help%2
>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. ]