Project

General

Profile

Actions

action #176265

closed

o3: Cron <munin@ariel> test -x /usr/bin/munin-cron && /usr/bin/munin-cron

Added by dheidler about 1 month ago. Updated 25 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Start date:
2025-01-28
Due date:
% Done:

0%

Estimated time:

Description

[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/lib/munin/munin-html line 38.

Actions #1

Updated by tinita about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to tinita
Actions #2

Updated by tinita about 1 month ago

  • Status changed from In Progress to Feedback

I couldn't find much hints, except https://debianforum.de/forum/viewtopic.php?t=131809 where the OP says that setting host_name in munin-node.conf helped.
I did that now and set host_name openqa.opensuse.org in /etc/munin/munin-node.conf.

Actions #3

Updated by okurz about 1 month ago

  • Tags set to reactive work, o3
  • Target version set to Ready
Actions #4

Updated by okurz about 1 month ago

  • Tags changed from reactive work, o3 to reactive work, o3, alert
Actions #5

Updated by okurz about 1 month ago

  • Status changed from Feedback to Resolved

tinita applied changes that could improve the situation. Right now no problem resides. We will see if that alerts us again.

Actions #6

Updated by tinita 25 days ago ยท Edited

  • Status changed from Resolved to Workable
  • Assignee deleted (tinita)

Happened again today Date: Thu, 6 Feb 2025 09:55:22 +0000 (UTC). No idea why.
I think we can just ignore it, but it would be good to have an automatic way to ignore this and not receive an email.
See also https://github.com/munin-monitoring/munin/issues/1497 and https://web.archive.org/web/20200711220239/http://munin-monitoring.org/wiki/FAQ_no_graphs

Actions #7

Updated by tinita 25 days ago

  • Status changed from Workable to Feedback
  • Assignee set to tinita

I tried something else from that FAQ "Inconsistent names for the node on the master and on the node"

host_name ariel.suse-dmz.opensuse.org

maybe I just understood it the wrong way before.

Actions #8

Updated by tinita 25 days ago

Hmm. I tried something else now.
Maybe I hadn't restarted the service when I did the config change last time. So I set host_name openqa.opensuse.org again and then restarted munin-node.service.
Then:

telnet localhost 4949
Trying ::1...
Connected to localhost.
Escape character is '^]'.
# munin node at openqa.opensuse.org
quit
Connection closed by foreign host.

if I understand the FAQ correctly, this should now be enough to let munin believe the hostname is openqa.opensuse.org, which should be the displayed titles in the graphs.

Actions #9

Updated by tinita 25 days ago

  • Status changed from Feedback to Resolved

Being optimistic that this time it will work :)

Actions

Also available in: Atom PDF