- Xymon - Xymon mailman web

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

How hobbit server deal with DNS server failure when doing conn test ?
by tj_yang＠hotmail.com 19 Mar '08

19 Mar '08

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#H… tj

2 1

New Hobbit Release...
by dns1407＠yahoo.com 19 Mar '08

19 Mar '08

Hi, Can anyone tell when the new release of The Hobbit will be available? Thanks... DNS ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

[hobbit] Nesting rules in hobbit-alerts.cfg
by gumby3203＠gmail.com 18 Mar '08

18 Mar '08

Is it possible to nest rules in hobbit-alerts.cfg? For example, can I do something like this (indenting provided for readability): PAGE=hostPageA NOTICE RECOVERED HOST=hostA,hostB,hostC MAIL pager at somewhere.com HOST=%(hostD[0-9]) MAIL email at somewhere.com Our alerting rules are starting to get kind of complex, and nesting alert rules as above would make things easier. I know I could do something like: PAGE=hostPageA NOTICE RECOVERED MAIL pager at somewhere.com HOST=hostA,hostB,hostC MAIL email at somewhere.com HOST=%(hostD[0-9]) But some of the HOST= lists are very long (i.e. wrap across multiple lines), so the above 2nd example would look a lot uglier than it does in this post (which was simplified for readability). If nesting rules won't work, I wonder how much effort would be involved in adding this feature.

4 4

[hobbit] Hobbit on Wikipedia
by bewhite＠fellowes.com 17 Mar '08

17 Mar '08

Not sure but here are some ideas. Installation and configuration change ease? Identifies status change in the last 24 hours? Ease of changing how monitored host appears in user interface? Thickness of the client? Built in report generation? Availability reporting? ......Bruce _____ From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Monday, March 17, 2008 3:18 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit on Wikipedia Ooh, I see. Also, Buchan - you're adding email addresses in your response. All you have to do is retain the subject and reply to hobbit at hswn.dk <mailto:hobbit at hswn.dk> so it will be distributed to everyone =) Does anyone know of additional features that we should be putting on the Wiki page? On 3/17/08, Buchan Milne <bgmilne at staff.telkomsa.net <mailto:bgmilne at staff.telkomsa.net> > wrote: On Monday 17 March 2008 15:50:47 Josh Luthman wrote: > The way I see trends being is a line graph, as those produced by Hobbit. > Does anyone else see things this way? Yes, that is what I understood, which is why I changed trending to Yes. However, I suspect they mean something else by "Charts" (e.g. pie charts etc.). -- 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 next Hobbit release (NOT "when is it due")
by gumby3203＠gmail.com 17 Mar '08

17 Mar '08

Quick question about the next version of Hobbit... Currently in 4.2.0 (latest patches), the "info" page doesn't correctly show the alert rules when using the GROUP directive. (I believe this was mentioned before on this mailing list). I'm just curious if the feature set for 4.3.0 (or whatever the next version will be numbered) has been frozen, and if this will be fixed. If it's not frozen and not currently in the code, would it be possible to add it to the next version?

6 10