Received: (qmail 5904 invoked by uid 501); 8 Jun 2000 20:33:20 -0000 Message-Id: <20000608203320.5903.qmail@locus.apache.org> Date: 8 Jun 2000 20:33:20 -0000 From: Mohan Khurana Reply-To: mohan@razorfish.com To: submit@bugz.apache.org Subject: logs stored on NFS do not get written X-Send-Pr-Version: 3.110 >Number: 6167 >Category: mod_log-any >Synopsis: logs stored on NFS do not get written >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Jun 08 13:40:02 PDT 2000 >Closed-Date: Thu Jun 08 17:27:41 PDT 2000 >Last-Modified: Thu Jun 08 17:27:41 PDT 2000 >Originator: mohan@razorfish.com >Release: 1.3.12 >Organization: >Environment: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Linux 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown >Description: I have several virtual hosts set up, the web sites as well as the logs for those web sites are stored on a central server and loaded from this web server via NFS. I set the LockFile directive to /var/run/apache-lock. Apache writes data to the log file, as it should, then automatically takes it away from the file, returning the access_log to it's original state, resulting in a net writing of nothing to the log file. >How-To-Repeat: Put your logs for some virtual host on an NFS mounted filesystem, set the LockFile directive to /var/run/apache-lock. >Fix: I have no idea... >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Thu Jun 8 17:27:41 PDT 2000 State-Changed-Why: Writing logs over NFS is not supported and is not reliable. This is particularly true on Linux, which has certain very broken NFS "features". There is nothing we can or will do about this. You really should write to a local disk. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]