Apache 'server-status' 404 not found + munin Apache stats

Discussion in 'Apache' started by salmedia, Oct 29, 2010.

  1. #1
    I am trying to solve a problem where Apache stats aren't displaying correctly in Munin. I've ran through quite a bit of checks and tests regarding Munin setup, but I think my issue is related to Apache, but my skill set there is lacking.

    first, system info:
    monitored server:
    CentOS 5.3 2.6.18-128.1.1.el5
    Apache/2.2.3


    "server-status" directive in httpd.conf (i've cross-compared this with another system that i did a successful parallel install of Munin on, correctly showing Apache stats, and the directive below is the same for both)

    ExtendedStatus On
    <Location /server-status>
            SetHandler server-status
            Order deny,allow
            Deny from all
     	Allow from 127.0.0.1
    </Location>
    Code (markup):
    ran "lynx http://localhost/server-status" -- got this >> HTTP/1.1 404

    taking a look at Apache access_log:

    127.0.0.1 - - [13/Oct/2010:07:00:47 -0700] "GET /server-status HTTP/1.0" 404 11237 "-" "Lynx/2.8.5rel.1 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.8e-fips-rhel5"

    mod_status is also loaded:
    grep "mod_status" /etc/httpd/conf/httpd.conf
    LoadModule status_module modules/mod_status.so

    i did notice that the ownership status on httpd.conf on this system is root.root.. whereas the system that is displaying correctly is apache.www -- not certain that this matters?? its got to be permission issue, but i'm not certain where the permissions are messed up.

    any thoughts on why the test of server-status is giving me a 404?


    it appears that the error_log doesn't get written to when I fire off the lynx lynx http://localhost/server-status request, only the access_log gets an entry:

    127.0.0.1 - - [14/Oct/2010:14:40:47 -0700] "GET /server-status HTTP/1.0" 404 11237 "-" "Lynx/2.8.5rel.1 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.8e-fips-rhel5"

    the /server-status directory is used on several hosts we have that accurately provide Apache stats back to Munin. So I feel confident saying this is the correct directory.

    But for troubleshooting sake, here is the error_log

    [Sun Oct 10 04:02:06 2010] [notice] Digest: generating secret for digest authentication ...
    [Sun Oct 10 04:02:06 2010] [notice] Digest: done
    [Sun Oct 10 04:02:06 2010] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
    [Sun Oct 10 07:03:17 2010] [error] [client 58.53.128.61] script not found or unable to stat: /var/www/cgi-bin/textenv.pl
    [Mon Oct 11 06:40:01 2010] [notice] caught SIGTERM, shutting down
    [Mon Oct 11 06:40:02 2010] [notice] SELinux policy enabled; httpd running as context root:system_r:httpd_t:s0
    [Mon Oct 11 06:40:02 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Mon Oct 11 06:40:02 2010] [notice] Digest: generating secret for digest authentication ...
    [Mon Oct 11 06:40:02 2010] [notice] Digest: done
    [Mon Oct 11 06:40:02 2010] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
    [Tue Oct 12 00:37:10 2010] [error] [client 99.192.173.66] Invalid URI in request GET HTTP/1.1 HTTP/1.1
    [Tue Oct 12 00:37:10 2010] [error] [client 99.192.173.66] File does not exist: /var/www/html/tiki/phpmyadmin
    [Tue Oct 12 00:37:10 2010] [error] [client 99.192.173.66] File does not exist: /var/www/html/tiki/phpMyAdmin
    [Wed Oct 13 04:15:30 2010] [notice] caught SIGTERM, shutting down
    [Wed Oct 13 04:15:31 2010] [notice] SELinux policy enabled; httpd running as context root:system_r:httpd_t:s0
    [Wed Oct 13 04:15:31 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Wed Oct 13 04:15:32 2010] [notice] Digest: generating secret for digest authentication ...
    [Wed Oct 13 04:15:32 2010] [notice] Digest: done
    [Wed Oct 13 04:15:32 2010] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
    [Wed Oct 13 04:29:51 2010] [notice] caught SIGTERM, shutting down
    [Wed Oct 13 04:29:52 2010] [notice] SELinux policy enabled; httpd running as context root:system_r:httpd_t:s0
    [Wed Oct 13 04:29:52 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Wed Oct 13 04:29:52 2010] [notice] Digest: generating secret for digest authentication ...
    [Wed Oct 13 04:29:52 2010] [notice] Digest: done
    [Wed Oct 13 04:29:52 2010] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
    [Wed Oct 13 04:32:24 2010] [notice] caught SIGTERM, shutting down
    [Wed Oct 13 04:32:25 2010] [notice] SELinux policy enabled; httpd running as context root:system_r:httpd_t:s0
    [Wed Oct 13 04:32:25 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Wed Oct 13 04:32:26 2010] [notice] Digest: generating secret for digest authentication ...
    [Wed Oct 13 04:32:26 2010] [notice] Digest: done
    [Wed Oct 13 04:32:26 2010] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
    [Wed Oct 13 21:20:58 2010] [error] [client 61.164.79.42] Invalid URI in request GET HTTP/1.1 HTTP/1.1
    [Wed Oct 13 21:21:15 2010] [error] [client 61.164.79.42] Invalid URI in request GET  HTTP/1.1
    Code (markup):
    any thoughts?
     
    salmedia, Oct 29, 2010 IP
  2. RHS-Chris

    RHS-Chris Well-Known Member

    Messages:
    1,007
    Likes Received:
    35
    Best Answers:
    10
    Trophy Points:
    150
    #2
    Does the other server have SeLinux running as well? I would suggest you turn it off, and then try.

    setenforce 0

    Chris
     
    RHS-Chris, Oct 29, 2010 IP
  3. gopkris2000

    gopkris2000 Peon

    Messages:
    86
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Could you please make your host configuration in /etc/hosts and then check your localhost 404 error.
     
    gopkris2000, Nov 2, 2010 IP