From apwww@hyperreal.org Mon Aug 4 00:35:57 1997 Received: (from apwww@localhost) by hyperreal.org (8.8.5/8.8.5) id AAA15277; Mon, 4 Aug 1997 00:35:57 -0700 (PDT) Message-Id: <199708040735.AAA15277@hyperreal.org> Date: Mon, 4 Aug 1997 00:35:57 -0700 (PDT) From: Boyd Currey Reply-To: boydc@meridian.net.au To: apbugs@hyperreal.org Subject: The data under the section 'Current Configuration' does not show up on servers whose config files reside across NFS. X-Send-Pr-Version: 3.2 >Number: 963 >Category: mod_info >Synopsis: The data under the section 'Current Configuration' does not show up on servers whose config files reside across NFS. >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: analyzed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Aug 4 00:40:01 1997 >Originator: boydc@meridian.net.au >Organization: >Release: 1.2.1 >Environment: BSD/OS 2.1 fully patched. Compiled using shlicc and gcc. Tried shared and static libraries. BSD/OS xxx.xxx.xxx.xxx 2.1 BSDI BSD/OS 2.1 Kernel #4: Fri Jul 11 09:06:02 EST 1997 root@xxx.xxx.xxx.xxx:/src/sys/compile/WWW i386 >Description: The data under the section 'Current Configuration' does not show up on servers whose config files reside across NFS. Restarting the server either completely or via a HUP or USR1 signal fixes the problem for the short term. After a while the data 'disappears' again. Also cd'ing to the configuration directory where the config files reside fixes the problem. Seems that the NFS information becomes stale? Restarting the NFS processes on both client and server had no effect. Servers that read the config files from a local hard disk have not displayed this problem. The error message from error_log is as follows: [Mon Aug 4 17:23:32 1997] mod_info: couldn't open config file /var/www/conf/srm.conf [Mon Aug 4 17:23:32 1997] mod_info: couldn't open config file /var/www/conf/access.conf ..where /var/www/conf points to a configuration directory on another server. >How-To-Repeat: Installing Apache on a BSD/OS 2.1 system that reads the config files from another server across NFS, should repeat the problem. The files are readable at first, but after time (approx 1 hour) the above error occurs. >Fix: >Audit-Trail: State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Mon Aug 4 10:06:11 PDT 1997 State-Changed-Why: Are the config files readable by the user the child processes run as? This doesn't really sound like an Apache problem, but rather some odd NFS thing. From: Marc Slemko To: Apache bugs database Subject: Re: mod_info/963: The data under the section 'Current Configuration' does not show up on servers whose config files reside across NFS. (fwd) Date: Mon, 4 Aug 1997 19:32:23 -0600 (MDT) ---------- Forwarded message ---------- Date: Tue, 05 Aug 1997 10:49:39 +1000 From: Boyd Currey To: Marc Slemko Subject: Re: mod_info/963: The data under the section 'Current Configuration' does not show up on servers whose config files reside across NFS. Marc Slemko wrote: > > Synopsis: The data under the section 'Current Configuration' does not show up on servers whose config files reside across NFS. > > State-Changed-From-To: open-analyzed > State-Changed-By: marc > State-Changed-When: Mon Aug 4 10:06:11 PDT 1997 > State-Changed-Why: > Are the config files readable by the user the child > processes run as? The config files are world readable. They are initially shown by mod_info (ie, after a server restart or HUP/USR1, but after a while mod_info says that it couldn't open the files and reports it in the error log files, and nothing shows up under the 'Current Configuration' section on the info page. > This doesn't really sound like an Apache problem, but > rather some odd NFS thing. Perhaps, but then why are the files readable for a short while? Like I noted in the original report, if I log into the server that Apache is running on, and then 'cd' into the directory that holds the config files (over NFS) and then reload the info page the 'Current Configuration' data appears on the info page. If it is a deeply embedded NFS problem, then wouldn't the actual web pages not be delivered as well, as they too are loaded over NFS? It seems to be only mod_info that has this problem. Regards, Boyd ___________________________________________________________________________ Boyd Currey | OzEmail Ltd System Administrator | Unit 21, 39 Herbert St. boydc@ozemail.com.au | St. Leonards, Australia Phone: +61 2 9433 2352 | Phone: +61 2 9433 2400 >Unformatted: >Last-Modified: Mon Aug 4 10:06:11 PDT 1997