- Xymon - Xymon mailman web

Hobbit Installation Issue
by tanveers＠yahoo.com 07 Dec '08

07 Dec '08

Hello everyone, For the first time, I am trying to install Hobbit on my Ubuntu Linux Server. I followed the installation instructions provided on http://hobbitmon.sourceforge.net/ Every step went fine but when I started hobbit and typed in the hobbit address [ http://server-ip/hobbit/ ] in the browser, instead of getting the main page, I get the directory structure (see below)? What am I missing here? Please assist. Thank you! Index of /hobbit Name Last modified Size Description ________________________________ Parent Directory - gifs/ 13-Nov-2008 14:22 - help/ 13-Nov-2008 14:22 - html/ 13-Nov-2008 14:22 - menu/ 13-Nov-2008 14:22 - notes/ 13-Nov-2008 14:22 - rep/ 13-Nov-2008 14:22 - snap/ 13-Nov-2008 14:22 - wml/ 13-Nov-2008 14:22 - ________________________________ Apache/2.2.8 (Ubuntu) Server at x.x.x.x Port 80

15 43

monitoring patch status?
by Dan.McDonald＠austinenergy.com 04 Dec '08

04 Dec '08

I got hit up with the task of using xymon to monitor whether our windows servers are patched. I saw a plugin on deadcat that requires licensed software from shavlik.com, (and being over 4 years old, I have no idea if it works with bbwin, or if shavlik's api was still the same) but wondered if there were any other solutions out there. Minimum functionality is a list of applied patches that would show up on the client data link. For our linux boxes, I could probably just rpm -qa --last | head and check the date that an RPM was last installed - if it's more than a month, there is probably a problem... But I don't know enough about windows to come up with a simple solution for those boxes. -- Daniel J McDonald, CCIE #2495, CISSP #78281, CNX Austin Energy http://www.austinenergy.com

13 17

Hobbit bbtest-net crashing
by Vernon.Everett＠woodside.com.au 04 Dec '08

04 Dec '08

Hi Henrik You may recall, a while ago I posted a question to the list about "passive tests" no longer working. See thread from here http://www.hswn.dk/hobbiton/2008/10/msg00150.html Since then, it has happened a few times, but in all cases we have not had a chance to sit down and examine the core. Until Now. Below are our 5 most recent cores. And the corresponding entry in the bb-network.log file where available. (Not all generate the entry in the log file) Colin, our Linux man, and part-time C hacker, had this to say ---snip--- [root at las006 tmp]# gdb ~hobbit/server/bin/bbtest-net GNU gdb Red Hat Linux (6.5-37.el5_2.1rh) Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) l *0x42493a 0x42493a is in ares_free_hostent (ares_free_hostent.c:35). 30 free(host->h_name); 31 for (p = host->h_aliases; *p; p++) 32 free(*p); 33 free(host->h_aliases); 34 free(host->h_addr_list[0]); 35 free(host->h_addr_list); 36 free(host); 37 } (gdb) line 31: Make 'p' equal to the memory address of host->h_aliases, check that pointer p is not null and increment p line 32: free the memory pointed at by 'p' The problem here is that you check p then free p++. My C is quite rusty but I'd hazard a guess and say line 31 should read like: 31 for (p = host->h_aliases; *(p++);) You need to be checking the addess you're going to free, not the one next to it. Hope this a) makes sense and b) is vaguely accurate... ---snip--- I am no C expert, but looking at the grep output below, it does look like a memory issue. Cheers Vernon $ grep glibc bb-network.log *** glibc detected *** bbtest-net: malloc(): memory corruption: 0x000000001f9408c0 *** *** glibc detected *** bbtest-net: corrupted double-linked list: 0x000000001e44ec70 *** *** glibc detected *** bbtest-net: double free or corruption (out): 0x000000000a96dd20 *** *** glibc detected *** bbtest-net: double free or corruption (out): 0x00000000120ca000 *** *** glibc detected *** bbtest-net: corrupted double-linked list: 0x0000000007178440 *** *** glibc detected *** bbtest-net: free(): invalid next size (fast): 0x000000000fe240a0 *** *** glibc detected *** bbtest-net: munmap_chunk(): invalid pointer: 0x00000000164be700 *** *** glibc detected *** bbtest-net: munmap_chunk(): invalid pointer: 0x000000001981fe90 *** *** glibc detected *** bbtest-net: munmap_chunk(): invalid pointer: 0x000000000a005e90 *** *** glibc detected *** bbtest-net: corrupted double-linked list: 0x0000000009fef8c0 *** *** glibc detected *** bbtest-net: corrupted double-linked list: 0x00000000149dbf30 *** *** glibc detected *** bbtest-net: double free or corruption (out): 0x000000000e655e60 *** *** glibc detected *** bbtest-net: double free or corruption (out): 0x0000000002c46920 *** # gdb /usr/lib/hobbit/server/bin/bbtest-net -c core.31727 GNU gdb Red Hat Linux (6.5-37.el5_2.1rh) Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /usr/lib64/libldap-2.3.so.0...done. Loaded symbols for /usr/lib64/libldap-2.3.so.0 ** snip ** Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `bbtest-net --report --ping --checkresponse'. Program terminated with signal 6, Aborted. #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 #1 0x0000003db7a31bf0 in abort () from /lib64/libc.so.6 #2 0x000000000041d7e3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 0x0000000000424a57 in qcallback (arg=0x1bc753c0, status=0, abuf=0x7fff461c1c50 "\201\200", alen=140) at ares_query.c:108 #5 0x00000000004216c2 in end_query (channel=0x1bc5e4d0, query=0x1bcf41c0, status=0, abuf=0x0, alen=1176247376) at ares_process.c:627 #6 0x0000000000421ebd in process_answer (channel=0x1bc5e4d0, abuf=0x7fff461c1c50 "\201\200", alen=140, whichserver=0, tcp=<value optimized out>, now=1226882897) at ares_process.c:359 #7 0x00000000004221ff in ares_process (channel=0x1bc5e4d0, read_fds=0x7fff461c1f20, write_fds=0x7fff461c1ea0) at ares_process.c:273 #8 0x000000000040f064 in dns_queue_run (channel=0x1bc5e4d0) at dns.c:228 #9 0x000000000040f464 in flush_dnsqueue () at dns.c:259 #10 0x00000000004088e6 in main (argc=4, argv=0x7fff461c3428) at bbtest-net.c:2099 #11 0x0000003db7a1d8b4 in __libc_start_main () from /lib64/libc.so.6 #12 0x00000000004039e9 in _start () (gdb) quit *** glibc detected *** bbtest-net: double free or corruption (out): 0x000000000e655e60 *** ======= Backtrace: ========= /lib64/libc.so.6[0x3db7a71634] /lib64/libc.so.6(cfree+0x8c)[0x3db7a74c5c] bbtest-net[0x422424] bbtest-net[0x422515] bbtest-net[0x424a59] bbtest-net[0x4216c2] bbtest-net[0x421ebd] bbtest-net[0x4221ff] bbtest-net[0x40f064] bbtest-net[0x40f464] bbtest-net[0x4088e6] /lib64/libc.so.6(__libc_start_main+0xf4)[0x3db7a1d8b4] bbtest-net[0x4039e9] ======= Memory map: ======== 00400000-00430000 r-xp 00000000 fd:01 389476 /usr/lib/hobbit/server/bin/bbtest-net 00630000-00631000 rw-p 00030000 fd:01 389476 /usr/lib/hobbit/server/bin/bbtest-net 00631000-00637000 rw-p 00631000 00:00 0 00830000-00832000 rw-p 00030000 fd:01 389476 /usr/lib/hobbit/server/bin/bbtest-net 0e533000-0e6bf000 rw-p 0e533000 00:00 0 3224600000-3224638000 r-xp 00000000 fd:01 68061 /usr/lib64/libldap-2.3.so.0.2.15 3224638000-3224838000 ---p 00038000 fd:01 68061 /usr/lib64/libldap-2.3.so.0.2.15 3224838000-322483a000 rw-p 00038000 fd:01 68061 /usr/lib64/libldap-2.3.so.0.2.15 3366400000-3366443000 r-xp 00000000 fd:00 75879 /lib64/libssl.so.0.9.8b 3366443000-3366643000 ---p 00043000 fd:00 75879 /lib64/libssl.so.0.9.8b 3366643000-3366649000 rw-p 00043000 fd:00 75879 /lib64/libssl.so.0.9.8b 3368000000-3368125000 r-xp 00000000 fd:00 75876 /lib64/libcrypto.so.0.9.8b 3368125000-3368325000 ---p 00125000 fd:00 75876 /lib64/libcrypto.so.0.9.8b 3368325000-3368344000 rw-p 00125000 fd:00 75876 /lib64/libcrypto.so.0.9.8b 3368344000-3368348000 rw-p 3368344000 00:00 0 385c600000-385c63b000 r-xp 00000000 fd:00 75779 /lib64/libsepol.so.1 385c63b000-385c83b000 ---p 0003b000 fd:00 75779 /lib64/libsepol.so.1 385c83b000-385c83c000 rw-p 0003b000 fd:00 75779 /lib64/libsepol.so.1 385c83c000-385c846000 rw-p 385c83c000 00:00 0 385ca00000-385ca15000 r-xp 00000000 fd:00 75786 /lib64/libselinux.so.1 385ca15000-385cc15000 ---p 00015000 fd:00 75786 /lib64/libselinux.so.1 385cc15000-385cc17000 rw-p 00015000 fd:00 75786 /lib64/libselinux.so.1 385cc17000-385cc18000 rw-p 385cc17000 00:00 0 385ce00000-385ce8f000 r-xp 00000000 fd:01 68057 /usr/lib64/libkrb5.so.3.3 385ce8f000-385d08e000 ---p 0008f000 fd:01 68057 /usr/lib64/libkrb5.so.3.3 385d08e000-385d092000 rw-p 0008e000 fd:01 68057 /usr/lib64/libkrb5.so.3.3 385d600000-385d608000 r-xp 00000000 fd:01 68055 /usr/lib64/libkrb5support.so.0.1 385d608000-385d807000 ---p 00008000 fd:01 68055 /usr/lib64/libkrb5support.so.0.1 385d807000-385d808000 rw-p 00007000 fd:01 68055 /usr/lib64/libkrb5support.so.0.1 385da00000-385da24000 r-xp 00000000 fd:01 68056 /usr/lib64/libk5crypto.so.3.1 385da24000-385dc23000 ---p 00024000 fd:01 68056 /usr/lib64/libk5crypto.so.3.1 385dc23000-385dc25000 rw-p 00023000 fd:01 68056 /usr/lib64/libk5crypto.so.3.1 385de00000-385de2c000 r-xp 00000000 fd:01 68058 /usr/lib64/libgssapi_krb5.so.2.2 385de2c000-385e02c000 ---p 0002c000 fd:01 68058 /usr/lib64/libgssapi_krb5.so.2.2 385e02c000-385e02e000 rw-p 0002c000 fd:01 68058 /usr/lib64/libgssapi_krb5.so.2.2 3af4400000-3af440d000 r-xp 00000000 fd:01 68095 /usr/lib64/liblber-2.3.so.0.2.15 3af440d000-3af460d000 ---p 0000d000 fd:01 68095 /usr/lib64/liblber-2.3.so.0.2.15 3af460d000-3af460e000 rw-p 0000d000 fd:01 68095 /usr/lib64/liblber-2.3.so.0.2.15 3db7600000-3db761a000 r-xp 00000000 fd:00 75791 /lib64/ld-2.5.so 3db781a000-3db781b000 r--p 0001a000 fd:00 75791 /lib64/ld-2.5.so 3db781b000-3db781c000 rw-p 0001b000 fd:00 75791 /lib64/ld-2.5.so 3db7a00000-3db7b4a000 r-xp 00000000 fd:00 75797 /lib64/libc-2.5.so 3db7b4a000-3db7d49000 ---p 0014a000 fd:00 75797 /lib64/libc-2.5.so 3db7d49000-3db7d4d000 r--p 00149000 fd:00 75797 /lib64/libc-2.5.so 3db7d4d000-3db7d4e000 rw-p 0014d000 fd:00 75797 /lib64/libc-2.5.so 3db7d4e000-3db7d53000 rw-p 3db7d4e000 00:00 0 3db7e00000-3db7e02000 r-xp 00000000 fd:00 75840 /lib64/libdl-2.5.so 3db7e02000-3db8002000 ---p 00002000 fd:00 75840 /lib64/libdl-2.5.so 3db8002000-3db8003000 r--p 00002000 fd:00 75840 /lib64/libdl-2.5.so 3db8003000-3db8004000 rw-p 00003000 fd:00 75840 /lib64/libdl-2.5.so 3db8200000-3db8218000 r-xp 00000000 fd:01 67958 /usr/lib64/libsasl2.so.2.0.22 3db8218000-3db8418000 ---p 00018000 fd:01 67958 /usr/lib64/libsasl2.so.2.0.22 3db8418000-3db8419000 rw-p 00018000 fd:01 67958 /usr/lib64/libsasl2.so.2.0.22 3db8600000-3db8614000 r-xp 00000000 fd:01 67257 /usr/lib64/libz.so.1.2.3 3db8614000-3db8813000 ---p 00014000 fd:01 67257 /usr/lib64/libz.so.1.2.3 3db8813000-3db8814000 rw-p 00013000 fd:01 67257 /usr/lib64/libz.so.1.2.3 3db9a00000-3db9a09000 r-xp 00000000 fd:00 76086 /lib64/libcrypt-2.5.so 3db9a09000-3db9c08000 ---p 00009000 fd:00 76086 /lib64/libcrypt-2.5.so 3db9c08000-3db9c09000 r--p 00008000 fd:00 76086 /lib64/libcrypt-2.5.so 3db9c09000-3db9c0a000 rw-p 00009000 fd:00 76086 /lib64/libcrypt-2.5.so 3db9c0a000-3db9c38000 rw-p 3db9c0a000 00:00 0 3dba600000-3dba611000 r-xp 00000000 fd:00 76082 /lib64/libresolv-2.5.so 3dba611000-3dba811000 ---p 00011000 fd:00 76082 /lib64/libresolv-2.5.so 3dba811000-3dba812000 r--p 00011000 fd:00 76082 /lib64/libresolv-2.5.so 3dba812000-3dba813000 rw-p 00012000 fd:00 76082 /lib64/libresolv-2.5.so 3dba813000-3dba815000 rw-p 3dba813000 00:00 0 3dbaa00000-3dbaa02000 r-xp 00000000 fd:00 76083 /lib64/libcom_err.so.2.1 3dbaa02000-3dbac01000 ---p 00002000 fd:00 76083 /lib64/libcom_err.so.2.1 3dbac01000-3dbac02000 rw-p 00001000 fd:00 76083 /lib64/libcom_err.so.2.1 3dbba00000-3dbba02000 r-xp 00000000 fd:00 76080 /lib64/libkeyutils-1.2.so 3dbba02000-3dbbc01000 ---p 00002000 fd:00 76080 /lib64/libkeyutils-1.2.so 3dbbc01000-3dbbc02000 rw-p 00001000 fd:00 76080 /lib64/libkeyutils-1.2.so 3dbc200000-3dbc20d000 r-xp 00000000 fd:00 75803 /lib64/libgcc_s-4.1.2-20080102.so.1 3dbc20d000-3dbc40d000 ---p 0000d000 fd:00 75803 /lib64/libgcc_s-4.1.2-20080102.so.1 3dbc40d000-3dbc40e000 rw-p 0000d000 fd:00 75803 /lib64/libgcc_s-4.1.2-20080102.so.1 2b7f796eb000-2b7f796ec000 rw-p 2b7f796eb000 00:00 0 2b7f796f8000-2b7f79700000 rw-p 2b7f796f8000 00:00 0 2b7f79700000-2b7f7970a000 r-xp 00000000 fd:00 75873 /lib64/libnss_files-2.5.so 2b7f7970a000-2b7f79909000 ---p 0000a000 fd:00 75873 /lib64/libnss_files-2.5.so 2b7f79909000-2b7f7990a000 r--p 00009000 fd:00 75873 /lib64/libnss_files-2.5.so 2b7f7990a000-2b7f7990b000 rw-p 0000a000 fd:00 75873 /lib64/libnss_files-2.5.so 2b7f7c000000-2b7f7c021000 rw-p 2b7f7c000000 00:00 0 2b7f7c021000-2b7f80000000 ---p 2b7f7c021000 00:00 0 7fff313a9000-7fff313bf000 rw-p 7fff313a9000 00:00 0 [stack] ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso] [root at las006 tmp]# gdb /usr/lib/hobbit/server/bin/bbtest-net -c core.31042 GNU gdb Red Hat Linux (6.5-37.el5_2.1rh) Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /usr/lib64/libldap-2.3.so.0...done. Loaded symbols for /usr/lib64/libldap-2.3.so.0 ** snip ** Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `bbtest-net --report --ping --checkresponse'. Program terminated with signal 6, Aborted. #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 #1 0x0000003db7a31bf0 in abort () from /lib64/libc.so.6 #2 0x000000000041d7e3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 0x0000000000424a57 in qcallback (arg=0x163b9ee0, status=0, abuf=0x7fff9d536fc0 "\201\200", alen=140) at ares_query.c:108 #5 0x00000000004216c2 in end_query (channel=0x163a34d0, query=0x163d6e50, status=0, abuf=0x0, alen=-1655476288) at ares_process.c:627 #6 0x0000000000421ebd in process_answer (channel=0x163a34d0, abuf=0x7fff9d536fc0 "\201\200", alen=140, whichserver=0, tcp=<value optimized out>, now=1226882805) at ares_process.c:359 #7 0x00000000004221ff in ares_process (channel=0x163a34d0, read_fds=0x7fff9d537290, write_fds=0x7fff9d537210) at ares_process.c:273 #8 0x000000000040f064 in dns_queue_run (channel=0x163a34d0) at dns.c:228 #9 0x000000000040f464 in flush_dnsqueue () at dns.c:259 #10 0x00000000004088e6 in main (argc=4, argv=0x7fff9d538798) at bbtest-net.c:2099 #11 0x0000003db7a1d8b4 in __libc_start_main () from /lib64/libc.so.6 #12 0x00000000004039e9 in _start () (gdb) quit [root at las006 tmp]# gdb /usr/lib/hobbit/server/bin/bbtest-net -c core.15643 GNU gdb Red Hat Linux (6.5-37.el5_2.1rh) Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /usr/lib64/libldap-2.3.so.0...done. Loaded symbols for /usr/lib64/libldap-2.3.so.0 ** snip ** Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `bbtest-net --report --ping --checkresponse'. Program terminated with signal 6, Aborted. #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 #1 0x0000003db7a31bf0 in abort () from /lib64/libc.so.6 #2 0x000000000041d7e3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 0x0000003db7a79f10 in strcasecmp () from /lib64/libc.so.6 #5 0x0000000000418cda in rbtFind (h=0x8d4b680, key=0x8e22310) at rbtr.c:381 #6 0x000000000040f4d8 in find_dnscache (hostname=0x0) at dns.c:86 #7 0x000000000040f546 in dnsresolve (hostname=0x8e22310 "DRPIR101") at dns.c:275 #8 0x0000000000406848 in ip_to_test (h=0x8e22150) at bbtest-net.c:790 #9 0x00000000004069ca in start_ping_service (service=<value optimized out>) at bbtest-net.c:1099 #10 0x000000000040891f in main (argc=4, argv=0x7fffefcdff38) at bbtest-net.c:2105 #11 0x0000003db7a1d8b4 in __libc_start_main () from /lib64/libc.so.6 #12 0x00000000004039e9 in _start () (gdb) quit [root at las006 tmp]# gdb /usr/lib/hobbit/server/bin/bbtest-net -c core.13374 GNU gdb Red Hat Linux (6.5-37.el5_2.1rh) Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /usr/lib64/libldap-2.3.so.0...done. Loaded symbols for /usr/lib64/libldap-2.3.so.0 ** snip ** Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `bbtest-net --report --ping --checkresponse'. Program terminated with signal 6, Aborted. #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 #1 0x0000003db7a31bf0 in abort () from /lib64/libc.so.6 #2 0x000000000041d7e3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 0x00000000004069b7 in start_ping_service (service=<value optimized out>) at bbtest-net.c:1098 #5 0x000000000040891f in main (argc=4, argv=0x7fff8f61e4d8) at bbtest-net.c:2105 #6 0x0000003db7a1d8b4 in __libc_start_main () from /lib64/libc.so.6 #7 0x00000000004039e9 in _start () (gdb) quit [root at las006 tmp]# gdb /usr/lib/hobbit/server/bin/bbtest-net -c core.7801 GNU gdb Red Hat Linux (6.5-37.el5_2.1rh) Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /usr/lib64/libldap-2.3.so.0...done. Loaded symbols for /usr/lib64/libldap-2.3.so.0 ** snip ** Loaded symbols for /lib64/libsepol.so.1 Reading symbols from /lib64/libnss_files.so.2...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `bbtest-net --report --ping --checkresponse'. Program terminated with signal 6, Aborted. #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x0000003db7a30155 in raise () from /lib64/libc.so.6 #1 0x0000003db7a31bf0 in abort () from /lib64/libc.so.6 #2 0x000000000041d7e3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 ares_process (channel=0x157137c0, read_fds=0x7fff91e5dbb0, write_fds=0x7fff91e5db30) at ares_process.c:285 #5 0x000000000040f064 in dns_queue_run (channel=0x157137c0) at dns.c:228 #6 0x000000000040f464 in flush_dnsqueue () at dns.c:259 #7 0x00000000004088e6 in main (argc=4, argv=0x7fff91e5f0b8) at bbtest-net.c:2099 #8 0x0000003db7a1d8b4 in __libc_start_main () from /lib64/libc.so.6 #9 0x00000000004039e9 in _start () (gdb) quit NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.

4 8

bbnet-test https bug
by brian＠majeska.net 04 Dec '08

04 Dec '08

environment: Hobbit 4.2 with allinone patch on RHEL5.1 It appears that using the https tag and defining a port introduces 50-200ms of latency to the results of all bbnet-tests. I had the following tag working fine for months in bb-hosts: cont=kvm;https://server.domain.com/dsview/protected/login.do;Avocent The need came up to move this particular webserver to a non-standard ssl port: cont=kvm;https://server.domain.com:9443/dsview/protected/login.do;Avocent As soon as I did this 'all' TCP graphs, http, ldap, smtp, etc... had a new plateau 50-200ms higher. I ran bbnet-test with the --debug and --timing options but didn't see anything out of the ordinary, then again I don't know what I should be looking for that would help to resolve it. Let me know what you want and I'll provide it. I was able to duplicate the problem on a separate dev hobbit server as well. -- Brian Majeska

3 2

[hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented
by spa＠syntec.co.uk 03 Dec '08

03 Dec '08

SebA <mailto:spa at syntec.co.uk> wrote: > Maybe we have now covered all the examples needed though? Ah, a few more examples I've been playing with FYI and for the documentation: HOST=%myhost(.*) EXHOST=myhost.whatever ... (whatever else) Works. You _can_ use HOST and EXHOST together. (Docs don't mention this.) Or you can do it like this: HOST=%myhost(.*) SERVICE=conn,http,imap,pop3,smtp MAIL CommaSeparatedE-MailAddresses EXHOST=myhost.whatever EXHOST even works in the MAIL line(s). Nice. And you can even have nested HOST flags, e.g.: HOST=%myhost(.*) SERVICE=conn,http,imap,pop3,smtp MAIL CommaSeparatedE-MailAddresses HOST=myhost.whatever Very nice for having different DURATIONs depending on the interface of myhost that is being network tested. :) Oh, BTW, I also discovered you can add durations and colors and things to the hobbitd_alert --test: ./bin/bbcmd hobbitd_alert --test myhost smtp --duration=11 And similar. This is documented here: http://hobbitmon.sourceforge.net/docs/man8/hobbitd_alert.8.html but it would be easier to find that man page if there was a link from http://hobbitmon.sourceforge.net/docs/hobbit-alerts.html ;) Kind regards, SebA -------- Better documentation => more user-friendly, less frustration => more Xymon users... ;)

1 0

[hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented
by tj_yang＠hotmail.com 03 Dec '08

03 Dec '08

Hi, SebA Would mind go one step further ? get a hobbit developer account from Henrik to update the manpages ? T.J. Yang From: spa at syntec.co.uk To: hobbit at hswn.dk Date: Wed, 15 Oct 2008 16:25:16 +0100 Subject: RE: [hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented Thanks for the suggestion. I'll certainly give that some thought. Comma-separated is just the easiest when it comes to converting my existing bbwarnrules.cfg file as I can just select the hosts and replace spaces with commas. Going forward I had thought of using macros, but I'll look at PAGEs too. SebA From: jm54601 at yahoo.com [mailto:jm54601 at yahoo.com] Sent: 15 October 2008 16:03 To: hobbit at hswn.dk Subject: Re: [hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented I struggled with the same thing through a lot of trial and error. On a related note, I highly recommend trying to get away from using a comma separated list as it's a nightmare to maintain. I'm working toward using the PAGE token, where a list of hosts on a given page alerts a group, so you're effectively grouping your hosts based on the support team responsible. There will still be exceptions, but if you can generalize alerts so all the hosts on a given page can alert the same way, you'll save time and avoid the possibility of a host not having an alert configured. Just my 2 cents. ----- Original Message ---- From: SebA <spa at syntec.co.uk> To: hobbit at hswn.dk Sent: Wednesday, October 15, 2008 7:43:35 AM Subject: [hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented Comma-separated lists of hostnames in hobbit-alerts.cfg is not documented, so maybe we could add something like this (taken from http://hobbitmon.sourceforge.net/docs/man5/hobbit-clients.cfg.5.html) to http://hobbitmon.sourceforge.net/docs/man5/hobbit-alerts.cfg.5.html: HOST=targetstring Rule matching a host by the hostname. "targetstring" is either a comma-separated list of hostnames (from the bb-hosts file), "*" to indicate "all hosts", or a Perl-compatible regular expression. E.g. "HOST=dns.foo.com,www.foo.com" identifies two specific hosts; "HOST=%www.*.foo.com EXHOST=www-test.foo.com" matches all hosts with a name beginning with "www", except the "www-test" host. Adding an example that used the comma-separated syntax to http://hobbitmon.sourceforge.net/docs/hobbit-alerts.html and hobbit-alerts.cfg (sample) files would also be good. And, actually, maybe something to say that the comma-separated syntax can be used in all XXX= places (except, presumably, REPEAT) and also for the recipient. One really shouldn't have to work this basic stuff out using: $ ./bin/bbcmd hobbitd_alert --test ! We definitely need some more complex examples. Maybe someone who has a complex and varied hobbit-alerts.cfg can post some sanitized examples that someone can commit to SVN? Many thanks, SebA _________________________________________________________________ Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!5…

3 2

[hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented
by jm54601＠yahoo.com 03 Dec '08

03 Dec '08

I struggled with the same thing through a lot of trial and error. On a related note, I highly recommend trying to get away from using a comma separated list as it's a nightmare to maintain. I'm working toward using the PAGE token, where a list of hosts on a given page alerts a group, so you're effectively grouping your hosts based on the support team responsible. There will still be exceptions, but if you can generalize alerts so all the hosts on a given page can alert the same way, you'll save time and avoid the possibility of a host not having an alert configured. Just my 2 cents. ----- Original Message ---- From: SebA <spa at syntec.co.uk> To: hobbit at hswn.dk Sent: Wednesday, October 15, 2008 7:43:35 AM Subject: [hobbit] Comma-separated lists of hostnames, etc. in hobbit-alerts.cfg is not documented Comma-separated lists of hostnames in hobbit-alerts.cfg is not documented, so maybe we could add something like this (taken from http://hobbitmon.sourceforge.net/docs/man5/hobbit-clients.cfg.5.html) to http://hobbitmon.sourceforge.net/docs/man5/hobbit-alerts.cfg.5.html: HOST=targetstring Rule matching a host by the hostname. "targetstring" is either a comma-separated list of hostnames (from the bb-hosts file), "*" to indicate "all hosts", or a Perl-compatible regular expression. E.g. "HOST=dns.foo.com,www.foo.com" identifies two specific hosts; "HOST=%www.*.foo.com EXHOST=www-test.foo.com" matches all hosts with a name beginning with "www", except the "www-test" host. Adding an example that used the comma-separated syntax to http://hobbitmon.sourceforge.net/docs/hobbit-alerts.htmland hobbit-alerts.cfg (sample) files would also be good. And, actually, maybe something to say that the comma-separated syntax can be used in all XXX= places (except, presumably, REPEAT) and also for the recipient. One really shouldn't have to work this basic stuff out using: $ ./bin/bbcmd hobbitd_alert --test ! We definitely need some more complex examples. Maybe someone who has a complex and varied hobbit-alerts.cfg can post some sanitized examples that someone can commit to SVN? Many thanks, SebA

3 3

hobbitdxboard: not xml compliance
by stef.coene＠docum.org 03 Dec '08

03 Dec '08

I just tried the hobbitdxboard command I found some <br> text in the output: <Sender>127.0.0.1<br></Sender> The hobbitdboard command has the same issue. I tried it on an other hobbit server and there is the output ok. I don't understand where the <br> comes from. Stef

1 0

Services listed multiple times on the info page
by tk＠westend.com 03 Dec '08

03 Dec '08

Hi, for some systems some services are listed multiple times in the alerting table on the info page. E.g. conn and cpu are listed three times but http is listed only once. Though there is no different alerting configuration for the different services. I couldn't figure out any negative effect yet. However it looks strange. Is there any known bug? Best regards Thomas -- Thomas Kähn NetCologne Network Engineering & Design Gesellschaft für Telekommunikation mbH Im Süsterfeld 6 Telefon: 0241/701333-18 52072 Aachen Fax: 0241/911879 Handelsregister: HRB 25580, Amtsgericht Köln Geschäftsführer: Werner Hanf, Dipl.-Ing. Karl-Heinz Zankel

2 4

Alerting does not work for more than 3 scripts?
by tk＠westend.com 03 Dec '08

03 Dec '08

Hi, I've configured 4 SCRIPT entries for a host in hobbit-alerts.cfg. However only 3 recipients are being notified. These notifications are also logged in /var/log/hobbit/notifications.log. hobbitd_alert --test and --dump-config are showing for SCRIPT entries as expected. Is there a limitation to 3 recipients per rule in hobbit-alerts.cfg? hobbitd_alert --dump-config: PAGE=crashnotification/CUSTOMER SCRIPT /etc/hobbit/alert.php recipient1 at domain.com FORMAT=PLAIN REPEAT=720 RECOVERED SCRIPT /etc/hobbit/alert.php recipient2 at domain.com FORMAT=PLAIN REPEAT=720 RECOVERED SCRIPT /etc/hobbit/alert-sms.php recipient3 at domain.com FORMAT=PLAIN REPEAT=720 RECOVERED SCRIPT /etc/hobbit/alert-sms.php recipient4 at domain.com FORMAT=PLAIN REPEAT=720 RECOVERED notification.log: Tue Dec 2 09:11:22 2008 crash.com.conn (xx.xxx.xxx.xxx) recipient1 at domain.com 1228205482 500 Tue Dec 2 09:11:22 2008 crash.com.conn (xx.xxx.xxx.xxx) recipient2 at domain.com 1228205482 500 Tue Dec 2 09:11:22 2008 crash.com.conn (xx.xxx.xxx.xxx) recipient3 at domain.com 1228205482 500 Best regards Thomas -- Thomas Kähn NetCologne Network Engineering & Design Gesellschaft für Telekommunikation mbH Im Süsterfeld 6 Telefon: 0241/701333-18 52072 Aachen Fax: 0241/911879 Handelsregister: HRB 25580, Amtsgericht Köln Geschäftsführer: Werner Hanf, Dipl.-Ing. Karl-Heinz Zankel

2 2