Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We've installed munin monitoring on one of our servers. Generally it seems to be working well but occasionally, 4 times in 2 months to be exact, munin-cron has generated the following error:

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

On searching for this error I can only find issues where munin is not working at all, rather than the intermittent problem that we're facing.

Some help preventing this error or how to debug it would be much appreciated.

We're running CentOS 5.5, Munin 1.4.5 installed using yum.

share|improve this question
The error message is defined in, after checking the output of get_group_tree() for sanity. You may try upgrading your Munin install (to 1.4.6, or even 2.0, if possible), there are quite a few changes in this module recently:… . The 1.4.5 release is built from SVN revision 3627 (two years ago!) and the current revision of the file is 4579. – Georgi Hristozov Jan 19 '12 at 21:06
We upgraded to 1.4.7 but the error is still appearing – scarba05 Jun 9 '12 at 10:19
I have that problem too. Every night at around 03:00 I get the same email but munin is somehow working fine. Can't find any hint where it tells me the problem. Did you find an Answer to this? Upgrading to a newer version isn't an option. – user169906 Apr 17 '13 at 7:28

If you are deploying your munin configs via configuration management you are probably running into a timing issue where the config file is being created while the munin cron is trying to run.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.