Received: (qmail 20487 invoked by uid 2012); 11 Mar 1999 10:15:58 -0000 Message-Id: <19990311101558.20486.qmail@hyperreal.org> Date: 11 Mar 1999 10:15:58 -0000 From: Arjan van Staalduijnen Reply-To: A.vanStaalduijnen@alpha.nl To: apbugs@hyperreal.org Subject: mod_info won't work if access.conf and srm.conf are not available. X-Send-Pr-Version: 3.2 >Number: 4035 >Category: mod_info >Synopsis: mod_info won't work if access.conf and srm.conf are not available. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: feedback >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Mar 11 02:20:01 PST 1999 >Last-Modified: Fri Mar 12 02:10:01 PST 1999 >Originator: A.vanStaalduijnen@alpha.nl >Organization: >Release: 1.3.4 >Environment: Linux 2.0.36 >Description: I'm using an Apache configuration with only a httpd.conf-file which contains all configuration information. I'm using the mod_info-module to see what options are set up, but when I access the mod_info module it will report an error: 'No such file or directory: mod_info: couldn't open config file /etc/apache/conf/access.conf', which is true, since I'm not using that file. In the browser mod_info will report some information, but the information report is incomplete - it's not showing any settings, such as '', etc. There is no ResourceConfig and/or AccessConfig parameter active; this doesn't appear to be a problem to the functionality of the Apache. It appears mod_info is not able to handle a high-perf configuration. >How-To-Repeat: Create a single file for all configuration parameters, compile mod_info into the binary and configure the webserver to use mod_info. Request the URI for the mod_info-module (default /server-info) and check the output, both on your browser (the output is incomplete) and in the error_log. >Fix: mod_info should look at all information available (at this moment it doesn't appear to be able to completely parse the httpd.conf-file I'm using). >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: jim State-Changed-When: Thu Mar 11 18:24:29 PST 1999 State-Changed-Why: Do you have the "other" conf files set to /dev/null in your main config file? From: "Arjan van Staalduijnen" To: , Cc: Subject: Re: mod_info/4035: mod_info won't work if access.conf and srm.conf are not available. Date: Fri, 12 Mar 1999 11:07:49 +0100 -----Original Message----- From: jim@apache.org To: a.vanstaalduijnen@alpha.nl ; apache-bugdb@apache.org ; jim@apache.org Date: Friday, March 12, 1999 3:24 AM Subject: Re: mod_info/4035: mod_info won't work if access.conf and srm.conf are not available. >[In order for any reply to be added to the PR database, ] >[you need to include in the Cc line ] >[and leave the subject line UNCHANGED. This is not done] >[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! ] > > >Synopsis: mod_info won't work if access.conf and srm.conf are not available. > >State-Changed-From-To: open-feedback >State-Changed-By: jim >State-Changed-When: Thu Mar 11 18:24:29 PST 1999 >State-Changed-Why: >Do you have the "other" conf files set to /dev/null in your main config file? > Hi, Uhm, no, as the base configuration I used a configuration which came along with a distribution (I don't remember if it was a configuration with a Linux Debian package or if it was in the Apache-tar which I downloaded). This httpd.conf file had the ResourceConfig and AccessConfig-parameters commented out; no others entered. This didn't affect the functionality of the webserver - everything, except mod_info, seemed to work fine, so I figured all was okay. I've now changed these two parameters to /dev/null and yes, everything functions the way it should now. Thanks. I don't want to be a smartass, but I guess it is something to take into consideration for new releases. Judging the fact that mod_info is smart enough to recognize that it can't load the access.conf and srm.conf and the fact that it is able to handle a /dev/null for input, I guess it would not be a lot of work to make mod_info more resistant to configuration mistakes. At the moment it appears that mod_info goes into error if one step goes wrong, even when all information is available. Thanks for your support. Arjan van Staalduijnen >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [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! ]