Munin-cron fails “Nothing to do”, possibly a munin.conf problem

munin

I have been working on this for a few hours now, and haven't yet been able to get munin to output the html files/generated graphs of resource usage on my CentOS 5.3 server.

Here are some things I run as the munin user, and the results:

/usr/share/munin/munin-update --nofork --debug

(above works fine, takes ~2.4 seconds to complete)

munin-run cpu

(And other options/plugins (besides 'cpu'), all work fine and give desired output)

munin-cron

Fails with:

[FATAL] There is nothing to do here, since there are no nodes with any plugins.  Please refer to http://munin-monitoring.org/wiki/FAQ_no_graphs at /usr/share/munin/munin-html line 38

I am wondering if, perhaps, the settings in my munin.conf file might be causing a problem. Here's the contents of that file (below):

bdir   /var/lib/munin/
htmldir /home/archdev/public_html/monitoring
logdir  /var/log/munin
rundir  /var/run/munin/
tmpldir /etc/munin/templates

[archstl.archstl.org]
        address 127.0.0.1
        use_node_name yes

Also, when I run the telnet localhost 4949 command, and list the node's plugins, it returns the default munin list… something seems to be wrong with the munin html creation process. 🙁

I'm running version 1.4.3.

Best Answer

I ended up installing munin (an older version) via the cPanel/WHM interface, and everything is working fine now. Strange...

Related Solutions

Linux – Having munin server monitoring problem: Graphs not being generated

It might be a permission pb....

Can you launch munin-run cpu as the same user that runs the munin-node process ?
If your system is SELinux/AppArmor enabled, you have to make sure that the processes launched with TTY are also allowed to launch the plugins.

... or something else : does it work with netcat ? Test with a nc localhost 4949. Netcat's line-ending handling is different than telnet's.

How to get a total bandwidth graph in munin

Yes, it is done on the server side by creating a combined graph.

Basically it is done by describing a new graph in munin server configuration (munin.conf) where the data graphed is the sum of two data sources :

[some.machine.boo]
    total_http_bw.graph_order total_received
    total_http_bw.graph_title HTTP traffic recived by machine1 and machine2
    total_http_bw.graph_vlabel Kb/s
    total_http_bw.total_received.label HTTP received traffic
    total_http_bw.total_received.sum \
            machine1.machine.boo:http_bw:received \
            machine2.machine.boo:http_bw:received

You can find an example of stacking (graphing two data sources one on the top of the other) on munin web site. If you want to graph the sum of two data sources you can use the total_received.sum function instead of total_received.stack.

[edit] ive added the stanzas required to have the net interface bandwidth to this answer, as it makes for a more complete answer to the original question (and I can't select 2 correct answers etc)

I had a lot of trouble getting the net interfaces to give up their values as a SUM, so here is the end result of lots of random trial and error changes to get a SUM line chart of multiple munin nodes

    [mydomain.com;aggregates]
    total_bandwidth.graph_args --base 1000 -l 0
    total_bandwidth.cdef 0
    total_bandwidth.graph_category Network
    total_bandwidth.graph_title Aggregated bandwidth
    total_bandwidth.graph_vlabel Bits/sec
    total_bandwidth.upload.label upload
    total_bandwidth.total.graph yes
    total_bandwidth.upload.sum \
    mybox1.mydomain.com:if_eth0.up \
    mybox2.mydomain.com:if_eth0.up
    total_bandwidth.upload.type COUNTER
    total_bandwidth.download.type COUNTER
    total_bandwidth.download.label download
    total_bandwidth.graph_order upload download
    total_bandwidth.total.graph no
    total_bandwidth.download.sum \
    mybox1.mydomain.com:if_eth0.down \
    mybox2.mydomain.com:if_eth0.down

I suspect a few of those directives are either unnecessary or plain wrong, but I hope it is a working starting point for anyone trying to achieve the same.

I also suspect that it works better if you explicitly make sure that all the hosts are in the aggregates group, eg mydomain.com even if your hosts are incorrectly named locally eg hostname -f is wrong

Related Topic