August 2006 - Xymon - Xymon mailman web

check once an hour or day for a given check for a given host
by jjj863＠gmail.com 06 Aug '06

06 Aug '06

how can I specify check should be run once a day or hour (or any time period other than the default 5 minutes), at the check level, say for only one FILE or PROC entry out of several FILE/PROC entries ? I know I can change the frequency of checking for all.

3 2

[hobbit] Some more clear RRD duplicating-causing samples
by brodie＠mcw.edu 06 Aug '06

06 Aug '06

Buchan- you should really capture the incoming data segment while simultaneously watching the rrd-data.log file; that way you can 100% let Henrik know which data chunks are causing RRD issues. In my case, I only had to "watch" for 5 minutes to capture all the instances of duplicztes happening.... --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Buchan Milne [mailto:bgmilne at staff.telkomsa.net] Sent: Thursday, August 03, 2006 9:46 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Some more clear RRD duplicating-causing samples On Thursday 03 August 2006 16:28, Brodie, Kent wrote: > Henrik, here you go: Two more netstat data chunks that cause the > Duplication error (parsing issue?) in rrd/hobbit. > > My simple observation is the one thing these two hosts have in common is > virtual network interfaces, so instead of simpler items like eth0, eth1 > and so on, you have eth0, eth0:0, and so forth. Linux in this case, > but that would apply to solaris and so on as well. Just a > hunch................. > > @@data#98185|1154614736.024527|192.168.224.202||dunn.hmgc.mcw.edu|ifstat > data dunn,hmgc,mcw,edu.ifstat > linux > eth0 Link encap:Ethernet HWaddr 00:09:3D:13:DC:AB > inet addr:192.168.224.105 Bcast:192.168.224.255 > Mask:255.255.255.0 > inet6 addr: fe80::209:3dff:fe13:dcab/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:40318794 errors:0 dropped:0 overruns:0 frame:0 > TX packets:15352953 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2942042461 (2.7 GiB) TX bytes:21803054108 (20.3 GiB) > Interrupt:185 > > eth0:0 Link encap:Ethernet HWaddr 00:09:3D:13:DC:AB > inet addr:192.168.224.107 Bcast:192.168.224.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:185 > > eth0:1 Link encap:Ethernet HWaddr 00:09:3D:13:DC:AB > inet addr:192.168.224.160 Bcast:192.168.224.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:185 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:37737 errors:0 dropped:0 overruns:0 frame:0 > TX packets:37737 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:6042388 (5.7 MiB) TX bytes:6042388 (5.7 MiB) > > @@ > > > > > > > @@data#98366|1154614859.203728|192.168.224.202||clifford.hmgc.mcw.edu|if > stat > data clifford,hmgc,mcw,edu.ifstat > linux > eth0 Link encap:Ethernet HWaddr 00:09:3D:13:C8:78 > inet addr:192.168.224.104 Bcast:192.168.224.255 > Mask:255.255.255.0 > inet6 addr: fe80::209:3dff:fe13:c878/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:146220628 errors:0 dropped:0 overruns:0 frame:0 > TX packets:42544430 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:14048692258 (13.0 GiB) TX bytes:57506442876 (53.5 > GiB) > Interrupt:185 > > eth0:0 Link encap:Ethernet HWaddr 00:09:3D:13:C8:78 > inet addr:192.168.224.106 Bcast:192.168.224.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:185 > > eth0:1 Link encap:Ethernet HWaddr 00:09:3D:13:C8:78 > inet addr:192.168.224.159 Bcast:192.168.224.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:185 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1189289 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1189289 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:347179798 (331.0 MiB) TX bytes:347179798 (331.0 MiB) > > @@ Hmm, now that I think about this more carefully, this issue could be affecting me as well, resulting in some gaps in various rrd files (which I first thought might be affected by running everything via bbproxy and a rather complex setup). In our environment we typically use bonding/teaming (eg with eth0 connected to one switch, eth1 connected to another, with the two interfaces set up in passive failover, appearing as one "bond0" device). Then, to ensure access to the right networks, we have VLANs (eg bond0.4, bond0.54, bond0106) on top of the bonded interface. In some cases (HA setups), there are virtual interfaces (eg bond0.4:0)on top of the bonded interface. I've included sample ifstat contents (but, not necessarily at the time I've seen gaps in the rrds): [ifstat] bond0 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet6 addr: fe80::216:35ff:fe7e:8d59/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:1353358109 errors:0 dropped:0 overruns:0 frame:0 TX packets:1414161412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3466938915 (3.2 GiB) TX bytes:1361756811 (1.2 GiB) bond0.4 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet addr:192.168.211.41 Bcast:192.168.211.255 Mask:255.255.255.0 inet6 addr: fe80::216:35ff:fe7e:8d59/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:1353172280 errors:0 dropped:0 overruns:0 frame:0 TX packets:1414125729 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3747147076 (3.4 GiB) TX bytes:2930351274 (2.7 GiB) bond0.4:0 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet addr:192.168.211.203 Bcast:192.168.211.255 Mask:255.255.255.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 bond0.54 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet addr:192.168.12.18 Bcast:192.168.15.255 Mask:255.255.252.0 inet6 addr: fe80::216:35ff:fe7e:8d59/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:15562 errors:0 dropped:0 overruns:0 frame:0 TX packets:220 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:952935 (930.6 KiB) TX bytes:9408 (9.1 KiB) bond0.106 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet addr:192.168.106.68 Bcast:192.168.106.255 Mask:255.255.255.0 inet6 addr: fe80::216:35ff:fe7e:8d59/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:173127 errors:0 dropped:0 overruns:0 frame:0 TX packets:38287 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10379598 (9.8 MiB) TX bytes:3224568 (3.0 MiB) eth0 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet6 addr: fe80::216:35ff:fe7e:8d59/64 Scope:Link UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:1353358109 errors:0 dropped:0 overruns:0 frame:0 TX packets:1414161412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3466938915 (3.2 GiB) TX bytes:1361756811 (1.2 GiB) Interrupt:201 eth1 Link encap:Ethernet HWaddr 00:16:35:7E:8D:59 inet6 addr: fe80::216:35ff:fe7e:8d59/64 Scope:Link UP BROADCAST NOARP SLAVE MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:209 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1668785 errors:0 dropped:0 overruns:0 frame:0 TX packets:1668785 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:720576454 (687.1 MiB) TX bytes:720576454 (687.1 MiB) Regards, Buchan -- Buchan Milne ISP Systems Specialist B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)

3 2

[hobbit] hobbit-*.cfg syntax check
by brodie＠mcw.edu 06 Aug '06

06 Aug '06

Speaking of config files--- the "STOP" keyword in hobbit-alerts.cfg does not appear to be recognized, even though it's referenced in the documentation?!?!?!? --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, August 04, 2006 10:09 AM To: hobbit at hswn.dk Subject: Re: [hobbit] hobbit-*.cfg syntax check On Fri, Aug 04, 2006 at 10:40:12AM -0400, Gary B. wrote: > > Is there a syntax checker for the hobbit-*.cfg configuration files > (such as hobbit-clients.cfg)? I'm having an issue where some of the > rules I set up are apparently being ignored, or otherwise not working > as expected. I have a feeling it may be due to a syntax error, but > I'm not sure. The utilities that read the configuration file does complain if they find something they cannot understand. Look in the clientdata.log and page.log files (for hobbit-clients.cfg and hobbit-alerts.cfg, respectively). There are also "--dump-config" options for these two utilities, which will dump the configuration as they understand it. And complain about any errors. > I'm also curious, how does Hobbit deal with syntax errors in the > configuration files? Does it just skip over bad syntax, or stop > completely when it encounters an error? It tries to cope, ignoring the error and continuing with whatever bits of the config file it understands. Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

2 1

[hobbit] BUG: Glibc 'free(): invalid next size' in bbcmd on FC5
by henrik＠hswn.dk 05 Aug '06

05 Aug '06

On Fri, Aug 04, 2006 at 12:33:37PM -0700, Japheth J.C. Cleaver wrote: > > Running "bbcmd" after a clean install (default configuration, current > allinone patch) results in a glibc free() error. This is on Fedora > Core 5 with Glibc2.4-8. Running as "MALLOC_CHECK_=0 ./bbcmd" is a > temporary workaround. Thanks, this appears to be a 1-byte miscalculation of a buffer needed for one of the Hobbit environment variables. This patch should solve it. Regards, Henrik

1 0

monitor a series of files for absolute size (alert & trending)
by jjj863＠gmail.com 04 Aug '06

04 Aug '06

greetings, I need to monitor some os and db backup files for their sizes for alert based on absolute sizes as well as rrd trending. Does Hobbit do this now? I am running 4.2-RC-20060712 on CentOS 4.3/i386. A twist is the file names are timestamped (os-backup-YYYYMMDD-HHmm.star.gz). any suggestions/tricks? I thought of making a copy to a fixed name for monitoring, but it is kinda expensive due to the size of the backups themselves.

6 12

BUG: Glibc 'free(): invalid next size' in bbcmd on FC5
by cleaver＠redwire.net 04 Aug '06

04 Aug '06

Running "bbcmd" after a clean install (default configuration, current allinone patch) results in a glibc free() error. This is on Fedora Core 5 with Glibc2.4-8. Running as "MALLOC_CHECK_=0 ./bbcmd" is a temporary workaround. Attached is the STDERR output, an strace of bbcmd, and partial output from an "strace -vf" on a box where the config file it's trying to open exists. The problem *appears* to be lines 256-7 of lib/environ.c... (but I'm not certain). Regards, Japheth "J.C." Cleaver cleaver at redwire.net

1 0

[hobbit] hobbit-*.cfg syntax check
by gmbfly98＠gmail.com 04 Aug '06

04 Aug '06

I searched through my archives of email on this mailing list, and couldn't find an answer to my question... Is there a syntax checker for the hobbit-*.cfg configuration files (such as hobbit-clients.cfg)? I'm having an issue where some of the rules I set up are apparently being ignored, or otherwise not working as expected. I have a feeling it may be due to a syntax error, but I'm not sure. If there isn't already a way to check the syntax of these files, I think it would be a great feature to add. Similar to the named-checkconf scripts that are available for BIND. I'm also curious, how does Hobbit deal with syntax errors in the configuration files? Does it just skip over bad syntax, or stop completely when it encounters an error?

3 6

[hobbit] ack'ing with --no-pin
by brodie＠mcw.edu 04 Aug '06

04 Aug '06

Cool! I am having issues debugging.... I see a few lines in procmail.log, but that's all. Even with --debug, where does the hobbit mailack debug output go? -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, August 04, 2006 10:50 AM To: hobbit at hswn.dk Subject: Re: [hobbit] ack'ing with --no-pin On Fri, Aug 04, 2006 at 10:34:33AM -0500, Brodie, Kent wrote: > OK, that's how I thought it worked. One cool thing we ought to > think about- email-based acks? Could that be possible? The hobbit > server would have to be smtp-aware, and would have to forward > hobbit-addressed emails to a script. Have you checked the manpage for "hobbit-mailack" ? Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

[hobbit] Disk Usage Sorting
by neil.camp＠deca.mil 04 Aug '06

04 Aug '06

Thanks, works like a champ! -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, August 04, 2006 12:38 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Disk Usage Sorting On Fri, Aug 04, 2006 at 12:14:49PM -0400, Camp, Neil D. (ManTech) CTR wrote: > If I wanted to sort my disk usage by highest offender first, how would I > change the display to show that? Thanks. > > Example > > Filesystem 1024-blocks Used Available Capacity Mounted on > /dev/MAIN/Usr 1625002 1423491 201511 88% /usr > /dev/MAIN/Home 523910 458737 65173 88% /home > /dev/MAIN/Opt 2025176 1664282 360894 83% /opt > /dev/MAIN/Root 300769 142019 158750 48% / > /dev/MAIN/Stand 272812 48284 224528 18% /stand > /dev/MAIN/Var 1556049 235055 1320994 16% /var > /dev/MAIN/Tmp 491827 1987 489840 1% /tmp The easiest - at least for me - would be to change the "df" command being run from the client script to do the sorting. E.g. send the "df" output through "| tail +2 | sort -nr -k 5" and add a command before the current "df" command to just output the header line: "df|head -1" Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

Disk Usage Sorting
by neil.camp＠deca.mil 04 Aug '06

04 Aug '06

Hello, If I wanted to sort my disk usage by highest offender first, how would I change the display to show that? Thanks. Example Filesystem 1024-blocks Used Available Capacity Mounted on /dev/MAIN/Usr 1625002 1423491 201511 88% /usr /dev/MAIN/Home 523910 458737 65173 88% /home /dev/MAIN/Opt 2025176 1664282 360894 83% /opt /dev/MAIN/Root 300769 142019 158750 48% / /dev/MAIN/Stand 272812 48284 224528 18% /stand /dev/MAIN/Var 1556049 235055 1320994 16% /var /dev/MAIN/Tmp 491827 1987 489840 1% /tmp

2 1