April 2006 - Xymon - Xymon mailman web

display howto
by toaster＠imber.com 05 Apr '06

05 Apr '06

Greet, Looking for some help on how to setup two hobbit servers. First I will explain what I have and then what I am trying to accomplish. Currently. I have a rack of servers on the east coast with a hobbit server and a second rack of servers on the west coast with it's own hobbit server. Each hobbit server only reports on the servers in its rack. The two hobbit server do not know the other exists. What I would like to do is make the east coast hobbit server be the "master" server. Is there a way that I can have the west coast hobbit server send it's display to the east coast hobbit server. I would like to see both racks displayed on the east coast hobbit server display. I do not want the west coast clients to send data to the east coast hobbit server. Thanks, Lee

3 3

[hobbit] disable until connected on 4.2 Alpha -- I'm not finding it
by KauffmanT＠nibco.com 05 Apr '06

05 Apr '06

Gotit! Thanks a heap for this one! Tom -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Wednesday, April 05, 2006 3:38 PM To: hobbit at hswn.dk Subject: Re: [hobbit] disable until connected on 4.2 Alpha -- I'm not finding it On Wed, Apr 05, 2006 at 02:50:56PM -0400, Kauffman, Tom wrote: > I did a 'make install' of 4.2 Alpha on a system that had a functional > 4.03 RC1; I'm looking for how to 'disable until connected', but I'm not > seeing an option in the cgi. Is there something I need to copy by hand, > or was 'make install' not the correct update? "make install" is correct. But one of the files that need updating is also one that you may change yourself - and then upgrading might not work. Copy over the hobbitd/webfiles/maint_* files, and you should see a "until OK" checkbox next to the duration setting on the disable form. Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

1 0

disable until connected on 4.2 Alpha -- I'm not finding it
by KauffmanT＠nibco.com 05 Apr '06

05 Apr '06

I did a 'make install' of 4.2 Alpha on a system that had a functional 4.03 RC1; I'm looking for how to 'disable until connected', but I'm not seeing an option in the cgi. Is there something I need to copy by hand, or was 'make install' not the correct update? Or am I just being dense this week? (I just got 1.2 tons (US) of disk subsystem I need to migrate to in the next two weeks, so I'm a bit distracted . . .) TIA Tom Kauffman CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

2 1

[hobbit] Alert config issue or question -- 4.2 Alpha Release (and 4.03 Rc1)
by KauffmanT＠nibco.com 05 Apr '06

05 Apr '06

Well, I feel better, but then I'm still stumped. We had an instance last week where the telnet test failed for 21 minutes -- and no alerts went out. This box acts as a telnet server for half our remote-site scanners, so if we loose it, we have production people not working :-( What's the syntax for adding the duration on the test? I tried "bin/bbcmd hobbitd_alert --test whq-sapcon-1 telnet DURATION=361" while I was playing around, to no apparent avail (on the 4.2 alpha). Thanks! Tom -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Wednesday, April 05, 2006 12:09 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Alert config issue or question -- 4.2 Alpha Release (and 4.03 Rc1) On Wed, Apr 05, 2006 at 11:52:00AM -0400, Kauffman, Tom wrote: > I've a problem with my running 4.03RC1 (yeah, I know :-) that doesn't > seem to change with 4.2 Alpha. > 00018172 2006-04-05 11:42:36 Failed 'MAIL techsupt at localhost UNMATCHED DURATION>6m REPEAT=4h' (min. duration 0<360) > > So if I'm reading this correctly, my 'duration>6m' is being interpreted > as 'duration>6h'. The intent here is to require two failed tests before > paging. Where have I gone wrong? You're not reading it correctly. When you put DURATION>6m into the config, Hobbit internally converts that into 360 seconds. The output you see means that the current duration of the alert (0 seconds) - was less than the minimum duration required (360 seconds). I cannot recall if the test option in 4.0.3 allows you to specify the duration for the test-alert; with newer version you can, and then you'd see the the "0" change accordingly. Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

1 0

4.2 Alpha Release - hobbit_rrd crashing
by CHRIS.MORRIS＠RWEnpower.com 05 Apr '06

05 Apr '06

Hi, I have just built the hobbit 4.2-alpha-20060404 release server on an AIX 5.2 system. hobbit_rrd is crashing every 5 mins hobbitlaunch.log : Task rrddata terminated, status 1 rrd-data.log : xcalloc: Out of memory! Worker process died with exit code 393350, terminating Unfortunately I cannot analyse a coredump as the OS is complaining that the coredump is failing Running the rrddata channel component with debug produces :- 2006-04-05 15:41:49 RRD update param 00: 'rrdupdate' 2006-04-05 15:41:49 RRD update param 01: '/usr/local/hobbit2/data/rrd/tru2407/netstat.rrd' 2006-04-05 15:41:49 RRD update param 02: '-t' 2006-04-05 15:41:49 RRD update param 03: 'udpInDatagrams:udpOutDatagrams:udpInErrors:tcpActiveOpens:tcpPassiveOpens:t cpAttemptFails:tcpEstabResets:tcpCurrEstab:tcpOutDataBytes:tcpInInorderBytes :tcpInUnorderBytes:tcpRetransBytes:tcpOutDataPackets:tcpInInorderPackets:tcp InUnorderPackets:tcpRetransPackets' 2006-04-05 15:41:49 RRD update param 04: '1144248109:678267:32007:0:63839:27393:U:U:U:3749401639:2357005339:440214:16 688:6179403:2368554:59679:13' 2006-04-05 15:41:49 hobbitd_rrd: Got message 5 @@data#5|1144248109.287065|192.164.0.1||truxxxx|ifstat 2006-04-05 15:41:49 xcalloc: Out of memory! 2006-04-05 15:41:49 Worker process died with exit code 393350, terminating (ip address and server name modified to protect the innocent) Always seems to crash on the second message (ifstat) although all rrds are updated execpt for vmstat!! Regards, Chris **************************************************************************** The information contained in this email is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination or copying of the message or associated attachments is strictly prohibited. If you have received this email in error, please contact the sender by return email or call 01793 877777 and ask for the sender and then delete it immediately from your system.Please note that neither RWE npower nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any). *****************************************************************************

5 7

Alert config issue or question -- 4.2 Alpha Release (and 4.03 Rc1)
by KauffmanT＠nibco.com 05 Apr '06

05 Apr '06

I've a problem with my running 4.03RC1 (yeah, I know :-) that doesn't seem to change with 4.2 Alpha. With this alert_config set: HOST=%(whq-sapcon-1|whq-sapcon-2) EXSERVICE=msgs SCRIPT=/usr/local/hobbit/server/ext/pg/sms oracle_echelon SERVICE=telnet,svcs,procs color=RED DURATION>6m REPEAT=4h MAIL techsupt at localhost SERVICE=telnet,svcs,procs DURATION>6 REPEAT=4h MAIL techsupt at localhost UNMATCHED DURATION>6m REPEAT=4h I get this when running the test: 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 140 00018172 2006-04-05 11:42:36 *** Match with 'HOST=%(whq-sapcon-1|whq-sapcon-2) EXSERVICE=msgs' *** 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 141 00018172 2006-04-05 11:42:36 Failed 'SCRIPT=/usr/local/hobbit/server/ext/pg/sms oracle_echelon SERVICE=telnet,svcs,procs color=RED DURATION>6m REPEAT=4h' (min. duration 0<360) 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 142 00018172 2006-04-05 11:42:36 Failed 'MAIL techsupt at localhost SERVICE=telnet,svcs,procs DURATION>6 REPEAT=4h' (min. duration 0<360) 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 143 00018172 2006-04-05 11:42:36 Failed 'MAIL techsupt at localhost UNMATCHED DURATION>6m REPEAT=4h' (min. duration 0<360) So if I'm reading this correctly, my 'duration>6m' is being interpreted as 'duration>6h'. The intent here is to require two failed tests before paging. Where have I gone wrong? Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

3 2

[hobbit] Alert config issue or question -- 4.2 Alpha Release (and 4.03 Rc1)
by KauffmanT＠nibco.com 05 Apr '06

05 Apr '06

Nope - same result both ways (and the doc says minutes is the default, FWIW). Tom ________________________________ From: Charles Jones [mailto:jonescr at cisco.com] Sent: Wednesday, April 05, 2006 12:02 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Alert config issue or question -- 4.2 Alpha Release (and 4.03 Rc1) Not sure if this could be the problem, but your DURATION parameter in the MAIL line just says "DURATION>6". Maybe hours is the default, and you need to change it to DURATION>6m (like your second use of it on the last line)? -Charles Kauffman, Tom wrote: I've a problem with my running 4.03RC1 (yeah, I know :-) that doesn't seem to change with 4.2 Alpha. With this alert_config set: HOST=%(whq-sapcon-1|whq-sapcon-2) EXSERVICE=msgs SCRIPT=/usr/local/hobbit/server/ext/pg/sms oracle_echelon SERVICE=telnet,svcs,procs color=RED DURATION>6m REPEAT=4h MAIL techsupt at localhost SERVICE=telnet,svcs,procs DURATION>6 REPEAT=4h MAIL techsupt at localhost UNMATCHED DURATION>6m REPEAT=4h I get this when running the test: 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 140 00018172 2006-04-05 11:42:36 *** Match with 'HOST=%(whq-sapcon-1|whq-sapcon-2) EXSERVICE=msgs' *** 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 141 00018172 2006-04-05 11:42:36 Failed 'SCRIPT=/usr/local/hobbit/server/ext/pg/sms oracle_echelon SERVICE=telnet,svcs,procs color=RED DURATION>6m REPEAT=4h' (min. duration 0<360) 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 142 00018172 2006-04-05 11:42:36 Failed 'MAIL techsupt at localhost SERVICE=telnet,svcs,procs DURATION>6 REPEAT=4h' (min. duration 0<360) 00018172 2006-04-05 11:42:36 Matching host:service:page 'whq-sapcon-1:telnet:' against rule line 143 00018172 2006-04-05 11:42:36 Failed 'MAIL techsupt at localhost UNMATCHED DURATION>6m REPEAT=4h' (min. duration 0<360) So if I'm reading this correctly, my 'duration>6m' is being interpreted as 'duration>6h'. The intent here is to require two failed tests before paging. Where have I gone wrong? Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

1 0

performance tuning
by jeffnewman75＠gmail.com 05 Apr '06

05 Apr '06

All, I'm running Hobbit 4.1.2p1 on a Redhat AS 4 server. I currently have a number of server side scripts that post-process incoming test results. My concern is a high number of "1984" sockets in TIME_WAIT condition (upwords of 60 on the client at times) The clients are AIX boxes. Is there any way to tune Redhat/AIX/Hobbit to smooth this out? I know that doesn't sound very technical heh. Just looking for some ideas. Thanks, Jeff

4 5

Question about bbproxy and bbtest-net
by frederic.mangeant＠steria.com 05 Apr '06

05 Apr '06

Hi all I'd like to run a Hobbit server, which would have to do the following : - run network tests (bbtest-net) - act as a proxy for incoming BB status (bbproxy). The tests results of bbtest-net and bbproxy should be sent to another Hobbit server. Is this possible ? I can see how to run bbproxy, but not how to stop the main hobbitd daemon... Thanks in advance for any clue. -- Frédéric Mangeant Steria EDC Sophia-Antipolis

3 5

RE [hobbit] hobbit log monitor
by thomas.seglard.enata＠cnp.fr 05 Apr '06

05 Apr '06

Hi, thanks for your tools ! They're really cool and efficient... Sincerly, Thomas "Schwimmer, Eric E *HS" <EES2Y at hscmail.mcc.virginia.edu> a écrit sur 07/03/2006 22:09:47 : > > Hi all, > > Just finished my Hobbit log monitor; thought I'd share it all with you. > Since the hobbit-client currently doesn't support the msgs test, I > wrote this to eliminate the need for the old bb client. > > You can download it, along with my other Hobbit/BB tools from: > > http://www.nerdvana.org/eric/bbtools > > Let me know if it blows up on you, or anything. > > Cheers, > -Eric Schwimmer > Network Engineer > UVA HSCS Network Engineering > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > Ce message (et toutes ses pieces jointes eventuelles) est confidentiel et etabli a l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, CNP Assurances et ses filiales declinent toute responsabilite au titre de ce message, s'il a ete altere, deforme ou falsifie. ***** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither CNP Assurances nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

1 0