May 2005 - Xymon - Xymon mailman web

Possible cosmetic bug
by v.everett＠afgonline.com.au 23 May '05

23 May '05

Hi Henrik A minor severity 5 bug for you. If we define our own logo in the $HOBBITLOGO variable in the hobbitserver.cfg file, the logo file cannot be found when logged into the secure admin screens (disabling a test) HOBBITLOGO="<img width=60 height=60 src="$BBSKIN/AFG.jpg" align=baseline border=0>" A workaround would be to copy the logo to the secure default directory. Cheers Vernon _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ NOTICE: This message and any attachments are confidential and may contain copyright material of Australian Finance Group Limited or a third party. It is intended solely for the purpose of the addressee and any other named recipient. If you are not the intended recipient, any use, distribution, disclosure or copying of this message is strictly prohibited. The confidentiality attached to this message is not waived or lost by reason of the mistaken transmission or delivery to any unintended party. If you have received this message in error, please notify the author immediately or contact Australian Finance Group on +61 8 9420 7888.

3 2

[hobbit] HOBBIT 4.0.3 ignoring bb-dftab
by Winn.Beutler＠mcdata.com 23 May '05

23 May '05

Sorry, my mistake. But why is it listed in the hobbitserver.cfg? I assume bb-cputab file along with bb-msgstab and the others are the same way, even though they are also listed in the file? Thanks for the help and the great product! Winn -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Wednesday, May 18, 2005 11:36 PM To: hobbit at hswn.dk Subject: Re: [hobbit] HOBBIT 4.0.3 ignoring bb-dftab On Wed, May 18, 2005 at 03:05:54PM -0600, Winn Beutler wrote: > I upgraded from BB to HOBBIT 4.0.3rc2 and notice that HOBBIT > seems to be ignoring the entries in bb-dftab. How do I > troubleshoot the problem? bb-dftab is used by the BB client. Hobbit only implements the server-side of your monitoring. Check the configuration of your client. bb-dftab needs to be installed on the clients, not the server. Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk SPECIAL NOTICE All information transmitted hereby is intended only for the use of the addressee(s) named above and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of confidential and privileged information is prohibited. If the reader of this message is not the intended recipient(s) or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that you must not read this transmission and that disclosure, copying, printing, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. Anyone who receives confidential and privileged information in error should notify us immediately by telephone and mail the original message to us at the above address and destroy all copies. To the extent any portion of this communication contains public information, no such restrictions apply to that information. (gate01)

5 13

Vmstat data for IRIX systems
by Christian.Perrier＠onera.fr 23 May '05

23 May '05

Hobbit currently does not handle vmstat data coming from IRIX systems. Indeed, on my former BB install, I hacked the bf-vmstat.sh script a little and made it use "sar" to report data to be processed like vmstat data from other hosts. The bf-vmstat.sh script I use is: #!/bin/sh # $Id: vmstat-bf.sh,v 1.1 2000/11/30 20:29:44 scott Exp $ # vmstat-bf.sh # variable definitions MET=vmstat VMSTAT=/usr/bin/sar OUT=$BBHOME/tmp/$MET.$$ ################# # COLLECT ################# # vmstat echo "$BBOSTYPE" > $OUT # get the data $VMSTAT 300 2 | $TAIL -1 >> $OUT ################## # REPORT ################## if [ $LARRDCOMM = DATA ] then $BB $BBDISP "data ${MACHINE}.$MET `$CAT $OUT`" else $BB $BBDISP "status ${MACHINE}.$MET green `date` <$MET> `$CAT $OUT`" fi rm $OUT /usr/bin/sar xx 2 output looks like that: bb at rhea:~/ext/bf-larrd> /usr/bin/sar 10 2 IRIX64 rhea 6.5 10070055 IP27 05/20/05 11:44:00 %usr %sys %intr %wio %idle %sbrk %wfs %wswp %wphy %wgsw %wfif 11:44:10 51 2 0 0 47 0 100 0 0 0 0 11:44:20 52 3 0 0 45 0 0 0 0 0 0 Average 52 2 0 0 46 0 167 0 0 0 0 The vmstat-larrd.pl entry I use is: irix => { cpu_usr => 1, cpu_sys => 2, cpu_int => 3, cpu_w => 4, cpu_idl => 5, }, How could I hack hobbit so that it may be able to deal with this ? PS : I have similar hacks for the Super-UX OS run by NEC supercomputers (I run BB clients on both of these) --

2 3

repeat counter
by cits.bogajewski＠daimlerchrysler.com 23 May '05

23 May '05

Hi folks, i am still observing incorrect indication of the repeat column value on the info page. i wonder that nobody else observes something like this.. regardless what i am configuring, there is always a value of 30 min displayed. however, i am sure this is only a display problem, since anything works as configured after all, e.g. REPEAT=5m, 60m, 24h. probably a bug? or something that is specific to my system only? Greetings btw. have a nice weekend... Anatoli Bogajewski

3 4

Larrd problem on upgrade to 4.0.3
by gsteer＠firstwave.com.au 23 May '05

23 May '05

I've just upgraded my test server to 4.0.3 and there is a problem with (I think) hobbitd_larrd. I was previously using hobbit 4.0.2 with no problem. The server is running Centos 4.0 (Redhat AS 4.0 equiv) The various config files are as installed by the hobbit install process, only the alerts file is changed. I'm providing sendmail and mailq data via the BB scripts. In the larrd-status.log I get: 2005-05-22 03:44:49 Tried to down BOARDBUSY: Invalid argument 2005-05-22 15:50:53 Gave up waiting for GOCLIENT to go low. 2005-05-22 16:37:50 Tried to down BOARDBUSY: Invalid argument 2005-05-23 04:18:51 Gave up waiting for GOCLIENT to go low. 2005-05-23 16:45:29 Tried to down BOARDBUSY: Invalid argument 2005-05-23 17:08:36 Tried to down BOARDBUSY: Invalid argument 2005-05-23 17:10:07 Tried to down BOARDBUSY: Invalid argument In the larrd-status.log I get: 2005-05-23 17:10:07 Tried to down BOARDBUSY: Invalid argument *** glibc detected *** corrupted double-linked list: 0x00479838 *** 2005-05-23 17:11:45 Worker process died with exit code 134, terminating *** glibc detected *** corrupted double-linked list: 0x00479838 *** 2005-05-23 17:12:54 Worker process died with exit code 134, terminating ANy suggestions? I was planning to put the server in as a production server tomorrow morning :-( Regards Geoff

2 2

Apache RRD
by Alexander.Sprotte＠eventim.de 23 May '05

23 May '05

Hi all at hobbit.list, a new version is out and it's running fine... But my Apache problem exists further. I can not monitoring the Apache-Status. If I into the configuration the following line insert: xxx.xxx.xxx.xxx www.xxxxxxxxx.com # ssh http://www.xxxxxxx.com/xxxxx.htm apache=http://www.xxxxxxx.com/server-status?auto LARRD:*,apache:apache|apache1|apache2|apache3 then hobbit say's -> "BBTEST "red" Programm crashed Fatal signal caught!" But the LARRD graph for Apache its running but all other tests not! Whats Wrong ??? I use Hobbit 4.0.3 on SuSE Linux 9.2 The gdb say's (bbtest-net) #4 0x401a6d41 in raise () from /lib/tls/libc.so.6 #5 0x401a8529 in abort () from /lib/tls/libc.so.6 #6 0x0805ca12 in sigsegv_handler (signum=11) at sig.c:57 #7 <signal handler called> #7544 0x4000d6ae in _dl_name_match_p () from /lib/ld-linux.so.2 Previous frame inner to this frame (corrupt stack?) (bbgen) #4 0x401a6d41 in raise () from /lib/tls/libc.so.6 #5 0x401a8529 in abort () from /lib/tls/libc.so.6 #6 0x0805ca12 in load_all_links () at links.c:130 #7 <signal handler called> #7544 0x4000d6ae in _dl_name_match_p () from /lib/ld-linux.so.2 Previous frame inner to this frame (corrupt stack?) Please help..... Cheers... Alexander Sprotte ------------------------------------------------------ Alexander Sprotte [mailto:alexander.sprotte at eventim.de]

2 2

Hobbit 4.0.3 released
by henrik＠hswn.dk 23 May '05

23 May '05

Version 4.0.3 of the Hobbit Monitor was uploaded to sourceforge.net a few minutes ago. This release adds a new maintenance script, native to Hobbit, so Hobbit no longer relies on any external tools for the core functionality. Beginning with this release, Hobbit can no longer be used as an add-on to Big Brother. Hobbit retains compatibility with BB clients and extension scripts, but you can no longer run eg. the Hobbit network test tool and have it report to a Big Brother server. All log files have been moved to the Hobbit log-directory, usually /var/log/hobbit/. If you have scripts that access these, you should change them or setup links for the old locations of the BBVAR/acks/* logfiles. Commandline options for all of the CGI tools have been collected into a "hobbitcgi.cfg" file. If you have customized your CGI scripts with additional commandline options, you should put them into this file instead of modifying the CGI wrappers directly, to ease upgrading. And of course, a number of bugs have been fixed. I am grateful to the people on the Hobbit mailing list for their great effort with reporting bugs, suggesting improvements and testing the early versions. The changelog for this release is included below. Regards, Henrik Changes from 4.0.2 -> 4.0.3 --------------------------- Bugfixes (general): * The bb-datepage and bbmessage CGI tools were reading the POST data in an incorrect way; it worked on most systems, but did not adhere to the CGI specification. Bugfixes (alerting): * Acknowledgments were broken in 4.0.2. * Using PAGE=... in hobbit-alerts.cfg to pick out hosts on the front-page was not possible. The front page is now recognized with the name "/", so PAGE=/ will find them. * The hobbitd_alert --test option would not pick up the correct page-path settings from the bb-hosts file. * The BBALPHAMSG text passed to scripts as a default alert message now includes the URL link to the statuslog. Bugfixes (graphs and trends): * hobbitgraph.cgi could show "@RRDPARAM@" on graphs if it was matched by a NULL string (would happen for mailq graphs). * RRD files were not being updated while a status was blue (disabled), even though status messages were received. Changed so that blue logs are passed off to the RRD * The "disk1" graph definition failed to take into account that the numbers logged were already in KB of data. So the axis-label was wrong. parser - we might as well track data when it's there. * The "mailq" RRD handler now finds the queue-length regardless of whether it is before or after the "requests" keyword in the "mailq" or "nmailq" status message. * If the "apache" data collection was specified for a host, but the host had no "http" tests, a bogus http status report was being generated. * Network statistics used a conversion that would overflow on 32-bit systems. Bugfixes (web pages): * Some header/footer files for the snapshot report were missing. * The "info_header" and "info_footer" files were not being used for the "info" column pages. Bugfixes (installation): * Fix file-descriptor leak in the "setup-newfiles" tool used during installation. This could cause "make install" to abort while installing new files, on systems with a low setting for the max. number of simultaneous open files. * Some systems keep libraries in a /lib64 directory - this was not being searched by the configure script. * If Hobbit was built without SSL support and an SSL network test is configured, it will now always fail with a meaningful error message. * If the configure script found SSL- or LDAP-libraries, but these could not link, the build would not disable SSL- and LDAP-support and therefore it failed. If the libraries do not work, disable the support. * The SSL test would link without required network support libraries on some platforms. * The options for overriding SSL- and LDAP-include files did not match the documented name. * AIX systems built with gcc were missing the OSDEF compile- flags. Improvements: * All remnants of Big Brother compatibility have been removed. If you want to stick with the old Big Brother tool, use bbgen. This allowed for some much needed cleaning up of the bbgen code that loaded the status data, especially for the handling of purple status logs. Also, the sending of messages has dropped all support for the Big Brother method of sending "page" messages when a status-message is sent with an alert-color, so the BBPAGE and BBPAGERS settings are no longer used. * The maint.pl script has been removed. A new tool, hobbit-enadis.cgi, replaces this with a native Hobbit tool. If you are upgrading, you should change the ~/server/www/menu/menu_items.js file to point link to "hobbit-enadis.sh" instead of "maint.pl". * The "info" column page now includes a form to disable and enable tests for a single host. If you prefer not to have this on the info page, add the option "--no-disable" to the hobbit-cgi/bb-hostsvc.sh wrapper. * Some logfiles have been moved to the normal log-file directory - /var/log/hobbit: - nkstatus.log (from ~hobbit/server/) - notifications.log (from ~hobbit/data/acks/) - acklog (from ~hobbit/data/acks), also renamed to acknowledge.log * The hobbit-mailack CGI will now find a "delay=DURATION" line in the mail message, and use that as the duration of the acknowledgment. Reports show that there are some types of mail/SMS systems where you cannot modify the message subject. * Paul D. Backer contributed "favicon" images generated from the Hobbit "recent" GIF files. These have been added and are now loaded from the Hobbit web/*_header files, so that browsers supporting this (Mozilla, Firefox) will display a favicon-image in the titlebar or on the page-tab holding the Hobbit webpage. * Two new settings in hobbitserver.cfg can be used to restrict which filesystems are being tracked by Hobbit. The NORRDDISKS / RRDDISKS settings are regular-expressions that the filesystem names are matched against. See the hobbitserver.cfg(5) man-page. * Hobbit now works with RRDtool 1.2.x. Due to a bug in the first 1.2.x releases of RRDtool, you must use at least version 1.2.2 with Hobbit. * A new report-output option lets you save a CSV (comma- separated values) file with the availability data for each host+test in Hobbit. This allows for further processing of the availability data eg. importing it into a spreadsheet. This can be selected from the report request webpage. * It is now possible to define different values for an environment setting in hobbitserver.cfg, depending on a new "--area=..." command-line option for all tools. See hobbitserver.cfg. * Apache 1.x performance data are now graphed correctly, by mapping the "BusyServers/IdleServers" data into the BusyWorkers/IdleWorkers datasets used by Apache 2.0 RRD graphs. * sendmail RRD's for sendmail 8.13+ now tracks the number of "quarantined" messages also. You must delete any existing sendmail.rrd files for this new data item to be tracked. * All RRD-updates now use the RRDtool "--template" option to map values to RRD datasets. This should keep us from updating datasets with wrong values. * Graphs can now get their title from a script, instead of using a static string in hobbitgraph.cfg. This lets you e.g. pick up the graphtitle from the mrtg.cfg. * All CGI's now pick up commandline options from a new configuration file, hobbitcgi.cfg. This is to ease packaging and make sure the CGI's can be updated without losing local configurations. * The debian- and rpm-specific packaging files are now included in the distribution tarfile. * A historical status-log now includes a "Full History" button to go to the history overview. * "irix" is now recognized as operating system. A preliminary vmstat RRD will be generated, but this may change in a future version. "netstat" reports are not yet handled. -- Henrik Storner

5 12

AW: [hobbit] Apache RRD
by Alexander.Sprotte＠eventim.de 23 May '05

23 May '05

Hi Henrik, I have now add the Apache Test on the local Apache where Hobbit is running and its running fine. No crash on problem... :) But the remote test crashed :( Alex > -----Ursprüngliche Nachricht----- > Von: Henrik Stoerner [mailto:henrik at hswn.dk] > Gesendet: Montag, 23. Mai 2005 14:17 > An: hobbit at hswn.dk > Betreff: Re: [hobbit] Apache RRD > > On Mon, May 23, 2005 at 02:11:25PM +0200, Alexander.Sprotte at eventim.de > wrote: > > >If not, I'd like to see the output from > > > > Here is it: > > > > bbcmd bbtest-net --debug --ping --checkresponse > > 2005-05-23 14:03:12 Using default environment file > > /home/hobbit/server/etc/hobbitserver.cfg > > Aborted (core dumped) > > Hrm, something funky going on with the option passing there. > Try this instead: > > * login as the hobbit user > * run "bbcmd" (this starts a sub-shell with all of the Hobbit > environment defined). > * run "bbtest-net --debug --ping --checkresponse --no-ares" > > > Henrik > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk >

1 0

AW: [hobbit] Apache RRD
by Alexander.Sprotte＠eventim.de 23 May '05

23 May '05

>On Mon, May 23, 2005 at 02:11:25PM +0200, Alexander.Sprotte at eventim.de >wrote: >> >If not, I'd like to see the output from >> >> Here is it: >> >> bbcmd bbtest-net --debug --ping --checkresponse >> 2005-05-23 14:03:12 Using default environment file >> /home/hobbit/server/etc/hobbitserver.cfg >> Aborted (core dumped) >Hrm, something funky going on with the option passing there. >Try this instead: >* login as the hobbit user >* run "bbcmd" (this starts a sub-shell with all of the Hobbit > environment defined). >* run "bbtest-net --debug --ping --checkresponse --no-ares" The test is running and crash. 2005-05-23 14:20:15 Adding to combo msg: status www1,xxxxxx,com.http green Mon May 23 14:20:05 2005: OK 2005-05-23 14:20:15 Recipient listed as '10.129.11.101' 2005-05-23 14:20:15 Standard BB protocol on port 1984 2005-05-23 14:20:15 Will connect to address 10.129.11.101 port 1984 2005-05-23 14:20:15 Connect status is 0 2005-05-23 14:20:15 Sent 32981 bytes 2005-05-23 14:20:15 Closing connection Aborted (core dumped) Alex To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

AW: [hobbit] Apache RRD
by Alexander.Sprotte＠eventim.de 23 May '05

23 May '05

Hi.... >Yes, there are a couple of bugs that haven't been dealt with in >4.0.3 - because I decided that they were so specific to your setup >that I wouldn't hold up the release any more. >Try adding "--no-ares" to the bbtest-net commandline in >hobbitlaunch.cfg. Does that help ? No, there is the part of the hobbitlaunch.cfg [bbnet] ENVFILE /home/hobbit/server/etc/hobbitserver.cfg NEEDS hobbitd CMD bbtest-net --no-ares --report --ping --checkresponse LOGFILE $BBSERVERLOGS/bb-network.log INTERVAL 5m >If not, I'd like to see the output from Here is it: bbcmd bbtest-net --debug --ping --checkresponse 2005-05-23 14:03:12 Using default environment file /home/hobbit/server/etc/hobbitserver.cfg Aborted (core dumped) >because the gdb trace is so messed up I cannot figure out >where the real problem happens. I use "gdb bin/bbtest-net tmp/core" is it right ?? Regards, Alex To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

2 2