- Xymon - Xymon mailman web

hobbitd status-board not available
by tlp-hobbit＠holme-pedersen.dk 22 Jun '05

22 Jun '05

Running Hobbit 4.0.4 on RHEL linux in a kinda special way. I have 2 BBNET servers, one server is also the BBDISPLAY server. On the BBNET server without display I am running hobbit basicly only bbnet process. On this host I am also running bbproxy for my production BBDISPLAY and my test BBDISPLAY (third seperate server). Now the problem started when I decided to "upgrade" the hobbit BBNET only server to also be a BBDISPLAY server. I did this by starting hobbit on port 1986 (--listen=172.17.110.20:1986) along with the bbdisplay/histry/lard etc processes and then add a third bbdisplay server to my bbproxy configuration (--bbdisplay=172.17.110.20:1986). Hobbitd.log and hobbitlaunch.log are fine - no errors - but on my "primary" BBDISPLAY I now have the above line as status. I tried to add --debug to the hobbitd and bbdisplay configurations in hobbitlaunch.cfg but this crashed. Tried to disable the HEARTBEAT in hobbitlaunch but this did not solve the problem. If I stop hobbit the state is written to the tmp/hobbit.chk file and started again has the saved state. If this was not enough the "new" BBDISPLAY is making the headlines but no hosts. :-( Any help is appresiated. BR Thomas

2 2

Redundant Hobbit Servers
by mlowery＠alliedtechgroup.com 21 Jun '05

21 Jun '05

I'm interested in knowing what everyone is doing for redundancy. I currently have 2 hobbit servers and each one performs the same tests as the other. I find this to be a bit wasteful and am looking for the active/passive type of configuration that has been talked about on this list before. This configuration works fine, except for alerting. In order to not be overwhelmed by messages, I only have one hobbit server performing the alerting task, the other only sends alerts on the other hobbit host. I have considered using the "depends=" test, but then I have to maintain two separate bb-hosts files, rather than copying and pasting from one to the other. Is there a better way than what I'm doing? My goal is to have both servers configured the same, as much as possible, and have only one of them at a time send me alerts. I'd love to know what you guys are doing to get around these limits. I could easily have missed something in the newest update that solves this problem, but I haven't seen it yet. Thanks for your thoughts on this subject. Michael

3 2

[hobbit] Redundant Hobbit Servers
by Scott.Kelley＠disney.com 21 Jun '05

21 Jun '05

We are moving to running all our monitoring services in (VMWare) virtual machines. The vm's are backed up each night to a NAS share. If the physical server dies, no big deal I can just start the vm on another host connected to the same SAN. If the SAN dies (unlikely), I can restore the vm from the backup on some other host. We also run Sitescope, which alerts us if BigBrother/Hobbit dies (and vice versa). -- Scott Kelley, Disney Enterprise IT Platform Services -----Original Message----- From: hobbit-return-2800-Scott.Kelley=disney.com at hswn.dk [mailto:hobbit-return-2800-Scott.Kelley=disney.com at hswn.dk] On Behalf Of Lowery, Michael Sent: Tuesday, June 21, 2005 9:13 AM To: hobbit at hswn.dk Subject: [hobbit] Redundant Hobbit Servers I'm interested in knowing what everyone is doing for redundancy. I currently have 2 hobbit servers and each one performs the same tests as the other. I find this to be a bit wasteful and am looking for the active/passive type of configuration that has been talked about on this list before. This configuration works fine, except for alerting. In order to not be overwhelmed by messages, I only have one hobbit server performing the alerting task, the other only sends alerts on the other hobbit host. I have considered using the "depends=" test, but then I have to maintain two separate bb-hosts files, rather than copying and pasting from one to the other. Is there a better way than what I'm doing? My goal is to have both servers configured the same, as much as possible, and have only one of them at a time send me alerts. I'd love to know what you guys are doing to get around these limits. I could easily have missed something in the newest update that solves this problem, but I haven't seen it yet. Thanks for your thoughts on this subject. Michael To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

[hobbit] only alert if X number of hosts are already in error
by blysik＠shutterfly.com 20 Jun '05

20 Jun '05

> My best suggestion would be to use the bbcombotest tool to define > a pseudo "host" with the combined status of your host "pool". > > E.g. if you're monitoring http on 5 hosts, you could define a > combination test like this: > > Pool1.http=(hostA.http+hostB.http+hostC.http+hostD.http+hostE.http)>3 > > That would give you a red alert if 3 or fewer hosts in the pool were > green. And you could then trigger an alert based on that test result. Pretty unwieldy when you have large pools of servers, however. I just started writing a smart paging script which will keep track of downed hosts and decide whether or not to page. One question I have so far is: Does hobbit wait for an alerting script to return before continuing to evaluate other rules? -- Bruce Z. Lysik <blysik at shutterfly.com> Operations Engineer The information contained in this message (including any attachments) may be confidential. This message (including any attachments) is intended to be read only by the recipient(s) to whom it is addressed. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Shutterfly by telephone at (650) 610-5200 and delete or destroy any copy of this message (including any attachments).

3 2

[hobbit] Hobbitd_history crashing
by dstuffle＠deltafaucet.com 20 Jun '05

20 Jun '05

henrik at hswn.dk wrote: > On Tue, Jun 14, 2005 at 10:59:31AM -0500, Stuffle, David > wrote: >> Hobbit 4.0.4 >> Fedora Core 3 >> >> My hobbitd_history has crashed several times in the past >> few weeks. It goes red with "Fatal signal caught" then >> it goes purple. I have core files in the server/tmp >> directory. Here is the debug output you have requested >> in a previous post. Thanks! >> >> #3 0x0804d5de in sigsegv_handler (signum=11) at >> sig.c:57 #4 <signal handler called> #5 0x0804a242 in >> main (argc=1, argv=0xfef4a724) at hobbitd_history.c:194 > > I guess this can happen if a "disable" message does not > provide any cause, i.e. "disable foo.test 180" > > Does this patch fix it for you ? > > > Regards, > Henrik Henrik, After applying the patch, I am still getting the crashes. Here is the core file output. Thanks -bash-3.00$ gdb bin/hobbitd_history tmp/core.27019 GNU gdb Red Hat Linux (6.1post-1.20040607.41rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `hobbitd_history'. Program terminated with signal 6, Aborted. Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 0x003ff7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) bt #0 0x003ff7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x0043f955 in raise () from /lib/tls/libc.so.6 #2 0x00441319 in abort () from /lib/tls/libc.so.6 #3 0x0804d5f6 in sigsegv_handler (signum=11) at sig.c:57 #4 <signal handler called> #5 nldecode (msg=0x804e926 "(No reason given)") at encoding.c:250 #6 0x0804a9ac in main (argc=1, argv=0xfeec01b4) at hobbitd_history.c:195 (gdb) ~~~~~~~~~~~~~~ David Stuffle dstuffle at deltafaucet.com Delta Faucet Company (317) 571-4301 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

1 0

what does the column "stop after" on "info page" mean ?
by xiao.xj＠neusoft.com 20 Jun '05

20 Jun '05

I am sorry for my first letter , I spell wrong word "DURATION >60" , what i mean indeed is "DURATION <60" . this is the correct one : I installed hobbit and find it is excellent! I was confused about the alert confiugre of "hobbit-alerts.cfg" , I configured the DURATION <60 ,I assume it will appear in the "stop after column " on the "info page", but I can't see it. Maybe I am wrong about the "stop after column" ,what does it mean ?

2 1

what does the column "stop after" on "info page" mean ?
by xiao.xj＠neusoft.com 20 Jun '05

20 Jun '05

I installed hobbit and find it is excellent! I was confused about the alert confiugre of "hobbit-alerts.cfg" , I configured the DURATION>60 ,I assume it will appear in the "stop after column " on the "info page", but I can't see it. Maybe I am wrong about the "stop after column" ,what does it mean ?

1 0

[hobbit] upgrade to 4.0.4, barrage of purples forhttp/smtp/dns queries
by blysik＠shutterfly.com 17 Jun '05

17 Jun '05

> > (I added an ntp check which wasn't showing up, and after I > stopped hobbit I noticed a few > > spawned ntpdate processes sticking around. Probably unrelated.) > > No, it's quite possible that you've found the real problem. > > Adding the ntp test causes bbtest-net to run "ntpdate". If > that command > hangs, bbtest-net will stall waiting for it to complete. So if ntpdate > never completes, your network tests will stop being updated because > it is waiting forever for this command to complete. That makes sense. What options does hobbit use for ntpdate to check an ntp server? I want to run it by hand and see what happens. -- Bruce Z. Lysik <blysik at shutterfly.com> Operations Engineer The information contained in this message (including any attachments) may be confidential. This message (including any attachments) is intended to be read only by the recipient(s) to whom it is addressed. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Shutterfly by telephone at (650) 610-5200 and delete or destroy any copy of this message (including any attachments).

6 6

Announcement: Hobbit client for z/VM and VM/ESA
by rsmrcina＠wi.rr.com 17 Jun '05

17 Jun '05

Hobbit is an open source network services monitor for Linux (it also runs on Linux for zSeries). This package runs in a virtual machine and reports on CPU Utilization, Paging, Page and Spool Utilization, running virtual machines and SFS Filepool and filespace utilization. The package is available at http://www.vmassist.com/rs_samples. If there are any questions, feel free to let me know. -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006

1 0

[hobbit] only alert if X number of hosts are already in error
by blysik＠shutterfly.com 17 Jun '05

17 Jun '05

> Something like > HOST=%(www.*).foo.com TEST=http COLOR=red COUNT>=5 > MAIL someone at foo.com > The "COUNT>=5" would then cause this rule to trigger only if there > were 5 or more hosts named www.*.foo.com, whose http tests are red. > You could even combine this with other criteria, say have a threshold of > 5 during the daytime, and 10 during off-hours. > I can foresee a problem in handling recovery-notifications for this kind > of alerts, but that's something I'll have to think about. > Would that be useful ? That would seem extremely useful. I was thinking about notifications as well, and my first thought was just to notify on every recovery (if you've selected RECOVERED). That way you would know if a single host kept doing a down/up/down/up/down/up type of thing. This would work alright in my environment since hosts that go into error for any length of time tend not to fix themselves anyways. :) -- Bruce Z. Lysik <blysik at shutterfly.com> The information contained in this message (including any attachments) may be confidential. This message (including any attachments) is intended to be read only by the recipient(s) to whom it is addressed. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Shutterfly by telephone at (650) 610-5200 and delete or destroy any copy of this message (including any attachments).

1 0