problem displaying munin reports

[mottwsc]

I have a LEMP server (Centos 6.3) and have installed munin according to Slicehost Articles: Installing munin on CentOS. I am using the default location for html files ( /var/www/html/munin ). I made sure munin can write there: chown -R munin /var/www/html/munin.

When I go to mydomain.com/munin or mydomain.com/munin/index.html, I get a 404 Not Found error. I can see that there is an index file and many other files in var/www/html/munin, but I can't display them.

Can anyone suggest how to fix this?

Thanks.

[bsdtux]

couple of things. Can you post the User and Group from the /etc/httpd/conf/httpd.conf file? On my servers it is apache. Also can you post the output of

ls -al /var/www/html/

Could you also look through your httpd.conf file to ensure that it does not include other config files that might create a virtual host and place the munin directory on a different port for access. Like say using port 8080 instead of just using the standard port 80

[mottwsc]

bsdtux -

I am not using Apache, but instead Nginx. In the /etc/httpd/conf.d directory, there is only a munin.conf file, as the contents are:

# This file can be used as a .htaccess file, or a part of your apache
# config file.
#
# For the .htaccess file option to work the munin www directory
# (/var/www/html/munin) must have "AllowOverride all" or something close
# to that set.
#
# As a config file enclose it in <directory> like so:
# 
<directory /var/www/html/munin>

AuthUserFile /etc/munin/munin-htpasswd
AuthName "Munin"
AuthType Basic
require valid-user

# This next part requires mod_expires to be enabled.
#
# We could use <IfModule mod_expires> around here, but I want it to be
# as evident as possible that you either have to load mod_expires _or_
# you coment out/remove these lines.

# Set the default expiery time for files 5 minutes 10 seconds from
# their creation (modification) time.  There are probably new files by
# that time.

ExpiresActive On
ExpiresDefault M310

</directory>

The results of ls -al /var/www/html/ are:

total 12
drwxr-xr-x 3 root root 4096 Feb 23 20:56 .
drwxr-xr-x 3 root root 4096 Feb 23 20:56 ..
drwxr-xr-x 5 munin munin 4096 Feb 23 21:30 munin

Here is the Nginx config file (/etc/nginx/conf.d/default.conf):

server {
    listen       80;
    server_name  999.99.999.99 (IP masked);

    #charset koi8-r;
    #access_log  /var/log/nginx/log/host.access.log  main;

    location / {
        root   /usr/share/nginx/html;
        index index.php index.html index.htm;
    }

    error_page  404              /404.html;
    location = /404.html {
        root   /usr/share/nginx/html;
    } 

    # redirect server error pages to the static page /50x.html
    #
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   /usr/share/nginx/html;
    }

    # proxy the PHP scripts to Apache listening on 127.0.0.1:80
    #
    #location ~ \.php$ {
    #    proxy_pass   127.0.0.1; (had to remove http : // from the front end since I could not post this) 
    #}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    location ~ \.php$ {
        root           /usr/share/nginx/html;
        fastcgi_pass   127.0.0.1:9000;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
        include        fastcgi_params;
    }

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny  all;
    #}
}

Thanks for any suggestions.

[bsdtux]

I am reaching here because I have very little experience with nginx but could you tell me if there is anything in the file. AuthUserFile /etc/munin/munin-htpasswd. If so do you get the 404 error or do you get a login prompt. What happens if you go to just localhost/index.html or localhost/ in a browser?

If I get some time at work today I will spin up a virtual machine and do some testing on this. I will see if I can duplicate your results. Will also be good for me to get some hands on with nginx

[bsdtux]

Well I get the same error. While looking through the logs I see that the server is using 127.0.0.1. I am going to try and change that to the IP address of the server. I will give you an update on what I find.

[bsdtux]

Well I made some head way. If you change the munin-node.conf file and change the host to point to the IP address and then navigate to the servers ip with port 4949. You will also need to add some of the Allow regexp to say it is ok to receive connections from these hosts. here is an exmple from mine

allow ^172\.16\.108\.130$
allow ^172\.16\.108\.1$

The problem I am running into now is that I get the following output

# munin node at linuxTest.local
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
# Unknown command. Try cap, list, nodes, config, fetch, version or quit

[bsdtux]

Ok I was able to resolve it. what I had to do was change my root to point to /var/www/html and then restart nginx. I see that your root points to /usr/share/nginx/html which I would change to /var/www/html then restart nginx.

[mottwsc]

RESOLVED:

bsdtux - changing the path as you suggested did the trick - thanks so much for your assistance!