Nachdem man per Telnet geprüft hat ob die Clients da sind, prüft man den Munin-Master

Prüfen on munin-cron funktioniert:

sh-3.2# munin-cron

Can’t locate RRDs.pm in @INC (@INC contains: /opt/local/lib/perl5/site_perl/5.16.3/darwin-thread-multi-2level /opt/local/lib/perl5/site_perl/5.16.3 /opt/local/lib/perl5/vendor_perl/5.16.3/darwin-thread-multi-2level /opt/local/lib/perl5/vendor_perl/5.16.3 /opt/local/lib/perl5/5.16.3/darwin-thread-multi-2level /opt/local/lib/perl5/5.16.3 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl .) at /opt/local/lib/perl5/site_perl/5.16.3/Munin/Master/Utils.pm line 22.

BEGIN failed–compilation aborted at /opt/local/lib/perl5/site_perl/5.16.3/Munin/Master/Utils.pm line 22.

Compilation failed in require at /opt/local/lib/perl5/site_perl/5.16.3/Munin/Master/UpdateWorker.pm line 18.

BEGIN failed–compilation aborted at /opt/local/lib/perl5/site_perl/5.16.3/Munin/Master/UpdateWorker.pm line 18.

Compilation failed in require at /opt/local/lib/perl5/site_perl/5.16.3/Munin/Master/Update.pm line 17.

BEGIN failed–compilation aborted at /opt/local/lib/perl5/site_perl/5.16.3/Munin/Master/Update.pm line 17.

Compilation failed in require at /opt/local/lib/munin/munin-update line 13.

BEGIN failed–compilation aborted at /opt/local/lib/munin/munin-update line 13.

 

In diesem Fall passt die Version von rrdtools nicht zur eingesetzten perl-version.

Abhilfe:

sh-3.2# port installed rrdtool

The following ports are currently installed:

  rrdtool @1.4.7_5

  rrdtool @1.4.8_0

  rrdtool @1.4.9_1

  rrdtool @1.5.4_0 (active)

  rrdtool @1.5.5_0

port activate rrdtool @1.4.9_1

sh-3.2# munin-cron

This program will easily break if you run it as root as you are

…

sh-3.2#

 

Funktionierte dann.