November 2005 - Xymon - Xymon mailman web

problems (with solution) building latest snapshot on Solaris
by jonescr＠cisco.com 06 Nov '05

06 Nov '05

Just for fun I grabbed the latest snapshot and tried to compile it on my Solaris10 server at home. I ran into a couple of problems which I was able to fix. Long gory details below, quick summary at the bottom. I configured with all default options, except no to LDAP. Here's the results: [hobbit at ultra5 snapshot]$ make CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I`pwd`/include -I/usr/local/include" OSDEF="-DSunOS" RPATHOPT="" PCREINCDIR="-I/usr/local/include" SSLFLAGS="-DBBGEN_SSL" SSLINCDIR="-I/usr/local/ssl/include " SSLLIBS="-L/usr/lib -lssl -lcrypto" NETLIBS="-lresolv -lsocket -lnsl" BBTOPDIR="/home/hobbit" BBLOGDIR="/var/log/hobbit" BBHOSTNAME="ultra5" BBHOSTIP="192.168.0.103" BBHOSTOS="sunos" make -C lib all make[1]: Entering directory `/home/hobbit/snapshot/lib' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/hobbit/snapshot/lib' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I`pwd`/include -I/usr/local/include" RPATHOPT="" SSLFLAGS="-DBBGEN_SSL" SSLINCDIR="-I/usr/local/ssl/include " SSLLIBS="-L/usr/lib -lssl -lcrypto" NETLIBS="-lresolv -lsocket -lnsl" BBHOME="/home/hobbit/server" make -C common all make[1]: Entering directory `/home/hobbit/snapshot/common' gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I/home/hobbit/snapshot/include -I/usr/local/include -o bbhostgrep bbhostgrep.o ../lib/libbbgen.a Undefined first referenced symbol in file recv ../lib/libbbgen.a(sendmsg.o) getservbyname ../lib/libbbgen.a(sendmsg.o) gethostbyname ../lib/libbbgen.a(sendmsg.o) socket ../lib/libbbgen.a(sendmsg.o) getsockopt ../lib/libbbgen.a(sendmsg.o) connect ../lib/libbbgen.a(sendmsg.o) inet_aton ../lib/libbbgen.a(sendmsg.o) inet_ntoa ../lib/libbbgen.a(sendmsg.o) shutdown ../lib/libbbgen.a(sendmsg.o) ld: fatal: Symbol referencing errors. No output written to bbhostgrep collect2: ld returned 1 exit status make[1]: *** [bbhostgrep] Error 1 make[1]: Leaving directory `/home/hobbit/snapshot/common' make: *** [common-build] Error 2 These errors are typical of missing networking libraries (resolv,socket,nsl), so I checked the Makefile and added $(NETLIBS) to snapshot/common/Makefile bbhostgrep: $(HOSTGREPOBJS) ../lib/libbbgen.a $(CC) $(CFLAGS) -o $@ $(HOSTGREPOBJS) ../lib/libbbgen.a *$(NETLIBS)* I then did a "make clean" and ran make again. This time I get this error: make[1]: Leaving directory `/home/hobbit/snapshot/common' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I`pwd`/include -I/usr/local/include" BBHOME="/home/hobbit/client" BBHOSTIP="192.168.0.103" LOCALCLIENT="" make -C client all make[1]: Entering directory `/home/hobbit/snapshot/client' cat hobbitclient.cfg.DIST | sed -e's!@BBHOSTIP@!192.168.0.103!g' >hobbitclient.cfg make[1]: *** [hobbitclient.cfg] Error 2 make[1]: Leaving directory `/home/hobbit/snapshot/client' make: *** [client] Error 2 I checked to see if /home/hobbit/snapshot/client/hobbitclient.cfg was created, and it was, but zero bytes. So, I checked the hobbitclient.cfg.DIST to make sure it had data in it and it did, I then I decided to check the sed command being used: "sed -e's!@BBHOSTIP@!192.168.0.103!g'". The syntax of that looks correct but when I tried it on the command line, it didn't work! So then I grepped for sed in all of the Makefiles, and found many usages of sed, but all the others had one difference, *a space after the -e option*. I changed the sed commands in snapshot/client/Makefile to have a space after the "-e" option, did a make clean; make; and now it compiled smoothly. --- Summary --- So, to summarize, for Solaris compatibility in the latest snapshot, please add the netlibs to the snapshot/common/Makefile, and correct the spacing of the sed command options in snapshot/client/Makefile. -Charles

2 1

Msgs test with Hobbit client
by v.everett＠afgonline.com.au 05 Nov '05

05 Nov '05

Hi Henrik I have at last found the time to move to Hobbit clients. (Which means there may be some documentation in the future) However, I have encoutered a small problem, and although this may have been addressed in earlier discussions, but I have not been reading the list for a while. Our BB client ran an msgs test, checking on /var/adm/messages When we switch to Hobbit client, this status changes to white, not purple as I would have expected. What is the status of this test within Hobbit? Regards Vernon ----- No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 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.

2 1

[hobbit] Server start ignores clientlaunch.cfg
by aoldaker＠wdtinc.com 04 Nov '05

04 Nov '05

I have also experienced this issue as well. Both server versions v4.1.1 and v4.1.2 have exhibited this odd behavior. As a quick workaround for the external scripts, I've moved them to ~/etc/hobbitlaunch.cfg and had good results. However the missing logs/missing PID file seems to be a problem. Otherwise, many thanks to Henrick for an **excellent** product. -AJO Andrew J Oldaker Linux Support, WDT Inc -----Original Message----- From: Morris, Chris (Shared Services) [mailto:CHRIS.MORRIS at RWEnpower.com] Sent: Friday, November 04, 2005 06:30 To: 'hobbit' Subject: [hobbit] Server start ignores clientlaunch.cfg 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). ************************************************************************ ***** To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

Problem with 'worst' conn method reporting
by EES2Y＠hscmail.mcc.virginia.edu 04 Nov '05

04 Nov '05

Hi Henrik, We've had a problem with the 'worst' conn method for a while now, and I've never got around to reporting or looking into it. Basically what happens is that a host with multiple IP addresses and the 'worst' conn method wont report any status changes (it will always be green, even if one or all of its ips are unpingable). I think I've fixed this, it was a pretty simple bug; on line 1383 of bbtest-net.c, I changed 'countasdown = 0;' to 'countasdown = 1;'. I didn't really investigate the ramifications of what this change might have on the rest of the code, so let me know if I'm way off base. (I know it did fix the worst issue, though, because 3 of our multi-interface sites with unpingable ifcs immediately went red). Regards, -Eric Schwimmer Network Engineer UVA HSCS Network Engineering

2 1

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

04 Nov '05

Hi Henrik, I don't know if you got my email, but the file attachment was too large to get placed into the mailing list so I sent it to your personal address you have listed here. 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 -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Thursday, November 03, 2005 4:05 PM To: hobbit at hswn.dk Subject: Re: [hobbit] few more questions On Thu, Nov 03, 2005 at 03:59:42PM -0500, Jason Chambers wrote: > > 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? Look for the ~hobbit/client/tmp/msg.txt file - this is the data collected by the client and sent to the Hobbit server. It should contain a section beginning with "[netstat]" and another with "[vmstat]". Are they in that file ? And not empty sections ? If they are, send me a copy of that file. It might be that Hobbit just fails to recognize the format of data your server sends; what OS is this on ? Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

problems (with solution) building latest snapshot on Solaris
by jonescr＠cisco.com 04 Nov '05

04 Nov '05

Just for fun I grabbed the latest snapshot and tried to compile it on my Solaris10 server at home. I ran into a couple of problems which I was able to fix. Long gory details below, quick summary at the bottom. I configured with all default options, except no to LDAP. Here's the results: [hobbit at ultra5 snapshot]$ make CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I`pwd`/include -I/usr/local/include" OSDEF="-DSunOS" RPATHOPT="" PCREINCDIR="-I/usr/local/include" SSLFLAGS="-DBBGEN_SSL" SSLINCDIR="-I/usr/local/ssl/include " SSLLIBS="-L/usr/lib -lssl -lcrypto" NETLIBS="-lresolv -lsocket -lnsl" BBTOPDIR="/home/hobbit" BBLOGDIR="/var/log/hobbit" BBHOSTNAME="ultra5" BBHOSTIP="192.168.0.103" BBHOSTOS="sunos" make -C lib all make[1]: Entering directory `/home/hobbit/snapshot/lib' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/hobbit/snapshot/lib' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I`pwd`/include -I/usr/local/include" RPATHOPT="" SSLFLAGS="-DBBGEN_SSL" SSLINCDIR="-I/usr/local/ssl/include " SSLLIBS="-L/usr/lib -lssl -lcrypto" NETLIBS="-lresolv -lsocket -lnsl" BBHOME="/home/hobbit/server" make -C common all make[1]: Entering directory `/home/hobbit/snapshot/common' gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I/home/hobbit/snapshot/include -I/usr/local/include -o bbhostgrep bbhostgrep.o ../lib/libbbgen.a Undefined first referenced symbol in file recv ../lib/libbbgen.a(sendmsg.o) getservbyname ../lib/libbbgen.a(sendmsg.o) gethostbyname ../lib/libbbgen.a(sendmsg.o) socket ../lib/libbbgen.a(sendmsg.o) getsockopt ../lib/libbbgen.a(sendmsg.o) connect ../lib/libbbgen.a(sendmsg.o) inet_aton ../lib/libbbgen.a(sendmsg.o) inet_ntoa ../lib/libbbgen.a(sendmsg.o) shutdown ../lib/libbbgen.a(sendmsg.o) ld: fatal: Symbol referencing errors. No output written to bbhostgrep collect2: ld returned 1 exit status make[1]: *** [bbhostgrep] Error 1 make[1]: Leaving directory `/home/hobbit/snapshot/common' make: *** [common-build] Error 2 These errors are typical of missing networking libraries (resolv,socket,nsl), so I checked the Makefile and added $(NETLIBS) to snapshot/common/Makefile bbhostgrep: $(HOSTGREPOBJS) ../lib/libbbgen.a $(CC) $(CFLAGS) -o $@ $(HOSTGREPOBJS) ../lib/libbbgen.a *$(NETLIBS)* I then did a "make clean" and ran make again. This time I get this error: make[1]: Leaving directory `/home/hobbit/snapshot/common' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -DSunOS -I. -I`pwd`/include -I/usr/local/include" BBHOME="/home/hobbit/client" BBHOSTIP="192.168.0.103" LOCALCLIENT="" make -C client all make[1]: Entering directory `/home/hobbit/snapshot/client' cat hobbitclient.cfg.DIST | sed -e's!@BBHOSTIP@!192.168.0.103!g' >hobbitclient.cfg make[1]: *** [hobbitclient.cfg] Error 2 make[1]: Leaving directory `/home/hobbit/snapshot/client' make: *** [client] Error 2 I checked to see if /home/hobbit/snapshot/client/hobbitclient.cfg was created, and it was, but zero bytes. So, I checked the hobbitclient.cfg.DIST to make sure it had data in it and it did, I then I decided to check the sed command being used: "sed -e's!@BBHOSTIP@!192.168.0.103!g'". The syntax of that looks correct but when I tried it on the command line, it didn't work! So then I grepped for sed in all of the Makefiles, and found many usages of sed, but all the others had one difference, *a space after the -e option*. I changed the sed commands in snapshot/client/Makefile to have a space after the "-e" option, did a make clean; make; and now it compiled smoothly. --- Summary --- So, to summarize, for Solaris compatibility in the latest snapshot, please add the netlibs to the snapshot/common/Makefile, and correct the spacing of the sed command options in snapshot/client/Makefile. -Charles

1 0

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 johng＠ixtelecom.com 04 Nov '05

04 Nov '05

Was there an update on this? When I have a system with red or yellow events, the disk graph combines all the filesystems into one graph instead of multiple graphs. When I get a green disk event it goes back to multiple graphs. I have a seen this on my Debian and Solaris 4.1.2 installs. John Jeffcoat, Al wrote: > 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 > > > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > >

2 6

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