Help: Munin thinks it has nothing to do
So, setting up a centOS server, and getting Munin up & running.
No big deal, it should be done && done in less than 5 minutes nowadays, specially if it will be graphing only itself.
But, after the install (thru the EPEL repo) and starting the service, you access the page, and instead aof getting grafancy graphics, all you see is a lousy list of the files.
And then you start getting problem report emails that look like this:
[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 40
Those come from the cronjob that actually runs Munin.
If you look on the file /var/log/munin/munin-update.log, you'll find something like this:
2014/12/11 04:25:01 [INFO]: Starting munin-update
2014/12/11 04:25:01 [INFO] starting work in 1101 for localhost/127.0.0.1:4949.
2014/12/11 04:25:01 Failed to connect to node 127.0.0.1:4949/tcp : Connection refused
2014/12/11 04:25:01 [ERROR] Munin::Master::UpdateWorker failed to connect to node
2014/12/11 04:25:01 [INFO] Reaping Munin::Master::UpdateWorker. Exit value/signal: 20/0
2014/12/11 04:25:01 [INFO] No old data available for failed worker localhost;localhost. This node will disappear from the html web page hierarchy
2014/12/11 04:25:01 [INFO]: Munin-update finished (0.02 sec)
The workaround?
Edit the file /etc/munin/munin.conf from this:
# a simple host tree
[localhost]
address 127.0.0.1
use_node_name yes
to this:
# a simple host tree
[localhost.localdomain]
address 127.0.0.1
use_node_name yes
And then restart the service:
sudo /etc/init.d/munin-node restart
No big deal, it should be done && done in less than 5 minutes nowadays, specially if it will be graphing only itself.
But, after the install (thru the EPEL repo) and starting the service, you access the page, and instead aof getting grafancy graphics, all you see is a lousy list of the files.
And then you start getting problem report emails that look like this:
[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 40
Those come from the cronjob that actually runs Munin.
If you look on the file /var/log/munin/munin-update.log, you'll find something like this:
2014/12/11 04:25:01 [INFO]: Starting munin-update
2014/12/11 04:25:01 [INFO] starting work in 1101 for localhost/127.0.0.1:4949.
2014/12/11 04:25:01 Failed to connect to node 127.0.0.1:4949/tcp : Connection refused
2014/12/11 04:25:01 [ERROR] Munin::Master::UpdateWorker
2014/12/11 04:25:01 [INFO] Reaping Munin::Master::UpdateWorker
2014/12/11 04:25:01 [INFO] No old data available for failed worker localhost;localhost. This node will disappear from the html web page hierarchy
2014/12/11 04:25:01 [INFO]: Munin-update finished (0.02 sec)
The workaround?
Edit the file /etc/munin/munin.conf from this:
# a simple host tree
[localhost]
address 127.0.0.1
use_node_name yes
to this:
# a simple host tree
[localhost.localdomain]
address 127.0.0.1
use_node_name yes
And then restart the service:
sudo /etc/init.d/munin-node restart
Labels: CentOS 5, IT slaves, Linux, Monitoring, Munin, Programs
0 Comments:
Post a Comment
<< Home