www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey W. Baker" <...@tca.net>
Subject Re: os-linux/2723: HTTPD dies complaining "error getting accept lock"
Date Fri, 06 Nov 1998 17:10:00 GMT
The following reply was made to PR os-linux/2723; it has been noted by GNATS.

From: "Jeffrey W. Baker" <jwb@tca.net>
To: lars@apache.org
Cc: apbugs@apache.org, lstein@cshl.org
Subject: Re: os-linux/2723: HTTPD dies complaining "error getting accept lock"
Date: Fri, 06 Nov 1998 09:56:17 -0600

 lars@apache.org wrote:
 
 > Comment-Added-By: lars
 > Comment-Added-When: Fri Nov  6 07:41:13 PST 1998
 > Comment-Added:
 > [This is a standard response.]
 > This Apache problem report has not been updated recently.
 > Please reply to this message if you have any additional
 > information about this issue, or if you have answers to
 > any questions that have been posed to you.  If there are
 > no outstanding questions, please consider this a request
 > to try to reproduce the problem with the latest software
 > release, if one has been made since last contact.  If we
 > don't hear from you, this report will be closed.
 > If you have information to add, BE SURE to reply to this
 > message and include the apbugs@Apache.Org address so it
 > will be attached to the problem report!
 
 Lars et al,
 
 It was a mere 17 days ago when Lincoln Stein contacted me to reveal that
 he has the same problem with the very latest and greatest versions of
 Apache and mod_perl (1.3.3/1.16, respectively).  I have included our email
 exchange to add to this bug report.
 
 Subject: Bad file number: flock: LOCK_EX
    Date: Tue, 20 Oct 1998 11:03:14 -0400
    From: Lincoln Stein <lstein@cshl.org>
      To: jwb@tamu.edu
 
 Hi Jeffrey,
 
 I see from the Apache bug database that you're seeing this problem:
 
 [emerg] (9)Bad file number: flock: LOCK_EX: Error getting accept lock.
 Exiting!
 [emerg] (9)Bad file number: flock: LOCK_EX: Error getting accept lock.
 Exiting!
 
 All of a sudden (as of last week) I'm seeing it too!  Every so often
 it brings down the root web server...arrgh!
 
 Did you ever find a solution or workaround for this?  I'm running
 Linux 2.0.33, with Apache/1.3.3 mod_perl/1.16.
 
 Lincoln
 
 Subject: Re: Bad file number: flock: LOCK_EX
    Date: Tue, 20 Oct 1998 10:30:14 -0500
    From: "Jeffrey W. Baker" <jwb@tamu.edu>
      To: lstein@cshl.org
 
 Lincoln,
 
 I haven't had this problem in a while, I was hoping it had quietly gone
 away. 
 My success could be due to an upgrade to libc6, but I am not sure.  I have
 received several emails from people with the same problem.
 
 I am interested in this bit from the CHANGES file:
 
 *) PORT: Apache has need for mutexes to serialize its children around
    accept.  In prior versions either fcntl file locking or flock file
    locking were used.  The method is chosen by the definition of
    USE_xxx_SERIALIZED_ACCEPT in conf.h.  xxx is FCNTL for fcntl(),
    and FLOCK for flock().  New options have been added:
       - SYSVSEM to use System V style semaphores
       - PTHREAD to use POSIX threads (appears to work on Solaris only)
       - USLOCK to use IRIX uslock
    Based on timing various techniques, the following changes were made
    to the defaults:
       - Linux 2.x uses flock instead of fcntl
       - Solaris 2.x uses pthreads
       - IRIX uses SysV semaphores -- however multiprocessor IRIX boxes
           work far faster if you -DUSE_USLOCK_SERIALIZED_ACCEPT
 
 Since flock() is failing, perhaps it would be useful to modify conf.h to
 use
 fcntl() instead, or even pthread if your linuxpthread library is recent.
 
 Good Luck,
 Jeffrey
 
 Subject: Re: Bad file number: flock: LOCK_EX
    Date: Tue, 20 Oct 1998 11:46:49 -0400
    From: Lincoln Stein <lstein@cshl.org>
      To: jwb@tamu.edu
 
 pthread didn't work -- some constants aren't defined in pthread.h.
 I'll try the fcntl... or maybe upgrade to glibc, which is something I
 have to do anyway.
 
 Lincoln
 
 END OF QUOTED MESSAGES
 
 You can see that the problem has not gone away.
 
 Jeffrey
 -- 
 Jeffrey William Baker 
 jwb@tca.net

Mime
View raw message