July 2006 - Xymon - Xymon mailman web

[hobbit] Question about logfetch/ log message checking
by massimo.morsiani＠gilbarco.com 17 Jul '06

17 Jul '06

Hi Francesco, another approach you can use is to query your network devices using SNMP traps. You can integrate in Hobbit the external tool RouterMon (http://www.routermon.net/) It's free and easy to setup. This is the tool we use to monitor all our Cisco devices (switch, router, PIX). Or you can explore RouterMon evolution: DevMon that you can find here http://devmon.sourceforge.net/. But it's still a beta. Regards. Massimo Morsiani Information Technology Dep. ------ Gilbarco S.p.a. via de' Cattani, 220/G 50145 Firenze tel: +39-055-30941 fax: +39-055-318603 email: massimo.morsiani at gilbarco.com web: http://www.gilbarco.it -----Original Message----- From: Francesco Duranti [mailto:fduranti at q8.it] Sent: sabato 15 luglio 2006 18.21 To: hobbit at hswn.dk Subject: [hobbit] Question about logfetch/ log message checking I'm finishing to centralize the logging of all of our network switch and netapp filers on one server (the machine that also run Hobbit Server) and I want to use logfetch and Hobbit log monitoring functionality to check those log files and create alerts. Is possible in some way (or in a future version) to start logfetch and report his data as another client without running the entire hobbit client? The ideal setup would be of logfetch running on the hobbit server that check messages files in various directory and report for each file as a different client ... Someone already used the log monitoring feature in a similar way? Thanks Francesco Duranti This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

1 0

hobbit-mailack Segmentation fault
by peterjakobs＠myrealbox.com 17 Jul '06

17 Jul '06

Hi, Running on a debian sarge, I tried the beta and the RC, but when I try to use the hobbit-mailack I get an segmentation fault. Any ideas?? Peter Jakobs hobbit at gefil016:~$ /home/hobbit/server/bin/hobbit-mailack --env=/home/hobbit/server/etc/hobbitserver.cfg --debug Re: Hobbit [601931] toscdc01:ntp CRITICAL (RED) 2006-07-17 08:28:25 Subject-line not found hobbit at gefil016:~$ /home/hobbit/server/bin/hobbit-mailack --env=/home/hobbit/server/etc/hobbitserver.cfg --debug Subject: Re: Hobbit [601931] toscdc01:ntp CRITICAL (RED) Segmentation fault hobbit at gefil016:~$ /home/hobbit/server/bin/hobbit-mailack --env=/home/hobbit/server/etc/hobbitserver.cfg --debug Subject: Re: Hobbit [601931] toscdc01:ntp CRITICAL (RED) what is going on Segmentation fault 2006-07-17 08:25:46 1G2MY6-0000GB-KO ** | /home/hobbit/server/bin/hobbit-mailack --env=/home/hobbit/server/etc/hobbitserver.cfg <hobbit at gefil015.it.mobile.marconi.com> R=userforward T=address_pipe: Child process of address_pipe transport (running command "/home/hobbit/server/bin/hobbit-mailack --env=/home/hobbit/server/etc/hobbitserver.cfg") was terminated by signal 11 (Segmentation fault) 2006-07-17 08:25:46 1G2MY6-0000GH-PF <= <> R=1G2MY6-0000GB-KO U=Debian-exim P=local S=2169

2 1

apache test cpuload measurements >100%
by tomg＠mcclatchyinteractive.com 17 Jul '06

17 Jul '06

This morning I was reviewing some of my apache performance trend charts and noticed that I've had several occasions where the Apache CPULoad measurement recorded in Hobbit is over 100%. Has anyone else seen this? I'm using the tag apache=http://webserver:port/server-status?auto to get the data, and the apache2 graph def to display it. Tom

2 1

Proxy
by brodie＠mcw.edu 15 Jul '06

15 Jul '06

Hi- can someone briefly explain how the bbproxy stuff works? We have a cluster whose "head node" is accessible, but the cluster nodes are hidden behind that server. If someone can explain how something like this is set up, that'd be super.. ============================================================= (network) [hobbit server] [most of my nodes] [head node] || || [cluster nodes] --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590

3 2

bbproxy with multiple targets in beta package patches
by bgmilne＠staff.telkomsa.net 15 Jul '06

15 Jul '06

I was running a Hobbit server on the beta package with the allinone patch July 04 2006. However, we now want the hosts being monitored by this ("old") Hobbit server accessible from our other ("new") Hobbit server (running 4.1.2p1). We can tolerate differences in log file/port/proc features for a while until we upgrade the "new" server. So, as when migrating from BB to Hobbit, I set hobbitd to listed on port 1985 on the "old" server, set up bbproxy to forward to localhost:1985 and the "new" Hobbit server, and transferred the relevant data. However, now the "old" server is not getting data from clients, but the "new" one is, eg cpu, disk, files, memory, msgs, ports, procs are purple on the "old" server but green on the "new" sever (and collecting in the RRDs). The bbproxy section on the "old" server has: [bbproxy] #DISABLED ENVFILE /usr/lib/hobbit/server/etc/hobbitserver.cfg CMD $BBHOME/bin/bbproxy --hobbitd --bbdisplay=127.0.0.1:1985,10.10.9.32:1984 --report=$MACHINE.bbproxy --pidfile=$BBSERVERLOGS/bbproxy.pid LOGFILE $BBSERVERLOGS/bbproxy.log Any ideas, or is this a potential, or known, bug in 4.2 ? (I'm building the rc as I type ... but would appreciate any ideas). Regards, Buchan -- Buchan Milne ISP Systems Specialist B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)

3 3

[hobbit] Proxy
by brodie＠mcw.edu 14 Jul '06

14 Jul '06

Aha! That's more of what I was looking for. I'll be trying this out early next week. Thanks for the info! --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, July 14, 2006 4:24 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Proxy bbproxy is written so it can run as a stand-alone application. So unless you want to run network tests against the cluster nodes (your next question), then you can just copy the bbproxy executable over to the head node and run it by itself. However, since you probably also want to do a ping test of the cluster nodes, it would make the most sense to do a Hobbit server installation on the head node. The you would disable everything in hobbitlaunch.cfg, except the bbproxy and the network test tasks. Regards, Henrik On Fri, Jul 14, 2006 at 03:47:03PM -0500, Brodie, Kent wrote: > Followup: > > What is the typical or preferred way of "running bbproxy" ? Do I > simply fire up the bbproxy executable, feeding it the few options it > needs, or do I set up a "hobbit server" on that node with > specially-configured files found in ../server/etc? > > > --------------------------------------------------------- > Kent C. Brodie - brodie at phys.mcw.edu > Department of Physiology > Medical College of Wisconsin > (414) 456-8590 > -----Original Message----- > From: Henrik Stoerner [mailto:henrik at hswn.dk] > Sent: Friday, July 14, 2006 3:34 PM > To: hobbit at hswn.dk > Subject: Re: [hobbit] Proxy > > On Fri, Jul 14, 2006 at 02:18:58PM -0500, Brodie, Kent wrote: > > Hi- can someone briefly explain how the bbproxy stuff works? We > > have a cluster whose "head node" is accessible, but the cluster nodes > > are hidden behind that server. > > > > If someone can explain how something like this is set up, that'd be > > super.. > > > > ============================================================= > (network) > > [hobbit server] [most of my nodes] [head node] > > || > > || > > [cluster nodes] > > Since your cluster nodes can talk to the head node, and the head node > can talk to the hobbit server, the most simple solution would be to run > bbproxy on the head node of the cluster. > > Your cluster nodes would then use the head node's bbproxy as their > BBDISPLAY server. bbproxy on the head node would be configured to > forward messages to the real hobbit server. To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

[hobbit] Proxy
by brodie＠mcw.edu 14 Jul '06

14 Jul '06

Followup: What is the typical or preferred way of "running bbproxy" ? Do I simply fire up the bbproxy executable, feeding it the few options it needs, or do I set up a "hobbit server" on that node with specially-configured files found in ../server/etc? --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, July 14, 2006 3:34 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Proxy On Fri, Jul 14, 2006 at 02:18:58PM -0500, Brodie, Kent wrote: > Hi- can someone briefly explain how the bbproxy stuff works? We > have a cluster whose "head node" is accessible, but the cluster nodes > are hidden behind that server. > > If someone can explain how something like this is set up, that'd be > super.. > > ============================================================= (network) > [hobbit server] [most of my nodes] [head node] > || > || > [cluster nodes] Since your cluster nodes can talk to the head node, and the head node can talk to the hobbit server, the most simple solution would be to run bbproxy on the head node of the cluster. Your cluster nodes would then use the head node's bbproxy as their BBDISPLAY server. bbproxy on the head node would be configured to forward messages to the real hobbit server. Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

2 1

[hobbit] Proxy
by brodie＠mcw.edu 14 Jul '06

14 Jul '06

Also, what IP address would I use on the hobbit server for those hosts being monitored? (that is, how is the "conn" test configured?) -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, July 14, 2006 3:34 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Proxy On Fri, Jul 14, 2006 at 02:18:58PM -0500, Brodie, Kent wrote: > Hi- can someone briefly explain how the bbproxy stuff works? We > have a cluster whose "head node" is accessible, but the cluster nodes > are hidden behind that server. > > If someone can explain how something like this is set up, that'd be > super.. > > ============================================================= (network) > [hobbit server] [most of my nodes] [head node] > || > || > [cluster nodes] Since your cluster nodes can talk to the head node, and the head node can talk to the hobbit server, the most simple solution would be to run bbproxy on the head node of the cluster. Your cluster nodes would then use the head node's bbproxy as their BBDISPLAY server. bbproxy on the head node would be configured to forward messages to the real hobbit server. Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

Bug Suspect - Hobbit 4.2-beta-20060605
by M.N.Harron＠herts.ac.uk 14 Jul '06

14 Jul '06

Hi, I'm not sure if this message is going to a list or an individual. Please accept my apology if this problem has been reported previously. The script $HOME/client/runclient.sh is created without a space character after the "sed -e" statements. This causes the interpretation of options "--hostname", "--class", etc to fail. So, for example, the line: MACHINEDOTS="`echo $1 | sed -e's/--hostname=//'`" should read: MACHINEDOTS="`echo $1 | sed -e 's/--hostname=//'`" ^ I have confirmed this problem on Solaris 9, Solaris 10, Red Hat 9 and Fedora Core 5 so I guess that it is not limited to any particular platform. Best regards, Mike ====================================================================== | Mike Harron | Network Development and | Security Manager | E-mail: M.N.Harron at herts.ac.uk | Learning Resources Centre | Telephone (external): 01707 286 447 University of Hertfordshire | Telephone (internal): 3447 College Lane | Hatfield | Telephone (mobile): 07984 605 275 AL10 9AB | ======================================================================

2 1

[hobbit] A funny thing happened on the way to the RC...............
by brodie＠mcw.edu 14 Jul '06

14 Jul '06

Henrik- no trouble at all. That's why it's a release CANDIDATE-- and why we're willing to put up with issues like this for the sake of making a REALLY great product. There's no way you would find all these little issues without people like us willing to play around and put it through its paces. And yeah, it got my attention. And my boss's. And my sysadmin. And the pager company who stopped accepting emails after the first 20 or so. That's what we do. :-) --------------------------------------------------------- Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590 -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Friday, July 14, 2006 12:37 AM To: hobbit at hswn.dk Subject: Re: [hobbit] A funny thing happened on the way to the RC............... On Thu, Jul 13, 2006 at 04:48:08PM -0500, Brodie, Kent wrote: > Fired up BB. Then, everyone's pager went NUTS. 100 pages, times 4 > pagers. WHOOOOPS. The entire world had uh..... "lost > connectivity." > > What had really happened of course is, that the hobbit userid couldn't > run fping, since I had forgotten to suid the executable. And yes, I > did eventually find it in a log file, but... But, this had the > very nasty side effect of turning each and every connectivity icon RED. > And then the alerts kicked in..... And four Duracell batteries died. Well, at least Hobbit managed to get your attention that there was some configuration problem :-) Seriously - you're right, it shouldn't do that. Such a problem should end up with a red status in the "bbtest" column and nothing else. I'll make sure it does that. Sorry about the trouble! Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0