July 2006 - Xymon - Xymon mailman web

[hobbit] process checks and user IDs
by gmbfly98＠gmail.com 25 Jul '06

25 Jul '06

I've looked through all the documentation, and can't find any information on how Hobbit processes the process check rules. I ask because we have some BB process check rules that check for user IDs in the ps output, rather than an actual process, and there's no real way of converting that into Hobbit. Also, the Solaris ps output doesn't include the full process name, so I can't check for the process that way either. Any suggestions?

2 1

Hobbitd_rrd status
by tschenk＠pironet-ndh.com 25 Jul '06

25 Jul '06

Hi all, Is it possible to get hobbitd_rrd to generate a status message when operating normally? With 4.2RC it generates a red status when it crashed (I tried some hacks ;), but no green status when it is restarted, so the status gets purple and has to be deleted manually. Regards, Thomas

1 0

exhost question
by billieperez＠gmail.com 25 Jul '06

25 Jul '06

Hello, Could someone let me know how I can use 2 different domain names when excluding hosts in the hobbit-alerts.cfg? Example: exhost=%(server).test.com %(server).abc.intra. I tried to use a comma and space between the 2 domain names but it isn't taking it. Thanks in advance for any info

4 7

Ports problem?
by rsmrcina＠wi.rr.com 25 Jul '06

25 Jul '06

I have the following in hobbit-clients.cfg: HOST=conn2 PORT LOCAL=:2387 STATE=LISTEN "TEXT=VSAM Redirector" Netstat reports the following (from the ports page for the conn2 host): Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:2387 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN tcp 0 0 192.168.201.8:23 192.168.201.4:1987 ESTABLISHED tcp 0 0 :::22 :::* LISTEN There is a 2387 in the LISTEN state. The status comes back as red and I can not figure out why. Both client and server are running the RC-20060712 code. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007

2 2

[hobbit] DNS resolution
by brodie＠mcw.edu 24 Jul '06

24 Jul '06

Aha! Ok, thanks. I made the mistake of running that manually, and it kind of short circuited every CONN test out there on the running server. Oops. More pager batteries........................ --------------------------------------------------------- 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: Monday, July 24, 2006 3:56 PM To: hobbit at hswn.dk Subject: Re: [hobbit] DNS resolution On Mon, Jul 24, 2006 at 03:35:47PM -0500, Brodie, Kent wrote: > Hi- by the way, my cluster stuff is finally working the way I want. > Thanks for putting up with my ignorance on how the hobbitd and bbproxy > stuff co-exist (or don't)! > > In my bbtests column of my main server, I see: > > DNS statistics: > # hostnames resolved : 141 > # succesful : 136 > # failed : 5 > # calls to dnsresolve : 183 > > .... any idea what's the easiest way for me to discern "which" of my 183 > hosts are failing DNS resolution? The only way currently is to run bbtest-net with the --debug option, and grep the output for "DNS lookup failed". I've been asked before, so I really should add some way of easily finding this information, or at least provide a way of logging it. BTW, you don't have 183 hostnames - you have 141. The 183 is the number of times a hostname lookup was done, so some of them was via the cache that bbtest-net has. This is because the same hostname may be needed for multiple tests, e.g. if you use it in http url's that you test. Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

DNS resolution
by brodie＠mcw.edu 24 Jul '06

24 Jul '06

Hi- by the way, my cluster stuff is finally working the way I want. Thanks for putting up with my ignorance on how the hobbitd and bbproxy stuff co-exist (or don't)! In my bbtests column of my main server, I see: DNS statistics: # hostnames resolved : 141 # succesful : 136 # failed : 5 # calls to dnsresolve : 183 .... any idea what's the easiest way for me to discern "which" of my 183 hosts are failing DNS resolution? So far, very very cool. I'm using hobbit to monitor just boatloads of stuff. --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590

2 1

hobbitd keeps dying, cannot bind...
by brodie＠mcw.edu 24 Jul '06

24 Jul '06

Same cluster setup - the node I'm having all my issues with is my cluster head node- the one that's the server, and also the proxy server. I am having a devil of a time keeping hobbit running. Sometimes I can get it going... but it never seems to stay up for more than 5 minutes, and even after a full clean reboot, I can't get hobbitd to start at all. Here's my relevant log info: Hobbitlaunch.log: 2006-07-24 11:28:27 hobbitlaunch starting 2006-07-24 11:28:27 Loading tasklist configuration from /home/hobbit/server/etc/hobbitlaunch.cfg 2006-07-24 11:28:27 Loading hostnames 2006-07-24 11:28:27 Loading saved state 2006-07-24 11:28:27 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:27 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:27 Task hobbitd terminated, status 1 2006-07-24 11:28:32 Loading hostnames 2006-07-24 11:28:32 Loading saved state 2006-07-24 11:28:32 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:32 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:32 Task hobbitd terminated, status 1 2006-07-24 11:28:37 Loading hostnames 2006-07-24 11:28:37 Loading saved state 2006-07-24 11:28:37 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:37 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:37 Task hobbitd terminated, status 1 2006-07-24 11:28:42 Loading hostnames 2006-07-24 11:28:42 Loading saved state 2006-07-24 11:28:42 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:42 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:42 Task hobbitd terminated, status 1 2006-07-24 11:28:47 Loading hostnames 2006-07-24 11:28:47 Loading saved state 2006-07-24 11:28:47 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:47 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:47 Task hobbitd terminated, status 1 2006-07-24 11:28:52 Loading hostnames 2006-07-24 11:28:52 Loading saved state 2006-07-24 11:28:52 Setting up network listener on 0.0.0.0:1984 2006-07-24 11:28:52 Cannot bind to listen socket (Address already in use) 2006-07-24 11:28:52 Task hobbitd terminated, status 1 Bbproxy.log: 2006-07-24 11:28:27 bbproxy version 4.2-RC-20060712 starting 2006-07-24 11:28:27 Listening on 0.0.0.0:1984 2006-07-24 11:28:27 Sending to BBDISPLAY(s) 141.106.224.202:1984 2006-07-24 11:28:27 Sending to BBPAGER(s) 141.106.224.202:1984 Is there some conflict having a hobbit server and proxy going at once?

5 4

iostatcpu & iostatdisk graphs
by craig＠cookitservices.com 24 Jul '06

24 Jul '06

I have noticed in 4.2 RC there are iostat commands (hobbitclient-sunos.sh -> [iostatcpu] & [iostatdisk]) But there is no definition listed in hobbitgraph.cfg... Is this a "work-in-progress"? Thanks Craig Cook -- Systems Monitoring Consulting and Support Services http://www.cookitservices.com

7 6

[hobbit] inode client checking
by shea_greg＠emc.com 24 Jul '06

24 Jul '06

Hi, On Solaris8 use: /usr/bin/df -Fufs -oi, otherwise use GNU df: /usr/local/bin/df -I RH uses the same syntax as GNU HTH -Grs- -----Original Message----- From: Frédéric Mangeant [mailto:frederic.mangeant at steria.com] Sent: Monday, July 24, 2006 10:00 AM To: hobbit at hswn.dk Subject: Re: [hobbit] inode client checking Francesco Duranti a écrit : > Just a request (not for 4.2 that is in RC so no new feature i think :P) .... It will be possible to get a inode column for systems with the same logic that there's for disk check? > We are having some problems witha filesystem that at the moment get out of inode while having a good chunk of space and then monitoring of inode shuld not be too long to implement in the client/server side but could be a nice feature too have. > Hi I second this : on a few systems (like the Hobbit server itself), I install bb-inode.sh from Deadcat, but it needs a 'df' command which supports inode reporting. -- Frédéric Mangeant Steria EDC Sophia-Antipolis To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

help with dialup of modembank
by fduranti＠q8.it 24 Jul '06

24 Jul '06

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20060724/933a2eff/attach…>

2 1