Munin Error
Contents |
The content of this page has been moved to the Munin Guide Troubleshooting. This wiki page has therefore been set to "Read only" and later will be purged. This page lists some general troubleshooting for Munin. The examples show a munin-node agent running on 127.0.0.1; replace with other IP adresses as restart munin master you see fit. Is the munin-node process running on the agent node?
Munin Graphs Not Updating
Did you restart the munin-node process? Does the munin-node agent allow your munin master to contact it? Simple test: munin test plugin telnet localhost 4949 Hint: check the "allow" directive in munin-node.conf. Make sure any firewalls allow contact on destination port 4949. Try to telnet to the host where you run munin-node (127.0.0.1 or
Munin-cron
localhost if Munin master and munin-node is on the same system) on port 4949. The prompt should look something like this: # telnet localhost 4949 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. # munin node at [your server name] Does the above output give the same hostname should be expected in munin.conf? E.g. if munin.conf has the following entry: [foo.example.com] address foo.example.com munin configuration ...then telneting to the node should give you: # munin node at foo.example.com In particular, note that if you have fully qualified domain name (FQDN) in munin.conf, the server you're monitoring have to identify itself with FQDN as well. Does munin-node recognize any plugins? Try issuing the command list after telneting to the agent, and a (long) list of plugins should show. # telnet localhost 4949 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. # munin node at foo.example.com list open_inodes irqstats if_eth0 df uptime [...] If you're troubleshooting one particular plugin, test it on the agent with the command munin-run [plugin_name]. Do the directories specified by dbdir, htmldir, logdir and rundir have the correct permissions? (If you first ran munin as root, maybe they're not readable/writeable by the user that runs the cron job) Is munin-cron established as a cron controlled process, run as the Munin user? Does the output when running munin-update as the Munin user on the server node show any errors? Try running "munin-cron --debug > /tmp/munin-cron.debug" and checking the output file /tmp/munin-cron.debug See also FAQ_no_graphs Last modified at 2016-10-15T21:23:46+02:00 Last modified on 2016-10-15T21:23:46+02:00
and Administration Guide Powered by Trac 1.0.1 By Edgewall Software. Visit the Munin open project athttp://munin-monitoring.org/
installed on the munin node Did you restart munin-node? Inconsistent names for the node on the master and on the node I just read the above answer and there still aren't any graphs Node does not "allow" master to telnet listed no services for localhost on Debian Attention: Content of this page should be moved to the Munin-Guide --> Visit http://munin-monitoring.org/wiki/FAQ_no_graphs the Guide now. These FAQs have a separate page to make it easy to put http://stackoverflow.com/questions/9127802/munin-server-with-apache-you-dont-have-permission-to-access-munin-on-this-se links in error messages in Munin. See also Debugging_Munin On one host there are no graphs at all! This could be due to a number of problems. No plugins installed on the munin node Plugins that munin-node uses are usually to be found in /etc/munin/plugins (or /etc/opt/munin/plugins). If the directory is empty you will need to fill it. The directory should munin error have been filled by the package installation script or by you when you read the INSTALL instructions. You can fill it manually by symlinking to files in /usr/share/munin/plugins (or /opt/munin/lib/plugins). Or automatically by running munin-node-configure --shell | sh -x. This will which plugins it thinks are suitable on your system and make the symlinks. After making all the symlinks restart munin-node. Then wait 5 to 10 minutes before re-loading the munin web pages to see graphs. restart munin master Did you restart munin-node? Restarting munin-node is a rather heavy operation requiring running all the plugins as part of the startup. Therefore munin-node does not restart itself when the contents of the plugin directory changes. So after making a change in the plugin directory you need to restart munin-node. There is a bug in a good number of versions of the Debian (and Ubuntu) munin package that did not restart munin-node after running munin-node-configure. A manual restart is needed in this case. Then wait 5 to 10 minutes before re-loading the munin web pages to see graphs. Inconsistent names for the node on the master and on the node If your node has plugins and is restarted the next possibility is: it is likely because the server and the node have inconsistent name information for the node. Munin wants the host names to match between its configuration and what the munin-node calls itself. If you telnet to the node you'll be told the node name: $ telnet lorbanery 4949 Trying 10.1.0.2 Connected to lorbanery. Escape character is '^]'. # munin node at lorbanery.langfeldt.net quit Connection closed by foreign host. This means that this machine knows itself to be named lorbanery.langfeldt.net. If the name shown is not what you expected, you need to configure the correct name in munin-node.conf: host_name lorbanery.langfeldt.net On the master you configure lorbanery
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Munin server with apache - You don't have permission to access /munin on this server up vote 16 down vote favorite 6 On a fresh apache and munin server install when I to to domain.com/munin I get this error. Forbidden You don't have permission to access /munin on this server. for these directories I did a chown -R munin:munin dbdir /var/lib/munin htmldir /var/cache/munin/www logdir /var/log/munin rundir /var/run/munin What am I supposed to do with apache? I restated apache with /etc/init.d/apache restart but still get forbidden. I have made no changes to the apache config files from a fresh apache install. apache munin share|improve this question asked Feb 3 '12 at 11:17 user959129 May you list also file permissions on your www root especially on the munin directory in your www root –fyr Feb 3 '12 at 11:23 That should be the anser, user959129. –nbolton Jun 9 '12 at 13:42 1 @user959129 the url you have provided no longer works. It's a good idea to make an stackoverflow answer instead of pasting in urls. Particularly private blogs tend to be volatile. –Pylinux Apr 8 '14 at 15:53 There's an Ubuntu bug filed for the Apache 2.2 / 2.4 config file version of this problem. bugs.launchpad.net/ubuntu/+source/munin/+bug/… –Nelson Sep 29 '14 at 22:51 add a comment| 12 Answers 12 active oldest votes up vote 32 down vote Open the Munin Apache config file: vim /etc/munin/apache.conf change the the following lines: Order allow,deny Allow from localhost 127.0.0.0/8 ::1 Options None like so: Order allow,deny Allow from all Options FollowSymLinks SymLinksIfOwnerMatch Like @hamish noted in Apache 2.4 it need to be Require all granted Options FollowSymLinks SymLinksIfOwnerMatch Restarting Apache and Munin can