Hi,

For years we had Munin to display information about key values for our Debian Linux machines. If there was a new machine I would simply copy a munin-node.conf file from an existing server to the new server and I was prety much ready.
I now have a server that is showing strange values.

Looking at /etc/munin/plugins I see:
lrwxrwxrwx 1 root root 29 Nov 15 15:05 acpi -> /usr/share/munin/plugins/acpi
lrwxrwxrwx 1 root root 28 Nov 15 15:05 cpu -> /usr/share/munin/plugins/cpu
lrwxrwxrwx 1 root root 27 Nov 15 15:05 df -> /usr/share/munin/plugins/df
lrwxrwxrwx 1 root root 33 Nov 15 15:05 df_inode -> 
/usr/share/munin/plugins/df_inode
lrwxrwxrwx 1 root root 34 Nov 15 15:05 diskstats -> 
/usr/share/munin/plugins/diskstats
lrwxrwxrwx 1 root root 32 Nov 15 15:05 entropy -> 
/usr/share/munin/plugins/entropy
lrwxrwxrwx 1 root root 39 Nov 15 15:05 exim_mailqueue -> 
/usr/share/munin/plugins/exim_mailqueue
lrwxrwxrwx 1 root root 39 Nov 15 15:05 exim_mailstats -> 
/usr/share/munin/plugins/exim_mailstats
lrwxrwxrwx 1 root root 30 Nov 15 15:05 forks -> /usr/share/munin/plugins/forks
lrwxrwxrwx 1 root root 37 Nov 15 15:05 fw_conntrack -> 
/usr/share/munin/plugins/fw_conntrack
lrwxrwxrwx 1 root root 43 Nov 15 15:05 fw_forwarded_local -> /usr/share/munin/plugins/fw_forwarded_local
lrwxrwxrwx 1 root root 35 Nov 15 15:05 fw_packets -> 
/usr/share/munin/plugins/fw_packets
lrwxrwxrwx 1 root root 38 Nov 15 15:05 http_loadtime -> 
/usr/share/munin/plugins/http_loadtime
lrwxrwxrwx 1 root root 32 Nov 15 15:05 if_err_eth1 -> 
/usr/share/munin/plugins/if_err_
lrwxrwxrwx 1 root root 32 Nov 15 15:05 if_err_eth3 -> 
/usr/share/munin/plugins/if_err_
lrwxrwxrwx 1 root root 28 Nov 15 15:05 if_eth1 -> /usr/share/munin/plugins/if_
lrwxrwxrwx 1 root root 28 Nov 15 15:05 if_eth3 -> /usr/share/munin/plugins/if_
lrwxrwxrwx 1 root root 35 Nov 15 15:05 interrupts -> 
/usr/share/munin/plugins/interrupts
lrwxrwxrwx 1 root root 31 Nov 15 15:05 iostat -> /usr/share/munin/plugins/iostat
lrwxrwxrwx 1 root root 35 Nov 15 15:05 iostat_ios -> 
/usr/share/munin/plugins/iostat_ios
lrwxrwxrwx 1 root root 28 Nov 15 15:05 ip_217.114.99.194 -> 
/usr/share/munin/plugins/ip_
lrwxrwxrwx 1 root root 33 Nov 15 15:05 irqstats -> 
/usr/share/munin/plugins/irqstats
lrwxrwxrwx 1 root root 29 Nov 15 15:05 load -> /usr/share/munin/plugins/load
lrwxrwxrwx 1 root root 31 Nov 15 15:05 memory -> /usr/share/munin/plugins/memory
lrwxrwxrwx 1 root root 39 Nov 15 15:05 ntp_kernel_err -> 
/usr/share/munin/plugins/ntp_kernel_err
lrwxrwxrwx 1 root root 44 Nov 15 15:05 ntp_kernel_pll_freq -> /usr/share/munin/plugins/ntp_kernel_pll_freq lrwxrwxrwx 1 root root 43 Nov 15 15:05 ntp_kernel_pll_off -> /usr/share/munin/plugins/ntp_kernel_pll_off
lrwxrwxrwx 1 root root 35 Nov 15 15:05 ntp_offset -> 
/usr/share/munin/plugins/ntp_offset
lrwxrwxrwx 1 root root 35 Nov 15 15:05 open_files -> 
/usr/share/munin/plugins/open_files
lrwxrwxrwx 1 root root 36 Nov 15 15:05 open_inodes -> 
/usr/share/munin/plugins/open_inodes
lrwxrwxrwx 1 root root 34 Nov 15 15:05 processes -> 
/usr/share/munin/plugins/processes
lrwxrwxrwx 1 root root 33 Nov 15 15:05 proc_pri -> 
/usr/share/munin/plugins/proc_pri
lrwxrwxrwx 1 root root 29 Nov 15 15:05 swap -> /usr/share/munin/plugins/swap
lrwxrwxrwx 1 root root 32 Nov 15 15:05 threads -> 
/usr/share/munin/plugins/threads
lrwxrwxrwx 1 root root 31 Nov 15 15:05 uptime -> /usr/share/munin/plugins/uptime
lrwxrwxrwx 1 root root 30 Nov 15 15:05 users -> /usr/share/munin/plugins/users

Now why the heck is there suddenly an ip number like "ip_217.114.99.194" in there, it's not even an ip number on this server. :-(
And why am I seeing only stats for eth1 and eth3? What happened to eth0, eth2 
and eth5?

It looks like I have anly some things that were there when I was building the server. Is there a way to sort of reset the plugins dir and have it regenerated?

Bonno Bloksma



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/91b7f4b437fb478b9a3c7f5f9bd5f...@staf.tio.nl

Reply via email to