- Xymon - Xymon mailman web

[hobbit] Cpu-test going blue instead of red or yellow 4.0.2
by dhd733＠yahoo.se 11 Apr '05

11 Apr '05

Henrik Stoerner <henrik at hswn.dk> wrote: > What's the DOWNTIME setting for that host ? It's the only way it can go blue if you are not disabling it. Of course you are right, but why is it going green? There was a DOWNTIME. /Lars Hobbithobbyist "If you run UNIX and you don't have a UPS, you should see a psychiatrist...." --Byte Magazine (years ago)

2 1

Cpu-test going blue instead of red or yellow 4.0.2
by dhd733＠yahoo.se 11 Apr '05

11 Apr '05

Regards Lars Hobbithobbyist "If you run UNIX and you don't have a UPS, you should see a psychiatrist...." --Byte Magazine (years ago)

2 1

RRS Feed says No Critical Alerts
by iqbala-hobbit＠qwestip.net 11 Apr '05

11 Apr '05

Hi I use KNewsTicker to look at my RSS Feed from bigbrother and it always says 'No Critical Error' even when I have 'red' alerts. But when I click on the Feed link I can access the bigbrother site and can see the alerts. I am using bbgen like this in my bbdisplay section CMD bbgen --hobbitd --recentgifs --pagetitle-links --maxrows=12 --pagetext-headings --no-underline-headings --ignorecolumns=maint,scanmsg --subpagecolumns =2 --report --rss --rsslimit=yellow Also I noticed the Feedlink is pointing at https://hobbit.site.net/hobbit/bb.rss and when I click it it takes me to the default /hobbit/ page. Thanks for any help/suggestions -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu "..there are two kinds of people: those who work and those who take the credit...try to be in the first group;...less competition there." - Indira Gandhi

2 2

Error running gmake install
by dhd733＠yahoo.se 11 Apr '05

11 Apr '05

Hi, I have tested to run make install on 2 machines (32-bits and 64-bits kernels). I get the same error on both: cd webfiles; find . ö grep -v RCS ö grep -v DIST ö ../../build/setup-newfiles /o pt/hobbit/server/web/ ../../build/md5.dat Loading md5-data ... OK Installing new file /opt/hobbit/server/web/report_form_daily Installing new file /opt/hobbit/server/web/report_form_weekly /bin/sh: 23720 Memory fault(coredump) gmakeÄ1Å: *** Äinstall-cfgÅ Error 139 gmakeÄ1Å: Leaving directory é/opt/hobbit/hobbit-4.0.2/hobbitd' gmake: *** Äinstall-hobbitdÅ Error 2 Regards Lars Hobbithobbyist "If you run UNIX and you don't have a UPS, you should see a psychiatrist...." --Byte Magazine (years ago)

2 2

hobbitd_alert column
by allan＠zandahar.net 11 Apr '05

11 Apr '05

Hi all, I have just upgraded to the latest release of hobbit (moved old dir out and rebuilt so there were no old files) and I am now seeing a new column on the hobbit display page called hobbitd_alert and its staying red. Open it up and it says -Program crashed Fatal signal caught! I can't say I rememebr ever seeing this column ever appear before. Anoher thing is its still doing all of its alerts perfectly so I'm not sure why I'm getting this red msg. If someone could possibly shed some light on the situation it would be greatly appreciated Cheers Allan NB: Keep up the kick a$$ work with hobbit :)

2 3

Connectiontest
by dhd733＠yahoo.se 11 Apr '05

11 Apr '05

Hi, I would like to run the connectiontests more frequent. Is that possible? Regards Lars Hobbithobbyist "If you run UNIX and you don't have a UPS, you should see a psychiatrist...." --Byte Magazine (years ago)

2 1

Hobbit 4.0.2 released
by henrik＠hswn.dk 10 Apr '05

10 Apr '05

Hobbit 4.0.2 was uploaded to hobbitmon.sourceforge.net a few minutes ago and should be available by the time you read this. This is primarily a bug-fix update of the 4.0 release, with fixes for the bugs that have been reported after the initial release. Thanks to all who have contributed fixes, bug-reports and enhancement suggestions. One change done in 4.0.2 may require that you change your configuration. The "--alertcolors", "--okcolors" and "--repeat" options for hobbitd and hobbitd_alert have been removed, and replaced with three settings in the hobbitserver.cfg file: ALERTCOLORS, OKCOLORS and ALERTREPEAT respectively. You should remove these options from the hobbitlaunch.cfg file, and setup the hobbitserver.cfg equivalents instead. Note that these options are not used in the default hobbitlaunch.cfg, so unless you added them yourself then you don't need to worry about it. A new feature introduced in 4.0.2 is the possibility of defining default tags in the bb-hosts file. If you define a host named ".default." in the bb-hosts file, then the configuration tags you apply to this host will be used as defaults for the hosts that follow it. E.g. the following configuration 0.0.0.0 .default. # DOWNTIME=*:0200:0600 10.0.0.1 www.foo.com # http://www.foo.com/ 10.0.0.2 db.foo.com # oratns will cause the "www.foo.com" and "db.foo.com" to have a DOWNTIME setting of "*:0200:0600". The ".default." host is used only for this type of configuration tags, it does not appear on the generated webpages and no network testing is done on it. You can have multiple ".default." definitions in the bb-hosts file; for any host, the .default. immediately above is the active one. Also new in 4.0.2 is the "hobbitreports.sh" script, which shows how you can pre-build daily/weekly/monthly availability reports. An accompanying new CGI - bb-datepage.cgi - lets you select these pre-built reports from a simple date-selection form. And finally, the data generated for the "info" and "trends" columns is now fully dynamic, meaning that it is always up-to-date. The bb-infocolumn and bb-larrdcolumn tasks can be removed from hobbitlaunch.cfg. Regards, Henrik

2 1

Hobbit 4.0.2 beta
by henrik＠hswn.dk 10 Apr '05

10 Apr '05

I've packed up what will probably be a 4.0.2 release, and you can find it now at http://www.hswn.dk/beta/ If someone feels like giving it a quick try-out, I'd appreciate it. There are a two configuration changes you should do when installing this: * The --alertcolors, --okcolors and --repeat options for hobbitd_alert and hobbitd have been moved into a environment variables. I know some of you were using these, so you should do this change (remove the options from hobbitlaunch.cfg, and set the variables in hobbitserver.cfg instead). * The bb-infocolumn and bb-larrdcolumn tasks should be removed. These tools no longer exist, the info- and trend-columns are generated on-the-fly when requested. Changelog below. Regards, Henrik Changes from 4.0 -> 4.1 ----------------------- Bugfixes: * "meta" reports could crash hobbitd. * Parsing of HTTP responses could crash bbtest-net. * Eventlog entries from hosts not in bb-hosts would crash the eventlog CGI reporting tool. * bbgen would crash when FQDN was set to FALSE (not default) and a host was in bb-hosts with the fully-qualified name. * The external rrd-module might launch more than one script simultaneously, which resulted in the status message being lost. * AS/400 disk reports were not handled correctly by the RRD module, since the format was different from what was expected. * bbtest-net would do DNS lookups of hostnames when run with the "--dns=ip" option, causing a severe slowdown. * When viewing historical disk reports from Unix systems, the "Status unchanged in ..." message might be included in the last line of the disk status report, instead of being on a line by itself at the bottom of the page. * "badconn" tags were not being recognized. Eric Schwimmer found the problem and even provided a patch. * On Solaris, the HOME environment variable may not be defined if Hobbit is started from a bootup-script. This caused network tests to stop running. * Historical logs that are saved when a host is disabled or goes purple would not reflect the blue/purple color, but the color of the status before it was disabled or went purple. * A spelling error in the hobbitgraph.cfg file caused the hobbitgraph CGI to crash when trying to generate mailq graphs. * Some BSD systems do not have an atoll() routine, which broke compilation of the hobbitd_larrd module. Switched to use Hobbit's own atoll() for this platform. * Duration-times could be mis-reported on the "info" page, due to some bad math done when building this page. Improvements: * In bb-hosts you can now define a host called ".default." - the tags set for this host will be the default tag settings for the following hosts (until a new .default. host appears). * Merged the bb-infocolumn and bb-larrdcolumn functionality into the service-display CGI, and make bb-hostsvc into a Hobbit-only CGI called hobbitsvc.cgi. The bb-infocolumn and bb-larrdcolumn binaries have been removed. * --alertcolors, --okcolors and --repeat options for hobbitd, hobbitd_alert and bb-infocolumn were moved to settings in hobbitserver.cfg (ALERTCOLORS, OKCOLORS and ALERTREPEAT respectively). * A new generic RRD handler was added for name-colon-value reports. This can be used to handle RRD tracking of reports where the data is in lines of the form "Name: Value". * New "notrends" tag for bb-hosts entries drops the "trends" tag for a host (similar to the "noinfo" tag). * New "DOC:" tag for bb-hosts entries lets you set a documentation URL for each host, or as a default using the ".default." hostname. The --docurl option on bb-infocolumn (which no longer exists) has been dropped. * Included the "hobbitreports.sh" script to show how reports can be pre-generated by a cron-job. * New "bb-datepage.cgi" CGI makes it easy to select daily/weekly/monthly pre-generated reports. * The hobbitgraph CGI now allows you to show weekday- and month-names in your local language, instead of forcing it to english. Note that the fonts used may not include all non-ASCII characters. * CPU-reports from the bb-xsnmp.pl script should now be handled correctly by the RRD module. * CPU-reports for z/VM should now be handled correctly by the RRD module. * CPU-, disk- and memory-reports from the nwstats2bb script are now handled by the RRD module.

2 2

Blue status
by kevin＠ewormhole.com 10 Apr '05

10 Apr '05

Henrik, when I ran maint.pl on my old BB system I used to be able to go into "History", go back to the time when a system or test was put into maint mode, click on that event, and see who did it by reading their "Reason". Now when I do that, or a snapshot report to try to go back, and drill all the way down and click on the blue icon for that test, it shows as green and of course, no "reason". Is this by design and could it be made to show the actual status and reason for that time? Thanks KEvin

2 1

hobbit alert and STOP messages
by ctbeers＠syr.edu 10 Apr '05

10 Apr '05

I am having some difficulties with the STOP rules when an alert is triggered. I have the following rule in my hobbit-alert file. HOST=somehost.syr.edu MAIL ctbeers at syr.edu REPEAT=30m RECOVERED STOP MAIL pager_number at archwireless.net REPEAT=15m FORMAT=SMS RECOVERED STOP My understanding is that the alert module should alert me and the pager when the alert triggers. However, it appears that when the alert module encounters the STOP keyword it stop processing the entire rule (instead of stopping only if the recipient has already been alerted). Is this intended and if so how do I accomplish alerting two users for alert rules? Note: I was running beta6 when this problem occurred. I have updated to 4.0.1 with the eventlog patch, so maybe its fixed there. -- Christopher T. Beers Lead UNIX Architect - System Infrastructure Services (SIS) Syracuse University | 250 Machinery Hall | Syracuse, NY 13244 (315) 443-4103 Office | (315) 443-1621 Fax | p-ctbeers at syr.edu Pager

2 2