- Xymon - Xymon mailman web

ALT text for colored icons
by gendalia＠iastate.edu 04 Nov '05

04 Nov '05

The ALT text for the various icons to notify us of problems show "sslcert:yellow:4.47 days" and "sslcert:yellow:acked:4.47 days". Would it be reasonable to change it to "sslcert:yellow:4.47 days:acked:2 hours" or something like that, so it's more obvious that yellow & acked aren't both the same time period? Or is that loading too much into an ALT tag? Tracy J. Di Marco White Information Technology Services Iowa State University

1 0

Server start ignores clientlaunch.cfg
by CHRIS.MORRIS＠RWEnpower.com 04 Nov '05

04 Nov '05

When running the server and client on a machine, the startup of the server also includes starting the client.(To reduce the hobbitlaunch tasks) However, the client in this scenario does not write its logs or pid file to the normal client directories and ignores the clientlaunch.cfg which details any external scripts to be run. You cannot stop the client cleanly as there is no pid file and therefore the ./runclient.sh stop says the client is not running. Chris **************************************************************************** The information contained in this email is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination or copying of the message or associated attachments is strictly prohibited. If you have received this email in error, please contact the sender by return email or call 01793 877777 and ask for the sender and then delete it immediately from your system.Please note that neither RWE npower nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any). *****************************************************************************

1 0

[hobbit] Too many line on disk graph
by Al.Jeffcoat＠orhs.org 04 Nov '05

04 Nov '05

Hmmm... During the time that the graphs were "conglomorated" for me also, I too had disk events... Actually, I had a red and a yellow event. The yellow event was real, and the timing of fixing it coincided with cleaning the tmp directory, and restarting hobbit. Strange thing though, now that I am looking around. During this yellow disk event, hobbit also appeared to ignore the disk rules in hobbit-clients.cfg for another client, which caused a red event for this client. When the yellow event was fixed, the red was fixed also, and apparently the graphs. Al -----Original Message----- From: Pat Vaughan [mailto:patrick_a_vaughan at hotmail.com] Sent: Thursday, October 20, 2005 9:02 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Too many line on disk graph Another possible clue, when I came in this morning there was a yellow state on the disk test and Hobbit was displaying one huge disk graph. I even did a reload on the page to make sure Hobbit had to regenerate it. After I fixed the error and the state went back to green, the graphs were back to normal. It might just be a coincidence, though. > A couple of us have had the same problem. Stopping the server, clearing > out the Hobbit server tmp subdirectory and restarting it was suggested. > > At first it didn't fix anything (and I did a forced reload on the disk web > page), but after a couple of minutes the graphs went back to being split > as normal. > > > >> OK the server seam to be no long spitting the disk graphs. This is >> true for all source of data, bb-clients local and remote >> clients,. This is with snapshot done on Oct. 16 night. >> >> -- >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> | _p_ Mike Nemeth >> | ___| |_____ email(w) michael.nemeth at lmco.com Work: 856 359-1425 >> |><___________) | Home >> Page:http://www.geocities.com/mjnemeth/ >> | Work Page:http://faraday.motown.lmco.com:3000/~nemethm/ >> | Work Page:http://ortsweb/~mnemeth/ >> |++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> To unsubscribe from the hobbit list, send an e-mail to >> hobbit-unsubscribe at hswn.dk >> >> >> > > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > > To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

3 7

No pages when going from yellow to red
by hobbit＠pvaughan.us 04 Nov '05

04 Nov '05

On my AIX box running the Hobbit client I found that disk alarms aren't generated if the condition goes from yellow to red. I have rules to send an Email if it's yellow, and I always get that. I also have rules to send a page if the state is red, and I get those if it jumps from green to red. But, if the state goes to yellow and then to red, the paging rule never fires. There isn't a entry added to the notification log either. I've mentioned this before on the list, but never got a definite response.

5 5

Want to use rrds "Aberrant Behavior Detection"
by urban.edlund＠staff.spray.se 04 Nov '05

04 Nov '05

Hi, I tried to to substitute a tcp.conn.rrd with a rrd that has RRA:HWPREDICT but I get this error "can't handle RRD file version 0003". Any way to make this work ? -- Regards Urban

1 0

segmentation fault on startup
by bob＠phreakout.net 04 Nov '05

04 Nov '05

I have just installed the hobbit server 4.1.2 on openbsd 3.8-sparc64. I used gmake to make everything and when I get everything installed and go to start the little devil, I get: /var/www/htdocs/hobbit $/var/www/htdocs/hobbit/server/bin/hobbit.sh start Segmentation fault Hobbit started It says it started, but it did not. /var/www/htdocs/hobbit $ps waux|grep hobbit hobbit 15376 0.0 0.1 696 560 p0 S 6:31PM 0:00.18 -ksh (ksh) hobbit 25169 0.0 0.2 504 1168 p0 S+ 6:39PM 0:00.05 grep hobbit hobbit 13080 0.0 0.1 464 288 p0 R+ 6:39PM 0:00.02 ps -waux Now, I really do not know what to do to track this down. Can anyone help? -Bob

2 1

[hobbit] few more questions
by Jason.Chambers＠geosoft.com 03 Nov '05

03 Nov '05

> Installing the Hobbit server does install and launch the client. > You should see the netstat- and vmstat-graphs if you look at the > "trends" column; there is no dedicated netstat- or vmstat-column > since these are purely for collecting data. If I don't have these columns in the trends graph, what will I need to do to get them up? Jason Chambers IT Helpdesk Support Geosoft Inc. 85 Richmond St. West - 8th Floor Toronto, Ontario, Canada M5H 2C9 Tel: 416-369-0111 x344 Fax: 416-369-9599 www.geosoft.com

2 1

few more questions
by Jason.Chambers＠geosoft.com 03 Nov '05

03 Nov '05

1) For some reason I cant get the hobbit client to report anything for msgs, its always clear. Is this a permission thing I need to set within linux? 2) Does the hobbit client run on the server? I don't see a netstat or vmstat there. 3) Other then deadcat, is there another repository for bb/hobbit scripts I can look at? Jason Chambers IT Helpdesk Support eosoft Inc. 85 Richmond St. West - 8th Floor Toronto, Ontario, Canada M5H 2C9 Tel: 416-369-0111 x344 Fax: 416-369-9599 www.geosoft.com

2 1

[hobbit] Using bbproxy to replicate the display
by Craig_Whilding＠mentor.com 03 Nov '05

03 Nov '05

Finally solved it - BBSERVERID was being used by another variable that was performing network tests and listening on the external port. Changing it to 127.0.01 lets me see the status board locally and have the bbproxy working properly. Thanks for the help. Craig -----Original Message----- From: Thomas [mailto:tlp-hobbit at holme-pedersen.dk] Sent: 02 November 2005 14:22 To: hobbit at hswn.dk Subject: Re: [hobbit] Using bbproxy to replicate the display In my setup I have --listen=127.0.0.1 on the hobbitd section and --listen=172.17.100.10 --bbdisplay=127.0.0.1,172.17.100.20 on the bbproxy section. My central server is on 172.17.100.20 Try to look at netstat -ln and see where you have the port 1984 listening. Whilding, Craig wrote: >The --listen option is set to 127.0.0.1 only for hobbitd in the >hobbitlaunch.cfg file. > >Even when hobbitd is DISABLED I still get the socket is in use. > >-----Original Message----- >From: Thomas [mailto:tlp-hobbit at holme-pedersen.dk] >Sent: 02 November 2005 13:55 >To: hobbit at hswn.dk >Subject: Re: [hobbit] Using bbproxy to replicate the display > >No but you should remove the $BBSERVERID from the --listen option on >hobbitd. > >Whilding, Craig wrote: > > > >>Just looking through again, should BBSERVERID in hobbitserver.cfg still >>be set as the real ip of the machine? >> >>-----Original Message----- >>From: Henrik Stoerner [mailto:henrik at hswn.dk] >>Sent: 01 November 2005 15:40 >>To: hobbit at hswn.dk >>Subject: Re: [hobbit] Using bbproxy to replicate the display >> >>On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote: >> >> >> >> >>>My company has a few sites that are currently using hobbit or big >>>brother for monitoring. What we wish to do is forward all of this >>>information to a central hobbit server so collate it for reports etc. >>>This server would also be testing the networks site gateways etc. >>> >>> >>> >>> >>After >> >> >> >> >>>reading the "delay creation of web pages" posts I realise bbproxy is >>> >>> >>> >>> >>the >> >> >> >> >>>replacement to bbrelay I require but I was wondering how I should set >>> >>> >>> >>> >>it >> >> >> >> >>>up. Looking at the manual and hobbitlaunch.cfg it says I should >>> >>> >>> >>> >>disable >> >> >> >> >>>hobbitd. Will each sites monitoring work as normal if I set >>> >>> >>> >>> >>--bbdisplay= >> >> >> >> >>>localhost and also the other, central machine? >>> >>> >>> >>> >>By default, hobbitd and bbproxy will conflict because they will both >>attempt to listen to port 1984 to handle incoming messages. >> >>But if you configure them properly, they can coexist. The setup you're >>after sounds like you want bbproxy to receive all of the incoming >>status messages and then forward them to a) a local hobbitd running >>on the same host, and b) the central hobbitd server. >> >>The easiest way to do that is to setup the local hobbitd's to listen on >>only the loopback interface (127.0.0.1), and bbproxy to listen on the >>public IP-address. Say your local server has IP 172.16.10.1 and the >>central Hobbit server is 10.0.100.200, then you should use the options >> >> --listen=127.0.0.1 >> >>for hobbitd, and >> >> --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200 >> >>for bbproxy. >> >> >>Regards, >>Henrik >> >> >>To unsubscribe from the hobbit list, send an e-mail to >>hobbit-unsubscribe at hswn.dk >> >> >> >>To unsubscribe from the hobbit list, send an e-mail to >>hobbit-unsubscribe at hswn.dk >> >> >> >> >> >> >> > >To unsubscribe from the hobbit list, send an e-mail to >hobbit-unsubscribe at hswn.dk > > > >To unsubscribe from the hobbit list, send an e-mail to >hobbit-unsubscribe at hswn.dk > > > > > To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

[hobbit] Using bbproxy to replicate the display
by Craig_Whilding＠mentor.com 02 Nov '05

02 Nov '05

The --listen option is set to 127.0.0.1 only for hobbitd in the hobbitlaunch.cfg file. Even when hobbitd is DISABLED I still get the socket is in use. -----Original Message----- From: Thomas [mailto:tlp-hobbit at holme-pedersen.dk] Sent: 02 November 2005 13:55 To: hobbit at hswn.dk Subject: Re: [hobbit] Using bbproxy to replicate the display No but you should remove the $BBSERVERID from the --listen option on hobbitd. Whilding, Craig wrote: >Just looking through again, should BBSERVERID in hobbitserver.cfg still >be set as the real ip of the machine? > >-----Original Message----- >From: Henrik Stoerner [mailto:henrik at hswn.dk] >Sent: 01 November 2005 15:40 >To: hobbit at hswn.dk >Subject: Re: [hobbit] Using bbproxy to replicate the display > >On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote: > > >>My company has a few sites that are currently using hobbit or big >>brother for monitoring. What we wish to do is forward all of this >>information to a central hobbit server so collate it for reports etc. >>This server would also be testing the networks site gateways etc. >> >> >After > > >>reading the "delay creation of web pages" posts I realise bbproxy is >> >> >the > > >>replacement to bbrelay I require but I was wondering how I should set >> >> >it > > >>up. Looking at the manual and hobbitlaunch.cfg it says I should >> >> >disable > > >>hobbitd. Will each sites monitoring work as normal if I set >> >> >--bbdisplay= > > >>localhost and also the other, central machine? >> >> > >By default, hobbitd and bbproxy will conflict because they will both >attempt to listen to port 1984 to handle incoming messages. > >But if you configure them properly, they can coexist. The setup you're >after sounds like you want bbproxy to receive all of the incoming >status messages and then forward them to a) a local hobbitd running >on the same host, and b) the central hobbitd server. > >The easiest way to do that is to setup the local hobbitd's to listen on >only the loopback interface (127.0.0.1), and bbproxy to listen on the >public IP-address. Say your local server has IP 172.16.10.1 and the >central Hobbit server is 10.0.100.200, then you should use the options > > --listen=127.0.0.1 > >for hobbitd, and > > --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200 > >for bbproxy. > > >Regards, >Henrik > > >To unsubscribe from the hobbit list, send an e-mail to >hobbit-unsubscribe at hswn.dk > > > >To unsubscribe from the hobbit list, send an e-mail to >hobbit-unsubscribe at hswn.dk > > > > > To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

2 1