Bonjour,
J’ai quelques soucis avec munin depuis que j’ai installer/désinstallé sendmail & co (postfix, procmail, etc).
En fait, l’erreur est récurrente sur le net, et apparemment déjà corrigé.
Je reçois un mail dans /var/mail/root indiquant ceci :
[code]Return-Path: <munin@>
Received: from MASTER (localhost.localdomain [127.0.0.1])
by MASTER (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8H2g3bf019560
for root@MASTER; Mon, 17 Sep 2012 04:42:04 +0200
Received: (from munin@localhost)
by MASTER (8.14.3/8.14.3/Submit) id q8H2g3cf019559
for root; Mon, 17 Sep 2012 04:42:03 +0200
Date: Mon, 17 Sep 2012 04:42:03 +0200
Message-Id: 201209170242.q8H2g3cf019559@MASTER
From: root@ (Cron Daemon)
To: root@MASTER
Subject: Cron munin@MASTER if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi (failed)
Content-Type: text/plain; charset=UTF-8
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/var/lib/munin>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=munin>
[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
[/code]
Pour plus de détaille :
[code]munin@MASTER:/root$ bash -x /usr/bin/munin-cron
- /usr/share/munin/munin-update
- fgrep -v ‘*** attempt to put segment in horiz list twice’
- nice /usr/share/munin/munin-graph --cron
- /usr/share/munin/munin-limits
- wait
- nice /usr/share/munin/munin-html
[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 - exit 1
[/code]
J’ai regardé ici :
serverfault.com/questions/134748 … nf-problem
-> Visiblement il est pas plus avancé que moi
munin-monitoring.org/ticket/739
Mais l’erreur est déjà commenté avec une petite note : “FIX: this sometimes bugs:…”
La dernière procédure ici :
munin-monitoring.org/wiki/FAQ_no_graphs
Ce qui me donne :
2012/09/17 04:51:12 [DEBUG] Creating new lock file /tmp/munin-update.lock
2012/09/17 04:51:12 [DEBUG] Creating lock : /tmp/munin-update.lock succeeded
2012/09/17 04:51:12 [INFO]: Starting munin-update
2012/09/17 04:51:12 [DEBUG] Creating new lock file /tmp/munin-****.lock
2012/09/17 04:51:12 [DEBUG] Creating lock : /tmp/munin-****.lock succeeded
2012/09/17 04:51:12 [DEBUG] Reading from socket to ****: "# munin node at MASTER".
2012/09/17 04:51:12 TLS set to "disabled".
2012/09/17 04:51:12 [DEBUG] Negotiating capabilities
2012/09/17 04:51:12 [DEBUG] Writing to socket: "cap multigraph
".
2012/09/17 04:51:12 [DEBUG] Reading from socket to ****: "cap multigraph dirtyconfig".
2012/09/17 04:51:12 [DEBUG] Node says /cap multigraph dirtyconfig/
2012/09/17 04:51:12 [DEBUG] Writing to socket: "list MASTER
".
2012/09/17 04:51:12 [DEBUG] Reading from socket to ****: "".
2012/09/17 04:51:12 [WARNING] Config node **** listed no services for MASTER. Please see http://munin-monitoring.org/wiki/FAQ_no_graphs for further information.
2012/09/17 04:51:12 [DEBUG] Creating new lock file /tmp/munin-datafile.lock
2012/09/17 04:51:12 [DEBUG] Creating lock : /tmp/munin-datafile.lock succeeded
2012/09/17 04:51:12 [INFO]: Munin-update finished (0.03 sec)
Noté que rapport à la documentation, je n’ai pas la ligne de Warning
Et les différents support non officiel de munin :
sourceforge.net/mailarchive/foru … unin-users
Je passe les :
apt-get --purge munin munin-node & co
Du coup de désespère complètement.
Enfin pour couronner le tout, un “list” en telnet me renvois strictement rien :
[code]munin@MASTER:/root$ telnet 127.0.0.1 4949
Trying 127.0.0.1…
Connected to 127.0.0.1.
Escape character is ‘^]’.
munin node at MASTER
list
quit
Connection closed by foreign host.
[/code]
Avez-vous déjà été confronté à ce genre d’ennui ?
Merci d’avance pour vos lumière.
