July 2007 - Xymon - Xymon mailman web

PROC test question
by marco.pizzoli＠gmail.com 21 Aug '09

21 Aug '09

Hi all, I am a hobbit newby. I have a question about the PROC test: is there a way to define a test about the presence of a particular proc executed by a particular user? I'm in a situation where I have some daemons that could be started by a lot of (machine)users and so I would like to check the user the proc run as. Thanks in advance Marco

4 3

perl script
by gjohnson＠trantor.org 13 May '09

13 May '09

I've added the perl script example that Henrik provided late January to the tutorials page on The Shire. http://www.trantor.org/theshire/doku.php/tutorials:ssmodule Hopefully, Henrik won't mind. (I may be "borrowing" some of Henrik's content for the other tutorials yet to be written...of course, if someone would like to volunteer the tutorials I'd be happy to consider them for addition). If you have other ideas about tutorials or FAQs, please let me know. I'm trying to make more time for the site (interestingly, I showed a manager from one of our other groups Hobbit in passing one day...he just happened to have been looking for an easy to setup/configure monitoring solution...he's been singing the praises of Hobbit since) =G=

3 2

cupsd
by stoner-lists＠comcast.net 04 Jun '08

04 Jun '08

For those who want to monitor a cups print server, here's a definition you can put in your bb-services file: [cupsd] send "GET /printers\r\n" expect "HTTP/1.1 200 OK" port 631 Alternatively, you could just use http://host:631/printers in your bb-hosts file. The cupsd is, for monitoring purposes, a web server. -Jeff "Fun with Users #1: ln -s /dev/random /etc/motd"

2 1

zonestat : where are graphs ?
by ndorfsman＠gmail.com 02 Apr '08

02 Apr '08

Hi, I've read the question on the list...but can't find the answer. zonestat seems to work on client....but there's nothing on server ? I've followed the doc for installation...is there something to add in bbhosts ?

6 19

ntpdate question
by Dirk.Kastens＠uni-osnabrueck.de 09 Mar '08

09 Mar '08

Hi, before updating our hobbit server to version 4.2.0, I tested the ntp configuration with the bb-ntp-1_4.sh script on the client nodes. When I now configure the server to use the ntp network test instead, I realize that this doesn't work with most of our RedHat clients. I get the response ntpdate -u -q -p 2 a.b.c.d server a.b.c.d, stratum 0, offset 0.000000, delay 0.00000 29 Aug 10:53:26 ntpdate[3509]: no server suitable for synchronization found The network test works with all AIX clients and with older RedHat clients. The manual page of ntpdate on a RedHat machine says, that "the ntpdate program is to be retired from this distribution". Is there another way of testing the ntp synchronisation from the server side or do I still have to use the bb-ntp.sh script? Best wishes, Dirk Kastens

9 10

Client for NetApp storage and Weblogic Server
by fduranti＠q8.it 01 Oct '07

01 Oct '07

Hi all, I'm currently developing 3 perl client to use with Network appliance Storage, Weblogic Servers and Database (SQL/Oracle/Informix and Mysql). At this moment only the weblogic and netapp scripts are available, the database check for Oracle/Informix and with connection check to sqlserver will be probably available the next week. I uploaded the scripts to deadcat but i got some problems downloading them so I've also created a project on sourceforge and I'm uploading the scripts there (and I will also try to create a mailing list so that if users have the need to contact me they can do that there). The homepage on sourceforge is http://sourceforge.net/projects/hobbit-perl-cl/ <BLOCKED::http://sourceforge.net/projects/hobbit-perl-cl/> Thanks and sorry for the advertise but this seems the better place to let users know about hobbit clients available :D Regards Francesco Duranti

5 9

Hobbit, BBwin-0.9 and the ports column...
by rgordonjr＠gmail.com 19 Sep '07

19 Sep '07

Hello all - In looking at the client data generated by BBWin-0.9 I see that the port usage information is sent to the Hobbit server. Is there anyway to get this data displayed in the current ports column (populated by the hobbit client)? As its coming over the client channels I can create a custom server script to push the data into a new column but I'd kinda like to not have to do that... BBWin generated ports info.. --------------------------------------------- [ports] Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:7 0.0.0.0:0 LISTENING TCP 0.0.0.0:9 0.0.0.0:0 LISTENING TCP 0.0.0.0:13 0.0.0.0:0 LISTENING TCP 0.0.0.0:17 0.0.0.0:0 LISTENING TCP 0.0.0.0:19 0.0.0.0:0 LISTENING TCP 0.0.0.0:111 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:382 0.0.0.0:0 LISTENING Hobbit Client (Unix) generated port info ------------------------------------------------------------ [ports] Local Address Remote Address Swind Send-Q Rwind Recv-Q State -------------------- -------------------- ----- ------ ----- ------ ------- *.* *.* 0 0 49152 0 IDLE *.22 *.* 0 0 49152 0 LISTEN *.22 *.* 0 0 49152 0 LISTEN 10.9.12.102.17374 10.9.12.102.1352 49152 0 49152 0 ESTABLISHED 10.9.12.102.1352 10.9.12.102.17374 49152 0 49152 0 ESTABLISHED *.* *.* 0 0 49152 0 IDLE *.1352 *.* 0 0 49152 0 LISTEN *.27401 *.* 0 0 49152 0 LISTEN *.8635 *.* 0 0 49152 0 BOUND *.8640 *.* 0 0 49152 0 BOUND Thanks for the help here! -- --==[ Bob Gordon ]==--

2 1

Multiple yellow to red
by Galen.Johnson＠sas.com 07 Sep '07

07 Sep '07

Hey, I'll admit I haven't put a lot of legwork into this but...is it possible to configure hobbit to go red on a test after a certain number of cycles at yellow? I have some tests that I don't mind if they are yellow for small period but if they are there too long I need to know. I could probably handle this with a script but it'd be nice if hobbit could handle it out of the box...maybe extend COLOR or DURATION... HOST=* COLOR=3*yellow blah blah blah MAIL admin at foo.com That would alert after it was yellow for 3 cycles...or would a DURATION alert work...hurmmmmmm... =G=

4 7

Acknowledgements & History
by s_aiello＠comcast.net 06 Sep '07

06 Sep '07

All, I was curious if there was a reason why when an alert is acknowledged, why that acknowledgement is not displayed in History. In my mind an acknowledgement is a state change, i.e. Red -> to Red-acked. This would also help when performing audits on help-desk responsiveness to alerts in Hobbit. It would also help, when an alert acknowledgement expires. presently my team treats the alert as a new incident. It would be very helpful if they could check the history and see that the alert was previously acknowledged and what the ack-blurb was. Or are acks more of a BB legacy thing, and I should really be using disabled/maint of tests ? Thoughts ? ~Steve

2 2

Highlights of the 4.3.0 version
by henrik＠hswn.dk 10 Aug '07

10 Aug '07

In another thread, someone asked about what new features are planned for version 4.3.0. I've summarized them below; they have all been implemented by now. Some of them have been contributed by others over the past year - I'm pleased to have finally gotten their patches merged. There are some open bug-reports, and the plan now is to try and get those fixed. Once that is done I'll ask you all to start testing the beta-versions, and then a new release is hopefully available soon. This doesn't mean that I won't consider adding new stuff before the 4.3.0 release, but right now the plan is to get 4.3.0 shipped with the current set of features. But if I've missed someone's favourite patch or feature request, do let me know. Major new features ------------------ * PAGE setting for alert- and client-configuration handles hosts on multiple pages, so any pagename can be used. * Flap detection of statuses that change color rapidly. The status is kept at the most critical level until it stops flapping. * Holiday support for alerts, including variable holidays (Easter etc) * Split NCV support - graph data from NCV can be split into multiple RRD databases allowing for varying number of datasets. * RRD database parameters are now configurable (i.e. number of datapoints stored, whether to store min/max values etc). Note that this only applies to newly created RRD files, not existing ones. * Distributed worker modules allow sharing the load across multiple Hobbit servers * RRD updates are now cached for up to 30 minutes before being written to disk. This makes the I/O load on large installations much lighter. * Detection of statuses that are reported by multiple hosts * Client backend-support for the z/OS and z/VSE clients by Rich Smirna Display things -------------- * Graph zooming now limits the lower/upper bounds of a graph (requires rrdtool 1.2.x) * The trends page default data-period can be configured to something other than the default 48-hour view, and the user can select a different period on-the-fly. * Hosts can be sorted automatically on the overview webpage with a "group-sorted" group definition. * NOCOLUMNS setting in bb-hosts let you suppress certain columns on a per-host basis * Host-comments are displayed as tool-tips, to save screen space. Checks and graphs ----------------- * Network tests can use a specific source IP instead of the default * The validity-period of network tests is configurable, instead of being fixed at the default 30-minute setting * Client file checks can check for a symlink * "trends" report for RRD handling allows generating custom-made RRD files * Hobbit host- and status-counts are tracked in an RRD file Miscellaneous ------------- * NCV reports can handle color-icons before the name:value data * hobbitlaunch tasks can be configured to run on certain hosts only * Time-warp detection and warning * Local unix-socket interface to Hobbit daemon * hobbitd_capture can collect several statuses and hand off such a batch to an external command * Support for SHA-224/256/384/512 digests Regards, Henrik

35 93