July 2006 - Xymon - Xymon mailman web

[hobbit] hobbit-clients.cfg
by henrik＠hswn.dk 06 Jul '06

06 Jul '06

On Thu, Jun 29, 2006 at 05:21:06PM -0400, Paul Moore wrote: > I'm having a problem with the hobbit-clients.cfg matching. The > documentations states the below but I'm experiencing it matching all lines. > > # Rules are evaluated from the top of this file and down, and the first > # matching rule is used. So you should put the specific rules first, and > # the generic rules last. This is actually misleading, as you've found out. It only applies to some of the client checks, not all of them since it wouldn't make sense for all. E.g. you do want to check all of the PROC settings for a host, not just the first one. I'll remove that comment from the default setup. > Here is the layout of my cfg file. > HOST=pdcd20-ic1 > PROC sm_server 9 9 RED > HOST=pdcd20-ic1 > PROC sm_server 5 5 RED What exactly is the point in having both of these rules ? I cannot tell if you want 5 or 9 sm_server processes. > HOST=%(c[ar]y|omz|rch|[pn]dc)(d20-ic[1-3]|d15-ic[3-5]|d[0-9]*-icb).* > PROC sm_server 2 2 RED This one also matches the pdcd20-ic1 host. So now there are three rules. > HOST=%(c[ar]y|omz|rch|[pn]dc)d[0-9]*-ic.* > PROC sm_server 1 1 RED And this one also matches pdcd20-ic1. That makes 4 rules total. > Process sm_server color red: Count=2, min=9, max=9 > Process sm_server color red: Count=2, min=5, max=5 > Process sm_server color green: Count=2, min=2, max=2 > Process sm_server color red: Count=2, min=1, max=1 > > -=-=- > As you can see it matches 4 different times. Yep ... Regards, Henrik

2 4

conn test periodically fails (fping execution code 99)
by bernie9998＠gmail.com 06 Jul '06

06 Jul '06

I tried upgrading hobbit from 4.1.2p1 to 4.2beta in hopes that it would either solve to problem, or atleast give a more telling error message. I had hoped this would help as this was listed in the notes under improvements for 4.2 beta: "If invoking fping failed, the error message was lost and only a "failed with exit code 99" error was reported. Changed so that the real cause of the error is reported in the bbtest-net log." Unfortunately, I am still getting the same exact "failed with exit code 99" error which is not helping me much in troubleshooting. Now, I've noticed something else of interest-- there seems to be a discrepancy in the version numbers for bbtest-net. Whenever fping is having no issue and bbtest is in a green status, the version is such: bbtest-net version 4.2-beta-20060605 However, when the fping fails (as it has been doing every 3 minutes or so), resulting in the bbtest status to turn yellow, I get this version: bbtest-net version 4.1.2p1 Is this a bug of the beta version of hobbit? Also, I've decided to try to use hobbitping as a replacement for fping, in hopes that perhaps that will solve my issue. Following the notes about how to use it, I replace the FPING line to the new destination, "$BBHOME/bin/hobbitping". However, I still get the same errors involving fping. It is as if the FPING line in the config file has absolutely no effect. Once again, any assistance in this issue will be greatly appreciated. -Brian On 6/30/06, Brian Bernstein <bernie9998 at gmail.com> wrote: > I am having some trouble with the hobbit monitoring server. > > While at first, it seemed to be functioning fine, a few minutes later, > the conn test failed across the board, and I received a yellow warning > under the bbtest column. > > The actual error message under the bbtest details stated: > Error output: > Execution of '/usr/sbin/fping -Ae' failed with error-code 99 > fping invocation failed: No such file or directory > > This is really weird, as the output of 'ls -l /usr/sbin/fping' shows > that it is in fact there, and all have permissions to execute it: > -rwsr-xr-x 1 root root 23600 Jun 2 2005 /usr/sbin/fping > > Not to mention that this problem seems to be periodic, and not continual. > The test will fail about every 3-5 minutes and then succeed about > another 3-5 minutes later, > only the repeat the process again. > > Has anyone else experienced this? > > I'm running this on Fedora Core 2, > hobbit version 4.1.2p1-1. > > Thanks in advance for your assistance. > > -Brian >

2 1

BBTest Error
by david＠stenhouseconsulting.com 06 Jul '06

06 Jul '06

Pardon my ignorance, but what does this mean? Error output: Timeout waiting for data from child, killing it Timeout waiting for data from child, killing it Child process terminated with signal 15 And can I apply it to my five year old when she is not doing what I ask? :) David Gilmore Consultant Stenhouse Consulting, LLC. 4 Traverse St Providence, RI 02906 401.453.6900 x12 401.454.7581 (fax)

2 2

No data in files or msgs
by lars.ebeling＠leopg9.no-ip.org 06 Jul '06

06 Jul '06

Todays (6/7) snapshot does not report any data in files or msgs Regards Lars Ebeling Hobbithobbyist http://leopg9.no-ip.org ¤ "The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt." --Bertrand Russell

2 2

[hobbit] enable/disable
by henrik＠hswn.dk 06 Jul '06

06 Jul '06

On Fri, Jun 30, 2006 at 08:20:05PM +0200, Torsten Richter wrote: > I got this stuff working. But it raises another question. > If I want to enable/disable a whole host on Hobbit from the command line > what do I have to do? > Is there something like $BBHOME/bin/bb $BBDISP "disable $HOST.all 5d > Maintenance" Yes: $BB $BBDISP "disable $HOST.* 5d Maintenance". There is a description of the Hobbit protocol in the bb(1) man-page, although this particular feature is not mentioned. I've updated the docs to include it. Regards, Henrik

1 0

FW: hobbit-clients.cfg
by sean.hennessey1＠verizonbusiness.com 05 Jul '06

05 Jul '06

Bump. Any ideas on this? -----Original Message----- From: Paul Moore [mailto:paul.moore at verizonbusiness.com] Sent: Thursday, June 29, 2006 5:21 PM To: hobbit at hswn.dk Cc: 'Sean Hennessey' Subject: hobbit-clients.cfg I'm having a problem with the hobbit-clients.cfg matching. The documentations states the below but I'm experiencing it matching all lines. # Rules are evaluated from the top of this file and down, and the first # matching rule is used. So you should put the specific rules first, and # the generic rules last. Here is the layout of my cfg file. HOST=pdcd20-ic1 PROC sm_server 9 9 RED HOST=pdcd20-ic1 PROC sm_server 5 5 RED HOST=%(c[ar]y|omz|rch|[pn]dc)(d14-icb2|d02-icb1).* PROC sm_server 4 4 RED HOST=%(c[ar]y|omz|rch|[pn]dc)(d20-icb1|(d15-icb[1-2])|d15-ic2|d02-ic1|d14-ic 1).* PROC sm_server 3 3 RED HOST=%(c[ar]y|omz|rch|[pn]dc)(d20-ic[1-3]|d15-ic[3-5]|d[0-9]*-icb).* PROC sm_server 2 2 RED HOST=%(c[ar]y|omz|rch|[pn]dc)d[0-9]*-ic.* PROC sm_server 1 1 RED DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97 -=-=- Here is what I get in test ../bin/hobbitd_client --test --debug --config=hobbit-clients. cfg Hostname (.=end, ?=dump, !=reload) []: ? PROC sm_server 9 9 red HOST=pdcd20-ic1 (line: 142) PROC sm_server 5 5 red HOST=pdcd20-ic1 (line: 144) PROC sm_server 4 4 red HOST=%(c[ar]y|omz|rch|[pn]dc)(d14-icb2|d02-icb1).* (line: 146) PROC sm_server 3 3 red HOST=%(c[ar]y|omz|rch|[pn]dc)(d20-icb1|(d15-icb[1-2])|d15-ic2|d02-ic1|d14-ic 1).* (line: 148 ) PROC sm_server 2 2 red HOST=%(c[ar]y|omz|rch|[pn]dc)(d20-ic[1-3]|d15-ic[3-5]|d[0-9]*-icb).* (line: 150) PROC sm_server 1 1 red HOST=%(c[ar]y|omz|rch|[pn]dc)d[0-9]*-ic.* (line: 152) UP 3600 -1 (line: 155) LOAD 5.00 10.00 (line: 156) DISK * 90 95 0 -1 red (line: 157) MEMREAL 100 101 (line: 158) MEMSWAP 50 80 (line: 159) MEMACT 90 97 (line: 160) Hostname (.=end, ?=dump, !=reload) [?]: pdcd20-ic1 Test (cpu, mem, disk, proc): proc ps command string: sm_server ps command string: sm_server ps command string: Process sm_server color red: Count=2, min=9, max=9 Process sm_server color red: Count=2, min=5, max=5 Process sm_server color green: Count=2, min=2, max=2 Process sm_server color red: Count=2, min=1, max=1 -=-=- As you can see it matches 4 different times. -=-=- Paul Moore V966-5159 MSO OSS Support -=-=-=-=-= Pinky, Are You Pondering What I'm Pondering? Well, I think so Brain but if Jimmy cracks corn and no one cares, why does he keep doing it?

1 0

problem compiling nightly snapshot
by adam.scheblein＠marquette.edu 05 Jul '06

05 Jul '06

Greetings, I just got the nightly snapshot and now I am getting the following error when trying to compile it: clientupdate.c: In function 'main': clientupdate.c:49: error: too few arguments to function 'drop_root_and_removesuid' make[1]: *** [clientupdate] Error 1 make[1]: Leaving directory '/home/hobbit/snapshot/client' make: *** [client] Error 2 Any ideas? Thanks, Adam

3 7

combotest bug - minus sign in hostname
by ndo＠unikservice.com 05 Jul '06

05 Jul '06

Argggg....help : (c92-dc200.dns||c92-dc220.dns||c92-dc221.dns) = (1-1||1-1||1-1) = 0 (c92-dc200.dns||c92-dc220.dns) = (1-1||1-1) = 0

2 2

LDAP Query - Base DN with spaces
by allan＠zandahar.net 05 Jul '06

05 Jul '06

We have been given an LDAP server to host for someone to use as a directory for another application and would like to do some tests on querying users and the response time rather than just testing that port 389 or 636 responds however the base dn has a space in it. I thought about putting it inside quotes but then wasnt sure how much of the string to put into quotes. Also the server requires a bind user name and password there is no anonymous, and 99.9% of the user names also have a space, in this case "ldap manager" Any suggestions would be welcome Cheers guys Allan

2 2

[hobbit] Hobbit vs Nagios
by bgmilne＠staff.telkomsa.net 04 Jul '06

04 Jul '06

On Monday 26 June 2006 17:33, Hubbard, Greg L wrote: > Well, that's that. > > My problem is that I have a few systems that I want to monitor that are > either old, or singletons, or both. In my particular case it is and > elderly one-of-a-kind system. > List the platform, and you may find someone with one who can provide you with binaries ... -- Buchan Milne ISP Systems Specialist B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)

1 0