Re: munin showing stange info

2011-12-06 Thread Bonno Bloksma

Hi Bob,


The ip_ plugin suggests ip addresses based on rules in your iptables.
You can run:

$ sudo munin-run --servicedir=/usr/share/munin/plugins ip_ suggest

to see what IPs it's suggesting. If they look odd, perhaps check your
firewall.

Ok, it is indeed suggesting I track that ip number, but I do not
want to track any ip-number. SO I probably just need to remove that
link.


Yes.  Removing that symlink would be fine.


Ok, did that.

[]

The munin-node package runs a postinst script when it is installed.
That postinst script runs 'munin-node-configure --shell' and saves the
output to a temporary file.  The --shell option causes it to produce
shell commands instead of table output.  Then it feeds that file of
shell commends to a shell.  You can do the same if you like.

 munin-node-configure --shell --remove-also  munin-plugins.sh

Then review the file munin-plugins.sh for what it wants to do.  Edit
as you like.  Then run it.

 sh ./munin-plugins.sh


Thanks, that is what I was looking for. Now that you explain it, it's easy. ;-)

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/a29d4afb5f284c0f84b987a905fd4...@staf.tio.nl



Re: munin showing stange info

2011-12-05 Thread Bonno Bloksma

From: Darac Marjal mailingl...@darac.org.uk

Hello Darac,

[]

The ip_ plugin suggests ip addresses based on rules in your iptables.
You can run:

$ sudo munin-run --servicedir=/usr/share/munin/plugins ip_ suggest

to see what IPs it's suggesting. If they look odd, perhaps check your
firewall.


Ok, it is indeed suggesting I track that ip number, but I do not want to track any ip-number. SO I 
probably just need to remove that link.



And why am I seeing only stats for eth1 and eth3? What happened to eth0, eth2 
and eth5?


The if_ and if_err_ plugins look in /proc/net/dev for interfaces to
monitor. Perhaps those devices weren't there when you ran suggest?


Well here is the kicker, *I* never ran munin-node-configure suggest, I assume that was what the 
default munin-node script did when it was started for the first time.


[.]


To see what plugins may be suitable for your system, run:

$ sudo munin-node-configure --suggest

For more details, you might want to start reading here:
http://munin-monitoring.org/wiki/munin-node-configure


I have read that page and a lot is clear now but is there a way to simply have munin-node run 
the scrip that set up the pugins for the first time based on what is there now? I have been unable 
to find how to do that. When I run munin-node-configure I just get a screen full of options with 
yes/no, I cannot change anything. The same with the suggest option.
The wiki page suggests I create/remove a lot of symlinks by hand, which I could do if most of the 
default values are wrong, but they are not.
I would very much like to know how to symply have all/most symlinks created by default and then edit 
the result where needed.


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/f22dec3fd7c44c038170154d22b47...@staf.tio.nl



Re: munin showing stange info

2011-12-05 Thread Bob Proulx
Bonno Bloksma wrote:
 Darac Marjal
 The ip_ plugin suggests ip addresses based on rules in your iptables.
 You can run:
 
 $ sudo munin-run --servicedir=/usr/share/munin/plugins ip_ suggest
 
 to see what IPs it's suggesting. If they look odd, perhaps check your
 firewall.
 
 Ok, it is indeed suggesting I track that ip number, but I do not
 want to track any ip-number. SO I probably just need to remove that
 link.

Yes.  Removing that symlink would be fine.

 To see what plugins may be suitable for your system, run:
 $ sudo munin-node-configure --suggest
 For more details, you might want to start reading here:
 http://munin-monitoring.org/wiki/munin-node-configure
 
 I have read that page and a lot is clear now but is there a way
 to simply have munin-node run the scrip that set up the pugins for
 the first time based on what is there now? I have been unable to
 find how to do that. When I run munin-node-configure I just get a
 screen full of options with yes/no, I cannot change anything. The
 same with the suggest option.

The munin-node package runs a postinst script when it is installed.
That postinst script runs 'munin-node-configure --shell' and saves the
output to a temporary file.  The --shell option causes it to produce
shell commands instead of table output.  Then it feeds that file of
shell commends to a shell.  You can do the same if you like.

  munin-node-configure --shell --remove-also  munin-plugins.sh

Then review the file munin-plugins.sh for what it wants to do.  Edit
as you like.  Then run it.

  sh ./munin-plugins.sh

Note that munin-node-configure will suggest *changes* to your existing
/etc/munin/plugins directory.  If it likes what is there then that
script file that it creates will be empty.  If you were to remove all
of the old symlinks then it would suggest all new ones.  If you
manually add new symlinks there that outside what it wants then it
will create 'rm' suggestions.

 The wiki page suggests I create/remove a lot of symlinks by hand,
 which I could do if most of the default values are wrong, but they
 are not.

If most of them are okay and you just want to add or remove one or
another then I don't understand why you wouldn't just add or remove
one or another?

 I would very much like to know how to symply have all/most symlinks
 created by default and then edit the result where needed.

Perhaps the easiest solution for you would be to purge the package
first and then install it again.  Having purged it all of the old
configuration will be gone.  Installing it again will run the
munin-node postinst script, which runs the munin-node-configure
script.

  # dpkg --purge munin-node
  # apt-get install munin-node

Bob


signature.asc
Description: Digital signature


munin showing stange info

2011-11-22 Thread Bonno Bloksma

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



Re: munin showing stange info

2011-11-22 Thread Darac Marjal
On Tue, Nov 22, 2011 at 03:41:30PM +0100, Bonno Bloksma wrote:
 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. :-(

The ip_ plugin suggests ip addresses based on rules in your iptables.
You can run:

$ sudo munin-run --servicedir=/usr/share/munin/plugins ip_ suggest

to see what IPs it's suggesting. If they look odd, perhaps check your
firewall.

 And why am I seeing only stats for eth1 and eth3? What happened to eth0, eth2 
 and eth5?

The if_ and if_err_ plugins look in /proc/net/dev for interfaces to
monitor. Perhaps those devices weren't there when you ran suggest?

 
 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?

When munin is installed, it installs what seem like suitable plugins.
You are free, though to add or remove symlinks to /etc/munin/plugins as
you see fit.

To see what plugins may be suitable for your system, run:

$ sudo munin-node-configure --suggest

For more details, you might want to start reading here:
http://munin-monitoring.org/wiki/munin-node-configure

-- 
Darac Marjal


signature.asc
Description: Digital signature