- Xymon - Xymon mailman web

Latest 4.2-pre snapshot doesn't install CGI scripts
by frederic.mangeant＠steria.com 15 Feb '06

15 Feb '06

Hi Henrik installing the latest snapshot fails, as it seems that none of the cgi-bin/ and cgi-secure/ files get copied to the destination directory : chown hobbituser /var/log/hobbit /BB/hobbit/server /BB/hobbit/server/* /BB/hobbit/server/bin/* /BB/hobbit/server/etc/* /BB/hobbit/server/ext/* /BB/hobbit/server/web/* /BB/hobbit/server/www/gifs /BB/hobbit/server/www/gifs/* /BB/hobbit/server/www/menu /BB/hobbit/server/www/menu/* /BB/hobbit/server/www/help /BB/hobbit/server/www/notes /BB/hobbit/server/www/html /BB/hobbit/server/www/wml /BB/hobbit/data /BB/hobbit/data/* /BB/hobbit/cgi-bin /BB/hobbit/cgi-bin/* /BB/hobbit/cgi-secure /BB/hobbit/cgi-secure/* chown: cannot access `/BB/hobbit/cgi-bin/*': No such file or directory chown: cannot access `/BB/hobbit/cgi-secure/*': No such file or directory make[1]: *** [install-cfg] Error 1 make[1]: Leaving directory `/BB/src/snapshot/hobbitd' make: *** [install-hobbitd] Error 2 The Makefile I've generated with "./configure --server" is the same than with previous snapshots. -- Frédéric Mangeant Steria EDC Sophia-Antipolis

3 4

Backup server for HOBBIT
by Winn.Beutler＠mcdata.com 15 Feb '06

15 Feb '06

I have searched the HOBBIT archive but cannot find anything on setting up a hot standby HOBBIT server that receives input from the clients along with the primary server but does not send out alerts unless the primary server goes down. Any howto's on this? Thanks in advance for any help/hints. Winn 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)

6 6

[hobbit] Logfile monitoring - I'd like some comments
by v.everett＠afgonline.com.au 15 Feb '06

15 Feb '06

Hi all Henrik, I have given this a bit of thought, and think it's great. (I refer to your proposal here, not my capacity for thought.) Would it be possible to add custom strings and status? A perfect example would be this. (from /var/adm/messages) ---snip--- Feb 10 13:31:15 afgdev tldd[649]: [ID 138416 daemon.error] TLD(0) drive 2 (device 1) is being DOWNED, status: Unable to open drive ---snip--- Anywhere else, this would not be a major issue, but on my backup server where my tape library is attached, this is a major red alert. Regards Vernon -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Wednesday, 15 February 2006 5:40 AM To: hobbit at hswn.dk Subject: [hobbit] Logfile monitoring - I'd like some comments A few days ago, I mentioned that I would like to do logfile monitoring for the next Hobbit release. I've worked a bit on this and have a prototype solution for it, which you can test with the current snapshots. I'd like some comments on how it works to make sure I haven't overlooked something before committing myself. There are several objectives: - As far as is possible, logfile monitoring must be configured centrally, on the Hobbit server. Having to go to each server to (re)configure what logfiles to check and what to look for simply doesn't work. - The amount of data sent from each client to Hobbit should be small, but it must catch the "important" stuff. - You rarely know in advance what will be in the logs when you need them the most. So the monitor should give you as much of the log entries as possible, not just those lines that match some pre-defined strings or regex'es. - Some systems log messages on multiple lines. The system must be able to show all parts of a log entry. - Logfile entries must appear on the monitor for some time after they show up in the logs, but should also disappear after a while. In other words: The ideal solution would let you have the entire logfile available on the Hobbit server - but that obviously won't work. So the client should - after weeding out the really irrelevant stuff - send us as much of each logfile as possible. My proposed solution is this: - On the Hobbit server, there's a log-monitoring configuration file for the Hobbit clients. This defines which logfiles are monitored for a single client installation, or you can define it for a group of clients. (The idea is to define at least one group for each operating system, since the standard system logs are OS dependant). This configuration lists the log filename, the maximum amount of data to send from this logfile, a regex "noise" filter (i.e. lines that are stripped from the logfile), and *optionally* a regex identifying really interesting stuff in the logfile that should always be reported. - When a client connects to the Hobbit server and sends the normal client message, the Hobbit server will respond with the logfile configuration for this client. So the client has a copy of the central configuration file, but only the part that it needs for itself. The reason for sending this as a response to the client message is to avoid an extra round-trip from client to server; piggy-backing the config push on the client message means that it is almost without any performance cost on the server side. - When the client runs, it uses the local copy of the configuration file to determine what logs to look at. For each logfile, it maintains a "where-was-I-the-last-time" status, so it only looks at the entries made to the logfile during the past 30 minutes. First, the client strips off any "noise" messages. Then, if all of the entries fit into the maximum size that can be reported, it sends all of the log to the Hobbit server. If there is more than will fit, it first checks to see of the regex defining the really interesting stuff is present in the log - if it is, then it drops anything before the interesting text. If there is still more than will fit, it keeps the interesting text + a few lines after that (to allow for multi-line log-entries which some OS'es have), and then sends that together with as much of last part the log as will fit inside the max. message size. This part has been implemented in the Hobbit daemon (hobbitd), and in the clients via a new "logfetch" utility. This utility uses standard regular expressions - not the Perl-compatible ones, because that would require you to install the PCRE library on all of your clients. The standard regex routines are included in all (I think) system libraries used today. The last part is what happens when the log data arrives on the Hobbit server. Currently, there's a simple processing of this data to just dump it into an always-green "msgs" column. What should happen once I get it coded is: - Data from each logfile is matched against a set of strings (regex'es) defined in the hobbit-clients.cfg file. Each string determines the color (red, yellow, green) and sets the color of the msgs column accordingly. When the color has been decided, all of the normal alerting happens automatically. I do plan on making a more fine-grained alert mechanism (for the msgs, procs and disk statuses) so you can direct alerts to different groups depending on exactly which log-message triggered the alert, but that will not be part of this release. So - how does that sound ? Anything I've missed ? Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 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

Estimate for 4.2 release?
by jboone＠columbia.com 14 Feb '06

14 Feb '06

Is there an estimate for when the 4.2 release will be available? I'm currently running 4.0.4 in production and have been testing the 4.1.2p1 and the 4.2pre release. I'm looking to upgrade for the hobbit client and want to minimize the number of upgrades. - Jim

4 4

[hobbit] Logfile monitoring - I'd like some comments
by aoldaker＠wdtinc.com 14 Feb '06

14 Feb '06

While I'm sure there will be some extensive feedback on this issue for days to come, I would like to commend Henrick on the simple fact that we are finally looking at an opportunity to remove the third-party client side logfile scripts (most of us are using) from our Hobbit installations and get back toward centralized log monitoring. -AJO Andrew J Oldaker WDT Unix Systems Support

1 0

Alerts as .dat attachments
by kmckinnis＠macrovision.com 14 Feb '06

14 Feb '06

Perhaps someone can help me shed some light on this. I'm receiving some red alerts as .dat attachments. Is this normal behavior? red Mon Feb 13 20:33:11 2006: /Ping.tst Set-Cookie: JSESSI &red http://10.228.3.4/Ping.tst - /Ping.tst Set-Cookie: JSESSI HTTP/1.1 404 /Ping.tst Set-Cookie: JSESSIONID=100BAAD89BF9FB00920DA09504FEB4B1; Path=/ Content-Type: text/html Date: Tue, 14 Feb 2006 04:34:21 GMT Server: Apache-Coyote/1.1 Connection: close Seconds: 0.00 See (hobbit URL here) ------ Hobbit-alerts.cfg: $NSHOSTS=%(sc-isus-ns-1|sc-isus-ns-2|sc-isus-ns-3|sc-isus-ns-4|sc-isus-p w-1).subdomain.domain.com HOST=$NSHOSTS SERVICE=http MAIL isus-sms REPEAT=2h RECOVERED COLOR=red FORMAT=sms HOST=* MAIL isus-mail REPEAT=12h RECOVERED COLOR=red EXHOST=sc-isds-1.subdomain.domain.com UNMATCHED MAIL contact at domain.com COLOR=red REPEAT=12h RECOVERED ------- Is this a default behavior I didn't know about? It doesn't seem to be consistent. I've looked through the online page about configuring alerts. Perhaps I've missed something in my alerts.cfg. Thanks!

2 1

menu_items.js
by mlowery＠alliedtechgroup.com 14 Feb '06

14 Feb '06

Is it possible to have hobbit rewrite this on bootup? I have 2 hobbit prorams on 1 server and when the user on "hobbit 2" goes to the menu, they get redirected to "hobbit 1". I fixed it manually, but it would be nice for it to pick that up. Thanks, Michael

1 0

[hobbit] problem to see rrd graph
by tmyers＠autom.net 14 Feb '06

14 Feb '06

check the rrd logs and see you your sill looking for an old lib, I just moved to a new box with a new OS and I am having the same problem this morning. -----Original Message----- From: Marco Avvisano [mailto:marco.avvisano at regione.toscana.it] Sent: Monday, January 30, 2006 6:48 AM To: hobbit at hswn.dk Subject: [hobbit] problem to see rrd graph Hi all, i have upgrade rrd to 1.2.12 and hobbit to 4.2pre and now i don't see any graph. I try to add in hobbitserver.cfg LD_LIBRARY_PATH, and the bin directory for rrdtool in PATH but nothing. any suggestions? thanks Marco To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

4 9

Memory Test on OS X (Darwin)
by david＠stenhouseconsulting.com 14 Feb '06

14 Feb '06

Good day Hobbits, I installed the hobbit client on an OS X 10.4 server and found that memory was not being reported. I setup the bb-memory.sh script on the server and I get the following: Memory routine not defined for this operating system (Darwin). I thought this to be strange since the original bb-memory.sh supported BSD and OS X/Darwin was built on OpenBSD. Does anyone know of a fix or work around? David Gilmore Consultant Stenhouse Consulting, LLC. 4 Traverse St Providence, RI 02906 401.453.6900 401.454.7581 (fax)

2 4

[hobbit] Numbers lost in status report
by greg.hubbard＠eds.com 13 Feb '06

13 Feb '06

Found it! Using technique no. 1 -- I learned that my test returned different results when run by the Hobbit client than when I run it myself! Must be a life lesson in there somewhere... Thanks again, Henrik! GLH -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Monday, February 13, 2006 2:45 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Numbers lost in status report On Mon, Feb 13, 2006 at 01:54:23PM -0600, Hubbard, Greg L wrote: > Hobbit folk: > > Here is something interesting. I wrote a custom test today that sends > over data in pretty much the same format as used in the other custom > tests that I have written lately. Problem is that my numbers are > getting lost! I even added trailing text and it arrives, but the > numbers do not. > > According to my debug information, the numbers are being written in > the status message that goes out the door, but when posted by the > server on the status page they are gone. > > Any ideas on how to start to debug this? > > Solaris 8, Hobbit 4.1.2p1 First, double-check your custom test! If you add - at the top - a "BB=/bin/echo; export BB" then the command to send the status message off to Hobbit will just dump the status message to stdout - which goes into the logfile, normally. See what your status message looks like - and check if it's what you expect. Next check what hobbitd actually receives from your custom test: Run bb 127.0.0.1 "hobbitdlog HOSTNAME.COLUMNNAME" That gives you the raw status log which is received by hobbitd. If the numbers are there, you probably have some HTML tags in the status message which your browser chooses not to display. If they are not there, then you have an "interesting" situation. (As in "I have no idea how that can happen"). In that case, I'd like you to enable the --trace option for hobbitd: You'll need the IP address of the host that sends you this message, and then add "--trace=IP.OF.SENDING.HOST" to the hobbitd command in hobbitlaunch.cfg. With that, hobbitd will create a file in the ~hobbit/data/tmp/ directory logging all traffic from this host. Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0