March 2008 - Xymon - Xymon mailman web

How to alert on Summary reports
by Dave.Whitehouse＠talis.com 20 Mar '08

20 Mar '08

Hi, Is it possible to alert on a summary from a remote hobbit server? I have two servers, 1 in the office with a modem attached for SMS alerts and one out at one of our Co Location sites that sends summary reports to the first one. I've tried configuring an alert on the summary reports with a few different alert lines but can't seem to get it to works. I though if I use COLOR="red" then that should work but no joy. Any one done this ? Thanks Dave.

1 0

[hobbit] rrd "illegal attempt to update using time" error
by spa＠syntec.co.uk 20 Mar '08

20 Mar '08

I also have this problem and the result of it is some rather large log files: -rw-rw-r-- 1 hobbit hobbit 356M Mar 20 12:46 rrd-data.log -rw-rw-r-- 1 hobbit hobbit 3.5G Mar 20 12:46 rrd-status.log This happens on hobbit 4.2.0 (unpatched) and the latest snapshot of 4.3.0. Kind regards, Sebastian > * To: hobbit (at) hswn.dk > * Subject: rrd "illegal attempt to update using time" error > * From: "Robin Wood" <dninja (at) gmail.com> > * Date: Thu, 16 Aug 2007 21:35:20 +0100 > > Hi > While trying to solve my other problem I came across this in the > rrd-status.log file: > > 2007-08-16 20:34:40 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.http.xxxxxxx.dev,.rrd from > 127.0.0.1: illegal attempt to update using time 118729288 > 0 when last update time is 1187292880 (minimum one second step) > 2007-08-16 20:39:41 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.conn.rrd from 127.0.0.1: illegal > attempt to update using time 1187293181 when last u > pdate time is 1187293181 (minimum one second step) > 2007-08-16 20:39:41 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.http.xxxxxxx.dev,.rrd from > 127.0.0.1: illegal attempt to update using time 118729318 > 1 when last update time is 1187293181 (minimum one second step) > 2007-08-16 20:39:41 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.http.xxxxxxx.dev,.rrd from > 127.0.0.1: illegal attempt to update using time 118729318 > 1 when last update time is 1187293181 (minimum one second step) > 2007-08-16 20:44:42 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.conn.rrd from 127.0.0.1: illegal > attempt to update using time 1187293482 when last u > pdate time is 1187293482 (minimum one second step) > 2007-08-16 20:44:42 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.http.xxxxxxx.dev,.rrd from > 127.0.0.1: illegal attempt to update using time 118729348 > 2 when last update time is 1187293482 (minimum one second step) > 2007-08-16 20:44:42 RRD error updating > /usr/lib/hobbit/data/rrd/devsite/tcp.http.xxxxxxx.dev,.rrd from > 127.0.0.1: illegal attempt to update using time 118729348 > 2 when last update time is 1187293482 (minimum one second step) > > I assume that whatever is calling rrd is running too quickly and so > calling it in the same tick rather than waiting one before doing it. > > Can this be fixed? > > Robin >

1 0

www.deadcat.net bb-3ware.pl monitor 3ware raid client side
by robert＠schetterer.org 20 Mar '08

20 Mar '08

Hi all, i tried to modifiy bb-3ware.pl from www.deadcat.net to my needs and on the client i ve no problems in logs but it doesnt show up in server i am not clear if i need to add somthing more to the servers cfg to show up. Is there anybody running 3ware raid monitoring with hobbit and uses better or newer solution as bb-3ware.pl ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

hobbitd core dumps when receiving a status message on a host not in bb-hosts (snapshot 18 March 2008)
by spa＠syntec.co.uk 19 Mar '08

19 Mar '08

Hi, hobbitd core dumps when receiving a status message on a host not in bb-hosts (snapshot 18 March 2008). This may, possibly, just be when the message comes from a Big Brother server, since that was the case here. I haven't tested when the message comes from another Hobbit server and I have now downgraded again. However, if needed, I could try reupdating. Backtraces follow... [root at IVRA1 hobbit]# gdb hobbit-snapshot-18-Mar-08/hobbitd/hobbitd server/tmp/core.683 GNU gdb Red Hat Linux (6.3.0.0-1.96rh) 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 --pidfile=/var/log/hobbit/hobbitd.pid --restart=/usr/local/hobbit/serve'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libpcre.so.0...done. Loaded symbols for /lib/libpcre.so.0 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 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 0x005557a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) (gdb) (gdb) bt #0 0x005557a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x005957f5 in raise () from /lib/tls/libc.so.6 #2 0x00597199 in abort () from /lib/tls/libc.so.6 #3 0x0805c132 in sigsegv_handler (signum=11) at sig.c:58 #4 <signal handler called> #5 hostinfo (hostname=0x991a6f7 "Flaxman") at loadhosts.c:401 #6 0x0805d81d in check_downtime (hostname=0x991a6f7 "Flaxman", testname=0x991a6ff "conn") at timefunc.c:285 #7 0x0804b8ff in get_hts ( msg=0xb7cb21ac "status Flaxman.conn red  Wed Mar 19 16:13:13 2008 conn NOT ok \n\nService conn on Flaxman is not OK : Host does not respond to ping\n\n\nSystem unreachable for 15720 poll periods ("..., sender=0xbff45fb0 "192.168.4.118", origin=0x805fb8e "", host=0xbff44728, test=0xbff4472c, grouplist=0xbff44730, log=0xbff44734, color=0xbff44738, downcause=0xbff4473c, alltests=0x0, createhost=1, createlog=1) at hobbitd.c:1012 #8 0x0804f304 in do_message (msg=0x9926eb0, origin=0x805fb8e "") at hobbitd.c:2787 #9 0x08055129 in main (argc=8, argv=0xbff48424) at hobbitd.c:4867 (gdb) And [root at IVRA1 hobbit]# gdb hobbit-snapshot-18-Mar-08/hobbitd/hobbitd server/tmp/core.685 GNU gdb Red Hat Linux (6.3.0.0-1.96rh) 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 --pidfile=/var/log/hobbit/hobbitd.pid --restart=/usr/local/hobbit/serve'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libpcre.so.0...done. Loaded symbols for /lib/libpcre.so.0 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 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 0x005557a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) (gdb) (gdb) bt #0 0x005557a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x005957f5 in raise () from /lib/tls/libc.so.6 #2 0x00597199 in abort () from /lib/tls/libc.so.6 #3 0x0805c132 in sigsegv_handler (signum=11) at sig.c:58 #4 <signal handler called> #5 hostinfo (hostname=0x8924897 "faxmonster") at loadhosts.c:401 #6 0x0805d81d in check_downtime (hostname=0x8924897 "faxmonster", testname=0x89248a2 "conn") at timefunc.c:285 #7 0x0804b8ff in get_hts ( msg=0x8981748 "status faxmonster.conn red Wed Mar 19 16:16:44 2008 Can't connect to faxmonster\r\nPING faxmonster (192.168.4.91): 56 data bytes\r\nhost faxmonster unreachable\r\nhost faxmonster unreachable\r\nhost faxmonste"..., sender=0xbfeffbd0 "192.168.4.101", origin=0x805fb8e "", host=0xbfefe348, test=0xbfefe34c, grouplist=0xbfefe350, log=0xbfefe354, color=0xbfefe358, downcause=0xbfefe35c, alltests=0x0, createhost=1, createlog=1) at hobbitd.c:1012 #8 0x0804f845 in do_message (msg=0x88fb5a0, origin=0x805fb8e "") at hobbitd.c:2854 #9 0x08055129 in main (argc=8, argv=0xbff02044) at hobbitd.c:4867 (gdb) Etc. More very similar to these. It would appear that every single one of these status messages causes a core dump as they happen at approx. 5 minute, or less, intervals. Both of these hosts are commented out in bb-hosts, but hobbitd is receiving updates on them from a Big Brother server (where they should probably be commented out too, but I found I didn't need to with hobbit 4.2.0, so long as I don't mind getting the Ghost reports warning). Kind regards, Sebastian

2 1

[hobbit] How hobbit server deal with DNS server failure when doing conn test ?
by bewhite＠fellowes.com 19 Mar '08

19 Mar '08

Neither. It tries DNS, then it tries the IP address in the bb-hosts file. If it can ping the IP address it sets the conn dot to green. The only place I have found that reports it could not resolve the name via DNS is in the output I copied into my email. .....Bruce _____ From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Wednesday, March 19, 2008 10:14 AM To: hobbit at hswn.dk Subject: Re: [hobbit] How hobbit server deal with DNS server failure when doing conn test ? So if it can not resolve DNS, is it yellow instead of red? On 3/19/08, White, Bruce <bewhite at fellowes.com <mailto:bewhite at fellowes.com> > wrote: Josh, I think the first statement is true. I have many items monitored by hobbit which are not registered in DNS (I live with a bunch of windows centric team mates and they rely on WINS not DNS. None of these items end up with conn=red, but they are ID'd in the output from bbtest on the hobbit server. Here is that output: DNS statistics: # hostnames resolved : 383 # succesful : 306 # failed : 77 # calls to dnsresolve : 414 Notice that I have 77 monitored items which fail the DNS lookup. .....Bruce _____ From: Josh Luthman [mailto:josh at imaginenetworksllc.com <mailto:josh at imaginenetworksllc.com> ] Sent: Wednesday, March 19, 2008 8:55 AM To: hobbit at hswn.dk <mailto:hobbit at hswn.dk> Subject: Re: [hobbit] How hobbit server deal with DNS server failure when doing conn test ? Pretty confident if the DNS lookup fails it times out and marks the conn red =( If you don't need it to do a DNS lookup simply add testip. On 3/19/08, T.J. Yang <tj_yang at hotmail.com <mailto:tj_yang at hotmail.com> > wrote: I remember somewhere in the manpages, The hobbit server when doing fping conn test, it will try using FQDN and if not resolvable, it will use the ip address(from bb-hosts) file. Is this a correct statement ? I will summarize the answer here http://en.wikibooks.org/wiki/System_Monitoring_with_Hobbit/Other_Docs/FAQ#Ho w_does_the_conn_test_work_if_the_first_ping_doesn.27t_respond_.3F <http://en.wikibooks.org/wiki/System_Monitoring_with_Hobbit/Other_Docs/FAQ#H ow_does_the_conn_test_work_if_the_first_ping_doesn.27t_respond_.3F> tj To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk <mailto:hobbit-unsubscribe at hswn.dk> -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer ---------------------------------------------------- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. ---------------------------------------------------- -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer ---------------------------------------------------- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. ----------------------------------------------------

3 2

Bug (regression) with Disabled Status Alerts
by spa＠syntec.co.uk 19 Mar '08

19 Mar '08

Hi, Any progress on this one (see below)? Currently NOTICEs seem to be sent out when an alert is enabled but not when it is disabled (where it is a 'recovered' instead). This appears to be a regression since this message: http://www.hswn.dk/hobbiton/2005/11/msg00117.html shows that DISABLED NOTICEs did use to be sent a few years back. I am using Hobbit 4.2.0 with no patches. Example e-mail when I disable a test: Subject: Hobbit SebTest:conn recovered Body: red Tue Mar 18 18:54:07 2008 conn NOT ok Service conn on SebTest is not OK : Host does not respond to ping System unreachable for 51 poll periods (15086 seconds) I also tried upgrading to yesterday's snapshot, but that didn't help. Actually it was far worse, because after disabling a test, I got the e-mail as above, the test was shown as disabled on bb.html, and then hobbitd core dumped, and when it was restarted by hobbitlaunch, the test was no longer disabled and I got another alert. Looking at the core dumps now, it looks like it is core dumping approximately every 5 minutes, so I'll send another e-mail about that, plus another possibly related issue I found with the snapshot. In addition, one of the alerts I got on this particular test said: System unreachable for 5985 poll periods (1813435 seconds) And this was just after it went red. Maybe it was so soon afterwards that something went wrong in the calculations? It should have been 1 poll period. Kind regards, Sebastian >To: hobbit (at) hswn.dk >Subject: Suggestion about Disabled Status >From: "Jeffrey Chandler" <jeffrey.chandler (at) gmail.com> >Date: Wed, 4 Apr 2007 09:13:52 -0400 > >Hello, > >Currently when an alert is raised, and an administrator disables the alert, >an email is sent stating that the resource has been recovered. The body of >the email still says that the test is "Not OK" , but the subject of the >email still says Recovered. > >I don't know how difficult this would be to configure, but would it be >possible to have the subject of this email stat the the alert has been >disabled instead? > >Thanks, > >Jeff

1 0

content/http checks with interesting URLs
by cb＠df7cb.de 19 Mar '08

19 Mar '08

Hi, one of our customers wanted a content check for a URL looking roughly like: http://100.1.2.3:8080/httpserver/httpserver/isalive.jsp?password=aaa Hobbit barfs on the "/http" in there and thinks this is http check with a proxy URL. The following patch fixes this: --- a/lib/url.c +++ b/lib/url.c @@ -563,7 +563,9 @@ char *decode_url(char *testspec, bburl_t if (poststart) getescapestring(poststart, &bburl->postdata, NULL); if (expstart) getescapestring(expstart, &bburl->expdata, NULL); - p = strstr(urlstart, "/http"); + p = strstr(urlstart, "/http://"); + if (!p) + p = strstr(urlstart, "/https://"); if (p) { proxystart = urlstart; urlstart = (p+1); Christoph -- cb at df7cb.de | http://www.df7cb.de/

2 1

[hobbit] How hobbit server deal with DNS server failure when doing conn test ?
by bewhite＠fellowes.com 19 Mar '08

19 Mar '08

Josh, I think the first statement is true. I have many items monitored by hobbit which are not registered in DNS (I live with a bunch of windows centric team mates and they rely on WINS not DNS. None of these items end up with conn=red, but they are ID'd in the output from bbtest on the hobbit server. Here is that output: DNS statistics: # hostnames resolved : 383 # succesful : 306 # failed : 77 # calls to dnsresolve : 414 Notice that I have 77 monitored items which fail the DNS lookup. .....Bruce _____ From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Wednesday, March 19, 2008 8:55 AM To: hobbit at hswn.dk Subject: Re: [hobbit] How hobbit server deal with DNS server failure when doing conn test ? Pretty confident if the DNS lookup fails it times out and marks the conn red =( If you don't need it to do a DNS lookup simply add testip. On 3/19/08, T.J. Yang <tj_yang at hotmail.com <mailto:tj_yang at hotmail.com> > wrote: I remember somewhere in the manpages, The hobbit server when doing fping conn test, it will try using FQDN and if not resolvable, it will use the ip address(from bb-hosts) file. Is this a correct statement ? I will summarize the answer here http://en.wikibooks.org/wiki/System_Monitoring_with_Hobbit/Other_Docs/FAQ#Ho w_does_the_conn_test_work_if_the_first_ping_doesn.27t_respond_.3F <http://en.wikibooks.org/wiki/System_Monitoring_with_Hobbit/Other_Docs/FAQ#H ow_does_the_conn_test_work_if_the_first_ping_doesn.27t_respond_.3F> tj To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk <mailto:hobbit-unsubscribe at hswn.dk> -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer ---------------------------------------------------- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. ----------------------------------------------------

2 1

Question about ntp script
by pwilliamson＠mtb.com 19 Mar '08

19 Mar '08

I'm monitoring some ntp devices, and it works fine for all the appliances - based on the bb-ntp.sh script from deadcat. However, I have a device that is named with a string of "ntp" within the system name that makes the script think it should be testing ntp. I've tried adding a [[:space:]] to the grep in the script and it doesn't work (no effect) and the ntp script still tries to test ntp on the server. Can anyone help out with a grep that would work within a script? I tried a grep [[:space:]]ntp <filename> from the command line that works fine, but it doesn't work in the shell script. Thanks, Paul ************************************ This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information. There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission. ************************************

1 0

[hobbit] Bug latest snapshot, hobbitd_client
by david.gore＠verizonbusiness.com 19 Mar '08

19 Mar '08

[hobbit at hobbit2 server]$ file tmp/core.21567 tmp/core.21567: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'hobbitd_client' [hobbit at hobbit2 server]$ file tmp/core.21600 tmp/core.21600: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'hobbitd_client' [hobbit at hobbit2 server]$ ls -al tmp/core.21567 tmp/core.21600 -rw------- 1 hobbit hobbit 5210112 Mar 19 00:23 tmp/core.21567 -rw------- 1 hobbit hobbit 5210112 Mar 19 00:23 tmp/core.21600 Dumps core in pairs every 1-5 minutes or so: -rw------- 1 hobbit hobbit 5210112 Mar 19 00:23 tmp/core.21600 -rw------- 1 hobbit hobbit 5210112 Mar 19 00:23 tmp/core.21567 -rw------- 1 hobbit hobbit 4038656 Mar 19 00:27 tmp/core.21841 -rw------- 1 hobbit hobbit 4038656 Mar 19 00:27 tmp/core.21602 -rw------- 1 hobbit hobbit 49213440 Mar 19 00:31 tmp/core.21520 -rw------- 1 hobbit hobbit 5505024 Mar 19 00:32 tmp/core.22115 -rw------- 1 hobbit hobbit 5505024 Mar 19 00:32 tmp/core.22109 -rw------- 1 hobbit hobbit 4227072 Mar 19 00:36 tmp/core.22378 -rw------- 1 hobbit hobbit 4227072 Mar 19 00:36 tmp/core.22169 -rw------- 1 hobbit hobbit 3776512 Mar 19 00:38 tmp/core.22439 -rw------- 1 hobbit hobbit 3776512 Mar 19 00:38 tmp/core.22379 -rw------- 1 hobbit hobbit 5881856 Mar 19 00:43 tmp/core.22706 -rw------- 1 hobbit hobbit 5881856 Mar 19 00:43 tmp/core.22441 -rw------- 1 hobbit hobbit 3584000 Mar 19 00:44 tmp/core.22715 -rw------- 1 hobbit hobbit 3584000 Mar 19 00:44 tmp/core.22707 -rw------- 1 hobbit hobbit 4902912 Mar 19 00:48 tmp/core.22968 -rw------- 1 hobbit hobbit 4902912 Mar 19 00:48 tmp/core.22716 -rw------- 1 hobbit hobbit 5398528 Mar 19 00:51 tmp/core.23165 -rw------- 1 hobbit hobbit 5398528 Mar 19 00:51 tmp/core.22969 -rw------- 1 hobbit hobbit 4841472 Mar 19 00:53 tmp/core.23233 -rw------- 1 hobbit hobbit 4841472 Mar 19 00:53 tmp/core.23166 -rw------- 1 hobbit hobbit 3964928 Mar 19 00:58 tmp/core.23493 -rw------- 1 hobbit hobbit 3964928 Mar 19 00:58 tmp/core.23234 -rw------- 1 hobbit hobbit 3817472 Mar 19 01:03 tmp/core.23836 -rw------- 1 hobbit hobbit 3817472 Mar 19 01:03 tmp/core.23494 -rw------- 1 hobbit hobbit 54190080 Mar 19 01:07 tmp/core.22100 -rw------- 1 hobbit hobbit 5402624 Mar 19 01:12 tmp/core.24304 -rw------- 1 hobbit hobbit 5402624 Mar 19 01:12 tmp/core.24095 -rw------- 1 hobbit hobbit 4055040 Mar 19 01:13 tmp/core.24367 -rw------- 1 hobbit hobbit 4055040 Mar 19 01:13 tmp/core.24305 I am not sure I should post my gdb back trace here, but it has been dumping core for at least a week perhaps longer with different daily snapshots. We use the same configs on a much older snapshot with no problems. I am not sure of the date of the stable snapshot, the version is listed as Hobbit Monitor 4.3.0-0.20071026. Running Red Hat Enterprise 4.0. After a while it fills up the file system. As a side note, I thought I reported this a few month or so ago, but the files column is mangled for some hosts, shows duplicate file entries like /etc/hosts listed twice or even 3 times on the web page. Of course this means hobbitd is crashing, stopping? [hobbit at hobbit2 logs]$ cat hobbitlaunch.log 2008-03-19 00:22:14 hobbitlaunch starting 2008-03-19 00:22:14 Loading tasklist configuration from /home/hobbit/server/etc/hobbitlaunch.cfg 2008-03-19 00:22:14 Loading hostnames 2008-03-19 00:22:14 Loading saved state 2008-03-19 00:22:15 Setting up network listener on 0.0.0.0:1984 2008-03-19 00:22:15 Setting up local listener 2008-03-19 00:22:15 Setting up signal handlers 2008-03-19 00:22:15 Setting up hobbitd channels 2008-03-19 00:22:15 Setting up logfiles 2008-03-19 00:31:46 Task hobbitd terminated by signal 6 2008-03-19 00:31:46 Loading hostnames 2008-03-19 00:31:46 Loading saved state 2008-03-19 00:31:47 Setting up network listener on 0.0.0.0:1984 2008-03-19 00:31:47 Setting up local listener 2008-03-19 00:31:47 Setting up signal handlers 2008-03-19 00:31:47 Setting up hobbitd channels 2008-03-19 00:31:47 Setting up logfiles 2008-03-19 01:07:56 Task hobbitd terminated by signal 6 2008-03-19 01:07:56 Task bbnet terminated by signal 15 2008-03-19 01:07:56 Loading hostnames 2008-03-19 01:07:57 Loading saved state 2008-03-19 01:07:57 Setting up network listener on 0.0.0.0:1984 2008-03-19 01:07:57 Setting up local listener 2008-03-19 01:07:57 Setting up signal handlers 2008-03-19 01:07:57 Setting up hobbitd channels 2008-03-19 01:07:57 Setting up logfiles 2008-03-19 01:17:55 Task hobbitd terminated by signal 6 2008-03-19 01:17:55 Task bbnet terminated by signal 15 2008-03-19 01:17:55 Loading hostnames 2008-03-19 01:17:55 Loading saved state 2008-03-19 01:17:56 Setting up network listener on 0.0.0.0:1984 2008-03-19 01:17:56 Setting up local listener 2008-03-19 01:17:56 Setting up signal handlers 2008-03-19 01:17:56 Setting up hobbitd channels 2008-03-19 01:17:56 Setting up logfiles 2008-03-19 01:21:32 Task hobbitd terminated by signal 6 2008-03-19 01:21:33 Loading hostnames 2008-03-19 01:21:33 Loading saved state 2008-03-19 01:21:33 Setting up network listener on 0.0.0.0:1984 2008-03-19 01:21:33 Setting up local listener 2008-03-19 01:21:33 Setting up signal handlers 2008-03-19 01:21:33 Setting up hobbitd channels 2008-03-19 01:21:33 Setting up logfiles Perhaps this helps: [hobbit at hobbit2 logs]$ cat clientdata.log 2008-03-19 00:22:20 Peer not up, flushing message queue 2008-03-19 00:23:52 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:23:52 Peer not up, flushing message queue 2008-03-19 00:27:20 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:27:22 Peer not up, flushing message queue 2008-03-19 00:31:53 Peer not up, flushing message queue 2008-03-19 00:32:23 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:32:23 Peer not up, flushing message queue 2008-03-19 00:32:25 Peer not up, flushing message queue 2008-03-19 00:32:26 Peer not up, flushing message queue 2008-03-19 00:32:29 Peer not up, flushing message queue 2008-03-19 00:32:32 Peer not up, flushing message queue 2008-03-19 00:32:34 Peer not up, flushing message queue 2008-03-19 00:32:37 Peer not up, flushing message queue 2008-03-19 00:32:38 Peer not up, flushing message queue 2008-03-19 00:32:42 Peer not up, flushing message queue 2008-03-19 00:32:44 Peer not up, flushing message queue 2008-03-19 00:32:45 Peer not up, flushing message queue 2008-03-19 00:32:46 Peer not up, flushing message queue 2008-03-19 00:32:48 Peer not up, flushing message queue 2008-03-19 00:32:50 Peer not up, flushing message queue 2008-03-19 00:36:42 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:36:44 Peer not up, flushing message queue 2008-03-19 00:38:11 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:38:12 Peer not up, flushing message queue 2008-03-19 00:43:53 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:43:54 Peer not up, flushing message queue 2008-03-19 00:44:42 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:44:44 Peer not up, flushing message queue 2008-03-19 00:44:44 Peer not up, flushing message queue 2008-03-19 00:44:44 Peer not up, flushing message queue 2008-03-19 00:44:45 Peer not up, flushing message queue 2008-03-19 00:44:45 Peer not up, flushing message queue 2008-03-19 00:44:46 Peer not up, flushing message queue 2008-03-19 00:44:49 Peer not up, flushing message queue 2008-03-19 00:44:50 Peer not up, flushing message queue 2008-03-19 00:44:52 Peer not up, flushing message queue 2008-03-19 00:44:53 Peer not up, flushing message queue 2008-03-19 00:48:50 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:48:51 Peer not up, flushing message queue 2008-03-19 00:51:55 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:51:56 Peer not up, flushing message queue 2008-03-19 00:53:54 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:53:56 Peer not up, flushing message queue 2008-03-19 00:58:54 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 00:58:55 Peer not up, flushing message queue 2008-03-19 01:03:56 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 01:03:56 Peer not up, flushing message queue 2008-03-19 01:08:02 Peer not up, flushing message queue 2008-03-19 01:12:24 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 01:12:24 Peer not up, flushing message queue 2008-03-19 01:13:56 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 01:13:57 Peer not up, flushing message queue 2008-03-19 01:17:17 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 01:17:19 Peer not up, flushing message queue 2008-03-19 01:18:03 Peer not up, flushing message queue 2008-03-19 01:18:58 Peer at 0.0.0.0:0 failed: Broken pipe 2008-03-19 01:18:59 Peer not up, flushing message queue 2008-03-19 01:19:00 Peer not up, flushing message queue 2008-03-19 01:19:01 Peer not up, flushing message queue 2008-03-19 01:19:02 Peer not up, flushing message queue 2008-03-19 01:19:02 Peer not up, flushing message queue 2008-03-19 01:21:38 Peer not up, flushing message queue David

3 3