June 2005 - Xymon - Xymon mailman web

bb-disk_by_fs.sh
by iqbala-hobbit＠qwestip.net 29 Jan '06

29 Jan '06

Hi All Has anyone used bb-disk_by_fs.sh with BB client? I am trying to find out how it will work with HOBBIT? There are few things I am concern about. 1. How will I manage alerts per partition which this script offers? 2. How will the graph work? Thanks for any feedbacks. I guess I could always try it myself on a test system if there is no feedback already. -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu "It is not the strongest of the species that survives, not the most intelligent, but the one most responsive to change." - Charles Darwin

2 2

[hobbit] Changing default graph resolution
by v.everett＠afgonline.com.au 22 Dec '05

22 Dec '05

Hi all Anybody help me with graphing? In hobbitgraph.cfg, I have the following definition, and it produces wonderful, but somewhat cluttered graphs. ---snip--- [ora9-sga] FNPATTERN tablespace.rrd TITLE TableSpace Utilization YAXIS % Full DEF:xdb at RRDIDX@=@RRDFN@:siebprd_XDB:AVERAGE DEF:whsidx at RRDIDX@=@RRDFN@:siebprd_WHS_INDEX:AVERAGE DEF:whsdata at RRDIDX@=@RRDFN@:siebprd_WHS_DATA:AVERAGE DEF:users at RRDIDX@=@RRDFN@:siebprd_USERS:AVERAGE DEF:undotbs1 at RRDIDX@=@RRDFN@:siebprd_UNDOTBS1:AVERAGE DEF:tools at RRDIDX@=@RRDFN@:siebprd_TOOLS:AVERAGE DEF:system at RRDIDX@=@RRDFN@:siebprd_SYSTEM:AVERAGE DEF:siebind at RRDIDX@=@RRDFN@:siebprd_SIEB_INDEX:AVERAGE DEF:siebdata at RRDIDX@=@RRDFN@:siebprd_SIEB_DATA:AVERAGE DEF:loader at RRDIDX@=@RRDFN@:siebprd_LOADER_DATA:AVERAGE LINE2:xdb at RRDIDX@#@COLOR@:XDB LINE2:whsidx at RRDIDX@#@COLOR@:WHS_INDEX LINE2:whsdata at RRDIDX@#@COLOR@:WHS_DATA LINE2:users at RRDIDX@#@COLOR@:USERS LINE2:undotbs1 at RRDIDX@#@COLOR@:UNDO LINE2:tools at RRDIDX@#@COLOR@:TOOLS LINE2:system at RRDIDX@#@COLOR@:SYSTEM LINE2:siebind at RRDIDX@#@COLOR@:SIEB_INDEX LINE2:siebdata at RRDIDX@#@COLOR@:SIEB_DATA LINE2:loader at RRDIDX@#@COLOR@:LOADER -u 100 -l 0 ---snip--- How do I get it to split this across 2 or even 3 graphs, like the disk utilisation graphs. 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 3

rrd graphs for bb-xsnmp.pl script
by rdeal＠tigr.org 27 Sep '05

27 Sep '05

I had a lot of graphs for several routers, ups, etc but they seem to be rather hosed. It looks like the data that was transferred is graphed well but no new data is going in correctly. It seems that any script sending data in a status message is not working. I suspect due to the formatting. One example is bb-xsnmp.pl script. I am using against routers, switches and apc ups. Using an APC ups as an example I get this in the web page: Tue Apr 5 09:23:03 2005 green UPS Temperature: 37? C bb-xsnmp.pl Version: 1.78 but in hobbit/data/rrd/apc1.tigr.org I have: tcp.conn.rrd tcp.telnet.rrd temperature.UPS_Temperature:_37&deg_C.rrd temperature.UPS_Temperature:_38&deg_C.rrd and the graph on the temperature page has no data but two entries at the bottom for UPS_Temperature:_37&deg_C and UPS_Temperature:_38&deg_C This problem is much worse on my switches and routers which have a different line for each sensor and every temperature ever reported.

3 2

Hobbit 4.0.4 released
by henrik＠hswn.dk 27 Aug '05

27 Aug '05

Version 4.0.4 is now available on SourceForge: https://sourceforge.net/project/showfiles.php?group_id=128058&release_id=33… This fixes the bugs reported since Hobbit 4.0.3 was released. The only new stuff in this release is a new "beastat" utility to collect performance statistics from an BEA Weblogic server via SNMP. This replaces the old "bea-snmpstats" script, and should work for sites with a large number of BEA instances per server. This is still somewhat experimental, but I am interested to hear reports of it working or not. (It's been tested with Weblogic ver. 8). The Changelog is appended. Regards, Henrik Changes from 4.0.3 -> 4.0.4 --------------------------- Bugfixes: * "nodisp" tag re-implemented for hosts that should not appear on the Hobbit webpages. * Enabling the "apache" data collection could crash bbtest-net if the /server-status page returned was larger than 32 KB. * The "bbcmd" tool would not pass a --debug option to the command it was running. * Nested macros in hobbit-alerts.cfg were not working. * Using TAB's in hobbit-alerts.cfg could confuse the alert module. * hobbitd_alert's --test option now determines the page-name for a host automatically. It will also now accept a time-parameter to simulate how alerts are processed at specific time-of-day. * Status messages from "dialup" hosts should not go purple. * The "mailq" RRD handler would pick up the first number from the "requests" line, which might not be the right number. * Scheduling a "disable" did not work. * The startup-script was modified to correctly handle stale PID files left over from an unclean shutdown of Hobbit. These are now removed, and startup will proceed normally. Improvements: * CGI tools now log error-output to dedicated logs in /var/log/hobbit/ * The "bea-snmpstats.sh" script has been removed, and replaced with an enhanced tool "beastat". This collects statistics via SNMP from BEA Weblogic servers, and reports these via "data" messages to Hobbit. The data collected are run-time data for the JRockIT JVM and thread/memory utilization data from each Weblogic server instance. * The "ntpstat" RRD handler now accepts the raw output from "ntpq -c rv" * The heartbeat-timeout for hobbitd has been increased to 60 seconds.

3 16

bb-hostedit v1.1 beta released
by EES2Y＠hscmail.mcc.virginia.edu 25 Jul '05

25 Jul '05

Get it here: http://www.nerdvana.org/eric/files/bb-hostedit-1.1b.tar.gz Once you guys have beaten on it for a little bit, I'll put it up on deadcat (although I'll make all the options set to the bigbrother defaults when I do that). Regards, -Eric Schwimmer Network Engineer UVA HSCS Network Engineering

3 2

[hobbit] upgrade to 4.0.4, barrage of purples forhttp/smtp/dns queries
by blysik＠shutterfly.com 15 Jul '05

15 Jul '05

> > That makes sense. What options does hobbit use for ntpdate > to check > > an ntp server? I want to run it by hand and see what happens. > > ntpdate -u -q -p 2 HOSTNAME Yes, that command just sits there. Would it be possible to add some sort of timeout in bbtest-net where if ntpdate doesn't return within an amount of time it will just kill it? -- Bruce Z. Lysik <blysik at shutterfly.com> Operations Engineer The information contained in this message (including any attachments) may be confidential. This message (including any attachments) is intended to be read only by the recipient(s) to whom it is addressed. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Shutterfly by telephone at (650) 610-5200 and delete or destroy any copy of this message (including any attachments).

2 1

Current development plans
by henrik＠hswn.dk 13 Jul '05

13 Jul '05

It seems version 4.0 has reached some stability - there are still a few odd bug reports, but nothing that looks like major problems. So I thought it would be worthwhile to let you know what my plans are. First, I'm currently pretty busy with other stuff so questions raised here are not being answered as quickly as I'd like to. Rest assured that they have not been forgotten, and I will look at all of the reports and questions - but probably not very much for the next week or so. I'm currently working on a 4.0.5 release which will be a performance- improvement release. The current Hobbit code has a flaw in the alert- module, that makes it use much more CPU time than it should - especially if you have a large number of statuses that are in an alert state, but which do not have any recipients defined in hobbit-alerts.cfg. This will be released sometime in June. But summer is upon us, and that means less development activity - so things will slow down as the temperature rises. So don't expect a lot of activity during the summer. When I pick up speed again, I haven't yet decided if I should go for the alert/acknowledge improvements that I've talked about for some time, or if I should tackle the issue of a Hobbit client and get that into a reasonable shape for the more common platforms. I have some ideas for a rather different client architecture than the current one, and the client is also *the* missing piece of the whole Hobbit puzzle - so I could be tempted to get that done. I'd like some feedback on what you find most urgent. Regards, Henrik

10 13

RRD sometimes not updated in custom graphs
by anton.burkhalter＠gmx.net 13 Jul '05

13 Jul '05

Hi all, My custom RRD's are sometimes not updated, when the server receives two or more messages in a short interval from different clients. Thanks for any help Tony anton.burkhalter at gmx.net Here is the full story... Operating system: Tru64 OSF1 V5.1B 2650 alpha hobbitserver 4.0.4 Output from larrd.sh in debug mode written to larrd-test.log, ==> no missing entries here; there is every 5 min. a new entry like the following: 2005-06-20-18:26:34 p1 : foo.example.com p2 : envmon p3 : /usr/local/hobbit/server/tmp/rrd_msg_660975 # content of file $p3: data foo,example,com.envmon System Temperature:31 Treshold:48 # values extracted: DTEMP: 31 DTRESH: 48 ---------------------------------------------------- The following output is created by larrd.sh: echo "DS:temp:GAUGE:600:0:100" echo "envmon.temp.rrd" echo "$DTEMP" echo "DS:temp:GAUGE:600:0:100" echo "envmon.tresh.rrd" echo "$DTRESH" ---------------------------------------------------- Here is the relevant extract of the lard module running in debug mode, # grep foo larrd-data.log | awk '{printf "%s %s %s %s %s\n",$1,$2,$3,$4,$5}' 2005-06-27 18:32:59 hobbitd_larrd: Got message 2005-06-27 18:37:59 hobbitd_larrd: Got message 2005-06-27 18:37:59 RRD update param 2005-06-27 18:37:59 RRD update param 2005-06-27 18:43:01 hobbitd_larrd: Got message 2005-06-27 18:48:04 hobbitd_larrd: Got message 2005-06-27 18:48:04 RRD update param 2005-06-27 18:48:04 RRD update param 2005-06-27 18:53:07 hobbitd_larrd: Got message 2005-06-27 18:58:09 hobbitd_larrd: Got message 2005-06-27 19:03:12 hobbitd_larrd: Got message 2005-06-27 19:08:14 hobbitd_larrd: Got message 2005-06-27 19:08:14 RRD update param 2005-06-27 19:08:14 RRD update param 2005-06-27 19:13:18 hobbitd_larrd: Got message 2005-06-27 19:18:17 hobbitd_larrd: Got message 2005-06-27 19:23:18 hobbitd_larrd: Got message 2005-06-27 19:28:21 hobbitd_larrd: Got message 2005-06-27 19:33:25 hobbitd_larrd: Got message 2005-06-27 19:33:26 RRD update param 2005-06-27 19:33:26 RRD update param 2005-06-27 19:38:28 hobbitd_larrd: Got message 2005-06-27 19:38:28 RRD update param 2005-06-27 19:38:28 RRD update param 2005-06-27 19:43:32 hobbitd_larrd: Got message 2005-06-27 19:43:32 RRD update param 2005-06-27 19:43:32 RRD update param 2005-06-27 19:48:32 hobbitd_larrd: Got message The problem is that the RRD file is sometimes not updated, "Got message" but no RRD update in the log: 18:53:00 : Got message 3148 @@data#3148|1119891180.345343|172.22.1.10||bar.example.com|envmon 18:53:07 : Got message 3149 @@data#3149|1119891187.408847|172.22.1.11||foo.example.com|envmon 18:53:48 : Got message 3150 @@data#3150|1119891228.963696|172.22.1.12||dum.example.com|envmon 18:53:49 : RRD update param 00: 'rrdupdate' 18:53:49 : RRD update param 01: '/usr/local/hobbit/data/rrd/dum.example.com/envmon.temp.rrd' 18:53:49 : RRD update param 02: '-t' 18:53:49 : RRD update param 03: 'temp' 18:53:49 : RRD update param 04: '1119891228:41' 18:53:49 : RRD update param 00: 'rrdupdate' 18:53:49 : RRD update param 01: '/usr/local/hobbit/data/rrd/dum.example.com/envmon.tresh.rrd' 18:53:49 : RRD update param 02: '-t' 18:53:49 : RRD update param 03: 'temp' 18:53:49 : RRD update param 04: '1119891228:50' --------------------------------- This is the definition in hobbitgraph.cfg [envmon] FNPATTERN envmon.(.*).rrd TITLE System Temperature YAXIS Temperature(C) DEF:p at RRDIDX@=@RRDFN@:temp:AVERAGE LINE2:p at RRDIDX@#@COLOR@:@RRDPARAM@ -l 0 GPRINT:p at RRDIDX@:LAST: \: %5.1lf (cur) GPRINT:p at RRDIDX@:MAX: \: %5.1lf (max) GPRINT:p at RRDIDX@:MIN: \: %5.1lf (min) GPRINT:p at RRDIDX@:AVERAGE: \: %5.1lf (avg)\n ------------------------------------- This is the part in hobbitlaunch.cfg: [larrddata] ENVFILE /usr/local/hobbit/server/etc/hobbitserver.cfg NEEDS hobbitd CMD hobbitd_channel \ --channel=data \ --log=$BBSERVERLOGS/larrd-data.log \ hobbitd_larrd \ --rrddir=$BBVAR/rrd \ --extra-script=/usr/local/hobbit/server/ext/larrd.sh \ --extra-tests=fdmns,envmon \ --debug --------------------------------------

2 1

--purplelifetime
by rower.master＠gmail.com 13 Jul '05

13 Jul '05

Friends, When I was running bbgen I used to configurate the --purplelifetime=600 , I know that this is deprecated now, my question is if exists a way to reduce the actual 30 minutes purplelifetime ? Rgds, Mario.

2 1

badntp
by patrick_a_vaughan＠hotmail.com 12 Jul '05

12 Jul '05

Is it me, or does badntp in the bb-hosts file not work? I have several servers running NTP, and they occasionally (several times a day) will lose their sync for a few minutes while they switch between higher stratum servers. It would be nice if hobbit wouldn't change to a "red" state.

4 4