From apwww@hyperreal.org Thu Aug 21 15:02:53 1997 Received: (from apwww@localhost) by hyperreal.org (8.8.5/8.8.5) id PAA29117; Thu, 21 Aug 1997 15:02:53 -0700 (PDT) Message-Id: <199708212202.PAA29117@hyperreal.org> Date: Thu, 21 Aug 1997 15:02:53 -0700 (PDT) From: Justin Ashworth Reply-To: justin@ashworth.org To: apbugs@hyperreal.org Subject: Servers not starting correctly. Looks like file locking problem. X-Send-Pr-Version: 3.2 >Number: 1035 >Category: apache-api >Synopsis: Servers not starting correctly. Looks like file locking problem. >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Aug 21 15:10:01 1997 >Last-Modified: Sun Aug 24 15:28:09 PDT 1997 >Originator: justin@ashworth.org >Organization: >Release: 1.2.3 >Environment: SunOS www 5.5.1 Generic_103640-08 sun4u sparc SUNW,Ultra-1 gcc -O2 Proxy patch although it probably doesn't matter in my case. >Description: From error_log: ...... [Thu Aug 21 14:48:37 1997] fcntl: F_SETLKW: No record locks available [Thu Aug 21 14:48:37 1997] - Error getting accept lock. Exiting! [Thu Aug 21 14:48:37 1997] fcntl: F_SETLKW: No record locks available [Thu Aug 21 14:48:37 1997] - Error getting accept lock. Exiting! [Thu Aug 21 14:48:37 1997] fcntl: F_SETLKW: No record locks available [Thu Aug 21 14:48:37 1997] - Error getting accept lock. Exiting! [Thu Aug 21 14:48:38 1997] fcntl: F_SETLKW: No record locks available [Thu Aug 21 14:48:38 1997] - Error getting accept lock. Exiting! [Thu Aug 21 14:48:38 1997] fcntl: F_SETLKW: No record locks available [Thu Aug 21 14:48:38 1997] - Error getting accept lock. Exiting! ....... This caused the browser (Netscape Communicator 4.02) to just sit and wait with the "waiting for reply...." status. Only the root process started on the server...no child processes were spawned. Not all of our virtuals (the older-style virtuals, not HTTP/1.1) had this problem although all were using the same copy of the httpd. Some of the virtual servers had links to NFS-mounted drives. Server load increased nearly 10-fold as well. >How-To-Repeat: Try NFS-mounting a drive and having HTML documents exist on the other side of that mount. See if that will do it. >Fix: Nope, but I would love to know when you hear of one. Had this problem with 1.2.1 as well but due to the amount of bugs with that we just reverted back to 1.2.0. We are running 1.2.0 right now >Audit-Trail: State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Thu Aug 21 15:22:54 PDT 1997 State-Changed-Why: Try adding a: LockFile /var/tmp/accept.lock to your config files, assuming /var/tmp is not NFS mounted. The problem is probably that NFS locking isn't. From: Marc Slemko To: Justin Ashworth Subject: Re: apache-api/1035: Servers not starting correctly. Looks like file locking problem. Date: Thu, 21 Aug 1997 16:44:53 -0600 (MDT) On Thu, 21 Aug 1997, Justin Ashworth wrote: > > Would this go in the httpd.conf? I'd most likely want to give a unique > name to each lock file, right? It goes into whatever config file you want; any one of your main conf files. If you have multiple seperate copies of Apache running using different config files, each should use a different name. State-Changed-From-To: analyzed-closed State-Changed-By: marc State-Changed-When: Sun Aug 24 15:28:08 PDT 1997 State-Changed-Why: Assuming problem resolved. >Unformatted: