Received: (qmail 23762 invoked by uid 2012); 28 Aug 1998 23:42:07 -0000 Message-Id: <19980828234207.23761.qmail@hyperreal.org> Date: 28 Aug 1998 23:42:07 -0000 From: Ray Jong Reply-To: jong3@llnl.gov To: apbugs@hyperreal.org Subject: requests for server-status result in "NOT FOUND" error X-Send-Pr-Version: 3.2 >Number: 2923 >Category: mod_status >Synopsis: requests for server-status result in "NOT FOUND" error >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Aug 28 16:50:00 PDT 1998 >Last-Modified: Sun Sep 6 20:12:21 PDT 1998 >Originator: jong3@llnl.gov >Organization: >Release: 1.3.1 >Environment: SunOS skibuff 5.5.1 Generic_103640-20 sun4u sparc SUNW,Ultra-5_10 Server is running in standalone mode Standard SUN complier doing the standard build. >Description: When I try the URL http://skibuff.llnl.gov/server-status I get the response Not Found The requested URL /server-status was not found on this server. I have the following lines in the access.conf file: SetHandler server-status order deny,allow allow from all This looks to be set up just as the directed in the Apache Documentation, but I appear to be missing something. >How-To-Repeat: http://skibuff.llnl.gov/server-status >Fix: >Audit-Trail: From: Marc Slemko To: Ray Jong Cc: apbugs@hyperreal.org Subject: Re: mod_status/2923: requests for server-status result in "NOT FOUND" error Date: Fri, 28 Aug 1998 16:53:59 -0700 (PDT) On 28 Aug 1998, Ray Jong wrote: > Server is running in standalone mode > Standard SUN complier doing the standard build. > >Description: > When I try the URL http://skibuff.llnl.gov/server-status > I get the response > > Not Found > > The requested URL /server-status was not found on this server. Does anything appear in the error log? Do you have mod_status compiled into your server? From: "Raynard A. Jong" To: Marc Slemko Cc: apbugs@apache.org Subject: Re: mod_status/2923: requests for server-status result in "NOT FOUND" error Date: Fri, 28 Aug 1998 18:32:40 -0700 >On 28 Aug 1998, Ray Jong wrote: > >> Server is running in standalone mode >> Standard SUN complier doing the standard build. >> >Description: >> When I try the URL http://skibuff.llnl.gov/server-status >> I get the response >> >> Not Found >> >> The requested URL /server-status was not found on this server. > > >Does anything appear in the error log? > >Do you have mod_status compiled into your server? Here is the error log [Fri Aug 28 17:08:30 1998] [notice] httpd: caught SIGTERM, shutting down [Fri Aug 28 17:08:39 1998] [notice] Apache/1.3.1 (Unix) configured -- resuming normal operations [Fri Aug 28 17:08:49 1998] [warn] handler "server-status" not found for: /www/apache/share/htdocs/server-status [Fri Aug 28 17:08:49 1998] [error] File does not exist: /www/apache/share/htdocs/server-status I thought I had mod-status compiled into the serve, but it doesn't look like it is. To do the build, I edited the src/Configuration file to include AddModule modules/standard/mod_status.o then in the src parent directory (using the APACI build method), I did configure --prefix=/www/apache make make install This produced an executable httpd file in the /www/apache/sbin directory as desired. However, it looks like mod_status was not included. When I look in the src/module/standard directory, I do not see a mod_status.o file, and when I just rebuilt and watched the messages go by, I did not see a compilation of the mod_status.c file to create a mod_status.o Therefore, I concluded that the build using the APACI did not add in the mod_status module. I even tried manually editing the Configuration.apaci file to include mod_status, but that did not include it into the executable. I tried again using the Configuration.tmpl method from the src directory. The difference this time is that in the src directory, I again edited the src/Configuration file to include AddModule modules/standard/mod_status.o Then I did: ./Configure make This appeared to compile the mod_status module, as I saw it get compiled while building the executable that is made in the src directory. However, I want to put the server root in a nonstandard place (/www/apache) . This build method assumes that the server root is /usr/local/apache and builds it into the httpd executable. When started up, this httpd file tries to read the config files from/usr/local/apache/conf/httpd.conf The APCI build method has a method for specifying the server root. I guess the solution to my problem is to figure out how to make the Configuratiom.tmpl build method let me specify the server root. Is there a simple way that I am missing? I tried adding the line HTTP_ROOT = /www/apache to the Configuration file but this did not help Any suggestions would be appreciated. Thanks Ray #################################################### Ray Jong Lawrence Livermore National Laboratory P.O. Box 808 / L-637 Livermore, CA 94551-9900 Internet E-mail : rayjong@llnl.gov Telephone (with voice mail) : (925) 423-0498 FAX : (925) 424-6401 From: Marc Slemko To: "Raynard A. Jong" Cc: apbugs@apache.org Subject: Re: mod_status/2923: requests for server-status result in "NOT FOUND" error Date: Fri, 28 Aug 1998 18:45:55 -0700 (PDT) On Fri, 28 Aug 1998, Raynard A. Jong wrote: > I thought I had mod-status compiled into the serve, but it doesn't look > like it is. To do the build, I edited the src/Configuration file to > include > AddModule modules/standard/mod_status.o > > then in the src parent directory (using the APACI build method), I did > configure --prefix=/www/apache > make > make install No. Please go through the docs on apaci; you can _NOT_ edit your Configuration file if you expect to use it. Read the README.configure file for how to add modules using apaci. From: "Raynard A. Jong" To: Marc Slemko Cc: apbugs@apache.org Subject: Re: mod_status/2923: requests for server-status result in "NOT FOUND" error Date: Fri, 28 Aug 1998 18:51:45 -0700 > >Do you have mod_status compiled into your server? OK, I was finally able to build using the APACI method and put the executable where I want it. What I think is happening is that the APACI method uses src/Configuration.tmpl and ignores src/Configuration and src/Configuration.apaci I got it to work by making Configuration.tmpl include the mod_status module. I watched it get compiled and then yhe executable got made. Now I can see the server-status page. Ray #################################################### Ray Jong Lawrence Livermore National Laboratory P.O. Box 808 / L-637 Livermore, CA 94551-9900 Internet E-mail : rayjong@llnl.gov Telephone (with voice mail) : (925) 423-0498 FAX : (925) 424-6401 From: "Raynard A. Jong" To: Marc Slemko Cc: apbugs@apache.org Subject: Re: mod_status/2923: requests for server-status result in "NOT FOUND" error Date: Fri, 28 Aug 1998 19:04:28 -0700 >On Fri, 28 Aug 1998, Raynard A. Jong wrote: > >> I thought I had mod-status compiled into the serve, but it doesn't look >> like it is. To do the build, I edited the src/Configuration file to >> include >> AddModule modules/standard/mod_status.o >> >> then in the src parent directory (using the APACI build method), I did >> configure --prefix=/www/apache >> make >> make install > >No. Please go through the docs on apaci; you can _NOT_ edit your >Configuration file if you expect to use it. > >Read the README.configure file for how to add modules using apaci. OK, I see what I should have done. Thanks. Ray #################################################### Ray Jong Lawrence Livermore National Laboratory P.O. Box 808 / L-637 Livermore, CA 94551-9900 Internet E-mail : rayjong@llnl.gov Telephone (with voice mail) : (925) 423-0498 FAX : (925) 424-6401 State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Sun Sep 6 20:12:21 PDT 1998 State-Changed-Why: User config error. >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! ]