November 2005 - Xymon - Xymon mailman web

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

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

02 Nov '05

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

2 1

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

02 Nov '05

Should I be setting the loopback to listen on a specific port as currently its still giving errors that they are conflicting and so the status board does not show up. Thanks Craig -----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

1 0

[hobbit] delay creation of web pages
by frederic.mangeant＠steria.com 02 Nov '05

02 Nov '05

bb4 at richter-it.net a écrit : >Hi there, > >is it possible to delay the creation of the web pages in hobbit for a few minutes? > >The problem is that our customer is looking at the hobbit screen too and our suits are not very amused that he calls us instead of us calling him in case of an error. > >So management wants to delay the creation of the status pages in hobbit for a few minutes on the machine where the customer is looking at and on our internal machine everything should go the "old-fashioned" way. > Hi I'm running bbgen twice (once for admins, and once for customers), with different templates. Here's the task definition for customers's web pages : [customers-map] ENVFILE /BB/hobbit/server/etc/hobbitserver.cfg NEEDS hobbitd GROUP generators CMD bbgen $BBGENOPTS --report --subpagecolumns=2 --pages-last --pagetext-headings --recentgifs=60 --purplelog=/tmp/purple.log --noproppurple=NetBackup --ignorecolumns=info --template=customers $BBHOME/www/customers LOGFILE $BBSERVERLOGS/bb-display-customers.log INTERVAL 10m These web pages get updated every 10 minutes. You just have to point your customers to http://yourwebserver/hobbit/customers ;-) -- Frédéric Mangeant Steria EDC Sophia-Antipolis

1 0

[hobbit] Inexplicable purple on running services
by henrik＠hswn.dk 01 Nov '05

01 Nov '05

On Mon, Oct 31, 2005 at 05:32:44PM -0500, Rob Munsch wrote: > Consider the below. Approx. 25 minutes ago, across all monitored > systems, all net monitored services - ssh, ldaps and dns - went to > purple. They are still up, running, and just fine in every respect. > The status message is even the same as when it was showing green. But > now every ssh, ldaps and dns light is purple. Purple is an indication that some part of your monitoring system has stopped. All of the purple ones are network services ? Then it sounds as if your network tests have stopped running. Check the ~hobbit/server/logs/bb-network.log file for any errors. Regards, Henrik

2 7