Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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
  • kernel 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

ran lynx http://localhost/server-status got

HTTP/1.1 404

taking a look at Apache access_log: - - [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

iptables is turned off also

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?

share|improve this question
Can you show us the exact entry in the config file that references /server-status –  malonso Oct 14 '10 at 0:42
This might be a case of virtualhosts and /server-status in different context. If you have virtualhosts enabled you need to add /server-status definition to same virtualhost configuration. –  anttiR Jan 8 '13 at 17:55
Yes, pls show the virtual host configuration, too –  Shâu Shắc Aug 21 '13 at 3:06
Without a configuration it's only a guess... isn't the configuration enclosed in <IfDefine STATUS>...</IfDefine>? –  Aleš Krajník Sep 20 '13 at 12:55
add comment

2 Answers

Do you know if the apache process has been restarted since the configuration files were updated? The apache process start time should be in the log file or look at time on process listing (ps -ef). Might be as simple as that.

Something else to look over are the various options to the httpd binary itself (http://httpd.apache.org/docs/2.2/programs/httpd.html). There is an option -D that can be used for this: "If -D DUMP_MODULES is set, all loaded modules will be printed.".

share|improve this answer
add comment

Try stoping and starting apache explicitly. server-status configuration to not start working after apache reload.

share|improve this answer
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.