- Xymon - Xymon mailman web

Forwarding status messages
by Russell.Cook＠capita.co.uk 04 Apr '12

04 Apr '12

Hi, I am building a new XyMon server to replace an old Hobbit installation that is monitoring a few hundred devices. I would like to somehow like to forward the status messages to the new server while I am testing ... anyone have any ideas ... I thought of trying to use bbproxy, but I suspect hobbitd needs to be stopped ... which defeats the object I suppose. Regards Russell Cook Senior NMS Engineer IT Services Capita York House 49-51 Victoria Road Farnborough, Hampshire GU14 7PA Tel: 01252 500 718 Mobile: 07968 216175 Email: russell.cook at capita.co.uk <mailto:russell.cook at capita.co.uk> Web: www.capita-its.co.uk P Please consider the environment - only print this email if absolutely necessary This email and any attachment to it are confidential. Unless you are the intended recipient, you may not use, copy or disclose either the message or any information contained in the message. If you are not the intended recipient, you should delete this email and notify the sender immediately. Any views or opinions expressed in this email are those of the sender only, unless otherwise stated. All copyright in any Capita material in this email is reserved. All emails, incoming and outgoing, may be recorded by Capita and monitored for legitimate business purposes. Capita exclude all liability for any loss or damage arising or resulting from the receipt, use or transmission of this email to the fullest extent permitted by law.

4 3

Bug - xymonnet not correctly checking NOPAGENET
by john.horne＠plymouth.ac.uk 04 Apr '12

04 Apr '12

Hello, In Xymon 4.3.7 the xymonnet.c file contains the following code: ==================================== /* If a NOPAGENET service, downgrade RED to YELLOW */ if (color == COL_RED) { char *nopagename; /* Check if this service is a NOPAGENET service. */ nopagename = (char *) malloc(strlen(svcname)+3); sprintf(nopagename, ",%s,", svcname); if (strstr(nonetpage, svcname) != NULL) color = COL_YELLOW; xfree(nopagename); } ==================================== As far as I can see this is incorrect because it sets up 'nopagename' but then compares 'svcname' against 'nonetpage'. So all the 'nopagename' code is completely redundant. I suspect what should happen is: if (strstr(nonetpage, nopagename) != NULL) color = COL_YELLOW; This piece of code occurs in two other places - httpresult.c and ldaptest.c. Regards, John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001

1 0

Forwarding status messages - [resolved]
by Russell.Cook＠capita.co.uk 04 Apr '12

04 Apr '12

Hi Thomas, I checked the /etc/hosts localhost entry and it is there ... but I am happy to leave it using the servers IP address. Thanks again for your help Russell -----Original Message----- From: Thomas Eckert [mailto:thomas.eckert at IT-Eckert.de] Sent: 04 April 2012 08:58 To: Cook, Russell (IT Services - Operations) Subject: Re: [Xymon] Forwarding status messages Hi Russell, great to hear that it works fine. Your "localhost not working"-problem might be due to missing entries in `/etc/hosts` it should contain a line like 127.0.0.1 localhost You could reply to the list so others can find this "resolved" (this email reached my personally). All the best Thomas On 04/04/2012 09:50 AM, Cook, Russell (IT Services - Operations) wrote: > Thanks Thomas, > > I tried the setup as you suggested, but found the localhost:1985 didn't > work. I changed it to use the ip address instead and that worked. > > Thanks for your help > > Cheers > Russell > > -----Original Message----- > From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf > Of Thomas Eckert > Sent: 03 April 2012 21:35 > To: xymon at xymon.com > Subject: Re: [Xymon] Forwarding status messages > > The bbproxy-idea sounds good. > > The following _should_ work: > - running bbproxy on the old installation listening on port 1984 to > accept all incoming messages > - re-configure the hobbitd on the old installation to listen on another > port (say 1985) > - forward messages from bbproxy to localhost:1985 and newserver:1984 > > I've done something similar with ssh tunnels and bbproxy. A test-setup > would before going live with this may be helpful. > > Another option may be to add an additional IP to your server and binding > > bbproxy and hobbitd to them? > > All the best > Thomas > > On 04/03/2012 06:20 PM, Cook, Russell (IT Services - Operations) wrote: >> Hi, >> >> I am building a new XyMon server to replace an old Hobbit installation >> that is monitoring a few hundred devices. I would like to somehow like >> to forward the status messages to the new server while I am testing > ... >> anyone have any ideas ... I thought of trying to use bbproxy, but I >> suspect hobbitd needs to be stopped ... which defeats the object I > suppose. >> >> Regards >> >> *Russell Cook >> Senior NMS Engineer >> IT Services >> Capita >> >> *York House >> 49-51 Victoria Road >> Farnborough, Hampshire >> GU14 7PA >> Tel: 01252 500 718 >> Mobile: 07968 216175 >> Email: *russell.cook at capita.co.uk<mailto:russell.cook at capita.co.uk> >> *Web: *www.capita-its.co.uk* >> >> P*Please consider the environment - only print this email if > absolutely >> necessary* >> >> >> >> This email and any attachment to it are confidential. Unless you are > the >> intended recipient, you may not use, copy or disclose either the > message >> or any information contained in the message. If you are not the > intended >> recipient, you should delete this email and notify the sender > immediately. >> >> Any views or opinions expressed in this email are those of the sender >> only, unless otherwise stated. All copyright in any Capita material in >> this email is reserved. >> >> All emails, incoming and outgoing, may be recorded by Capita and >> monitored for legitimate business purposes. >> >> Capita exclude all liability for any loss or damage arising or > resulting >> from the receipt, use or transmission of this email to the fullest >> extent permitted by law. >> >> This message has been scanned for malware by Websense. > www.websense.com >> <http://www.websense.com/> >> >> >> >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon > -- -- -------------------------------------------------------------------- | IT-Beratung Eckert | Hartkirchweg 54 | fon: +49 (0)761/ 594 9898 | Thomas Eckert | 79111 Freiburg i.Br. | fax: +49 (0)761/ 594 9899 | | Germany | http://www.it-eckert.de/

1 0

Change Graph Definitions
by j.mcdo73＠gmail.com 03 Apr '12

03 Apr '12

Apologies about the error in the subject of the previous mail. I think I found what I need in this Zenoss post: http://community.zenoss.org/docs/DOC-4426. I post this in case someone else searches for something similar here. Rgds, > Message: 1 > Date: Mon, 2 Apr 2012 12:03:36 +0100 > From: James McDonald <j.mcdo73 at gmail.com> > To: xymon at xymon.com > Subject: Re: [Xymon] Xymon Digest, Vol 14, Issue 27 > Message-ID: > <CAE4zdC3nMDTz4_=d8qfhzZ_wDNp=gP2fGOgDrmQGmrz4nwboLA at mail.gmail.com > > > Content-Type: text/plain; charset="iso-8859-1" > > Hi again, > > > I found a Xymon config file which seems to hold the default setup for the > RRD graphs created within Xymon (rrddefinitions.cfg). The contents look > like this: > > > # 576 datapoints w/ 5 minute interval = 48 hours @ 5 min avg. > > RRA:AVERAGE:0.5:1:576 > > # 576 datapoints w/ 6*5 minute averaged = 12 days @ 30 min avg. > > RRA:AVERAGE:0.5:6:576 > > # 576 datapoints w/ 24*5 minute averaged = 48 days @ 2 hour avg. > > RRA:AVERAGE:0.5:24:576 > > # 576 datapoints w/ 288*5 minute averaged = 576 days @ 1 day avg. > > RRA:AVERAGE:0.5:288:576 > > > Would I be correct saying that if I *add / append* the following lines, > this would include the LAST value to all new graphs created still keepign > the AVERAGE? > > # 576 datapoints w/ 5 minute interval = 48 hours @ 5 min avg. > > RRA:LAST:0.5:1:576 > > # 576 datapoints w/ 6*5 minute averaged = 12 days @ 30 min avg. > > RRA:LAST:0.5:6:576 > > # 576 datapoints w/ 24*5 minute averaged = 48 days @ 2 hour avg. > > RRA: LAST:0.5:24:576 > > # 576 datapoints w/ 288*5 minute averaged = 576 days @ 1 day avg. > > RRA: LAST:0.5:288:576 > > > Thanks, > James > >

1 0

Compiling xymon-4.3.7 on Solaris 9
by sean.greasley＠guardian.co.uk 03 Apr '12

03 Apr '12

Hi There, I seem to be getting an error compiling 4.3.7 on Solaris 9... I noticed there was a similar error with 4.3.5 when the NETLIBS weren't included in the Makefile... I noticed for 4.3.7, however, that this isn't the case... Is there something im missing? Log below.... root at esddev-dc1:/tmp/xymon-4.3.7> gmake MAKE="gmake" CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include" LDFLAGS="" `pwd`/build/genconfig.sh Checking for socklen_t Checking for snprintf Checking for vsnprintf Checking for rpc/rpcent.h Checking for sys/select.h Checking for u_int32_t typedef Checking for PATH_MAX definition Checking for SHUT_RD/WR/RDWR definitions Checking for strtoll() config.h created CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include" LDFLAGS="" OSDEF="-DSunOS" RPATHOPT="" PCREINCDIR="-I/opt/csw/include" SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="-lresolv -lsocket -lnsl" LIBRTDEF="" XYMONTOPDIR="/home/xymon" XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="10.132.80.41" XYMONHOSTOS="" LOCALCLIENT="yes" gmake -C lib client gmake[1]: Entering directory `/tmp/xymon-4.3.7/lib' gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -o test-endianness test-endianness.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o osdefs.o osdefs.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o cgiurls.o cgiurls.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -DCLIENTONLY -c -o color-client.o color.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o crondate.o crondate.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o digest.o digest.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o encoding.o encoding.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -DXYMONTOPDIR=\"/home/xymon\" -DXYMONLOGDIR=\"\" -DXYMONHOSTNAME=\"\" -DXYMONHOSTIP=\"10.132.80.41\" -DXYMONHOSTOS=\"\" -DBUILD_HOME=\"/home/xymon/client\" -c -o environ-client.o environ.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o errormsg.o errormsg.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o holidays.o holidays.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o ipaccess.o ipaccess.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o loadhosts.o loadhosts.c In file included from loadhosts.c:332: loadhosts_file.c: In function `load_hostnames': loadhosts_file.c:176: warning: subscript has type `char' loadhosts_file.c:131: warning: 'insavchar' might be used uninitialized in this function gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o md5.o md5.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o memory.o memory.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o misc.o misc.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o msort.o msort.c msort.c: In function `msort': msort.c:119: warning: passing arg 4 of `qsort' from incompatible pointer type gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include `./test-endianness` -c -o rmd160c.o rmd160c.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o sendmsg.o sendmsg.c sendmsg.c: In function `sendtoxymond': sendmsg.c:138: warning: 'sockfd' might be used uninitialized in this function gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include `./test-endianness` -c -o sha1.o sha1.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o sha2.o sha2.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o sig.o sig.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o stackio.o stackio.c stackio.c: In function `stackfgets': stackio.c:424: warning: 'eolchar' might be used uninitialized in this function stackio.c:440: warning: 'eolchar' might be used uninitialized in this function gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o strfunc.o strfunc.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o suid.o suid.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -DCLIENTONLY -c -o timefunc-client.o timefunc.c timefunc.c: In function `timespec_text': timefunc.c:126: warning: 'days' might be used uninitialized in this function timefunc.c:126: warning: 'starttime' might be used uninitialized in this function timefunc.c:126: warning: 'endtime' might be used uninitialized in this function timefunc.c:126: warning: 'columns' might be used uninitialized in this function gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -c -o tree.o tree.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -I. -I../include -I/opt/csw/include -c -o matching.o matching.c ar cr xymonclient.a osdefs.o cgiurls.o color-client.o crondate.o digest.o encoding.o environ-client.o errormsg.o holidays.o ipaccess.o loadhosts.o md5.o memory.o misc.o msort.o rmd160c.o sendmsg.o sha1.o sha2.o sig.o stackio.o strfunc.o suid.o timefunc-client.o tree.o matching.o ranlib xymonclient.a || echo "" gmake[1]: Leaving directory `/tmp/xymon-4.3.7/lib' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include" LDFLAGS="" RPATHOPT="" SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="-lresolv -lsocket -lnsl" LIBRTDEF="" XYMONHOME="/home/xymon/client" gmake -C common client gmake[1]: Entering directory `/tmp/xymon-4.3.7/common' gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymon.o xymon.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -o ../client/xymon xymon.o ../lib/xymonclient.a -lresolv -lsocket -lnsl gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymonlaunch.o xymonlaunch.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -o ../client/xymonlaunch xymonlaunch.o ../lib/xymonclient.a -lresolv -lsocket -lnsl gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymoncmd.o xymoncmd.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -o ../client/xymoncmd xymoncmd.o ../lib/xymonclient.a -lresolv -lsocket -lnsl gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymongrep.o xymongrep.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -o ../client/xymongrep xymongrep.o ../lib/xymonclient.a -lresolv -lsocket -lnsl gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymoncfg.o xymoncfg.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -o ../client/xymoncfg xymoncfg.o ../lib/xymonclient.a -lresolv -lsocket -lnsl gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymondigest.o xymondigest.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -o ../client/xymondigest xymondigest.o ../lib/xymonclient.a -lresolv -lsocket -lnsl gmake[1]: Leaving directory `/tmp/xymon-4.3.7/common' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include" LDFLAGS="" RPATHOPT="" SSLLIBS="" NETLIBS="-lresolv -lsocket -lnsl" LIBRTDEF="" XYMONHOME="/home/xymon/client" gmake -C build all gmake[1]: Entering directory `/tmp/xymon-4.3.7/build' gcc -o merge-lines -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include merge-lines.c gcc -o merge-sects -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include merge-sects.c gcc -o setup-newfiles -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include setup-newfiles.c ../lib/xymonclient.a -lresolv -lsocket -lnsl gcc -o renamevars -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include renamevars.c gcc -o renametasks -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include renametasks.c gmake[1]: Leaving directory `/tmp/xymon-4.3.7/build' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include" LDFLAGS="" RPATHOPT="" RRDDEF="" RRDINCDIR="" PCREINCDIR="-I/opt/csw/include" NETLIBS="-lresolv -lsocket -lnsl" RRDLIBS="" PCRELIBS="-L/opt/csw/lib -lpcre" XYMONTOPDIR="/home/xymon" XYMONHOME="/home/xymon/client" XYMONVAR="" XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="10.132.80.41" XYMONHOSTOS="" XYMONUSER="xymon" CGIDIR="" SECURECGIDIR="" XYMONHOSTURL="" XYMONCGIURL="" SECUREXYMONCGIURL="" MAILPROGRAM=""mailx"" RUNTIMEDEFS="" INSTALLWWWDIR="/home/xymon/client/www" INSTALLETCDIR="/home/xymon/client/etc" gmake -C xymond client gmake[1]: Entering directory `/tmp/xymon-4.3.7/xymond' gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymond_client.o xymond_client.c xymond_client.c: In function `nextsection': xymond_client.c:216: warning: dereferencing type-punned pointer will break strict-aliasing rules In file included from xymond_client.c:1765: client/mqcollect.c: In function `handle_mqcollect_client': client/mqcollect.c:186: warning: subscript has type `char' gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymond_worker.o xymond_worker.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o xymond_buffer.o xymond_buffer.c gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DSunOS -I. -I/tmp/xymon-4.3.7/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/opt/csw/include -c -o client_config.o client_config.c gcc -o ../client/xymond_client xymond_client.o xymond_worker.o xymond_buffer.o client_config.o ../lib/xymonclient.a -L/opt/csw/lib -lpcre -lresolv -lsocket -lnsl Undefined first referenced symbol in file locator_serverdown xymond_worker.o locator_serverup xymond_worker.o locator_init xymond_worker.o locator_register_server xymond_worker.o ld: fatal: Symbol referencing errors. No output written to ../client/xymond_client collect2: ld returned 1 exit status gmake[1]: *** [../client/xymond_client] Error 1 gmake[1]: Leaving directory `/tmp/xymon-4.3.7/xymond' gmake: *** [xymond-client] Error 2 Thanks Sean Please consider the environment before printing this email. ------------------------------------------------------------------ Visit guardian.co.uk - newspaper of the year www.guardian.co.uk www.observer.co.uk www.guardiannews.com On your mobile, visit m.guardian.co.uk or download the Guardian iPhone app www.guardian.co.uk/iphone To save up to 30% when you subscribe to the Guardian and the Observer visit www.guardian.co.uk/subscriber --------------------------------------------------------------------- This e-mail and all attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender and delete the e-mail and all attachments immediately. Do not disclose the contents to another person. You may not use the information for any purpose, or store, or copy, it in any way. Guardian News & Media Limited is not liable for any computer viruses or other material transmitted with or as part of this e-mail. You should employ virus checking software. Guardian News & Media Limited A member of Guardian Media Group plc Registered Office PO Box 68164 Kings Place 90 York Way London N1P 2AP Registered in England Number 908396

1 0

Fix - trivial comment change in code
by john.horne＠plymouth.ac.uk 02 Apr '12

02 Apr '12

Hello, Xymon 4.3.7 xymonnet.c has the following line (line 491): * - '|' denotes reverse test, i.e. service should be DOWN. Surely the '|' should be a '!' character. John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001

1 0

Xymon Digest, Vol 14, Issue 27
by j.mcdo73＠gmail.com 02 Apr '12

02 Apr '12

Hi again, I found a Xymon config file which seems to hold the default setup for the RRD graphs created within Xymon (rrddefinitions.cfg). The contents look like this: # 576 datapoints w/ 5 minute interval = 48 hours @ 5 min avg. RRA:AVERAGE:0.5:1:576 # 576 datapoints w/ 6*5 minute averaged = 12 days @ 30 min avg. RRA:AVERAGE:0.5:6:576 # 576 datapoints w/ 24*5 minute averaged = 48 days @ 2 hour avg. RRA:AVERAGE:0.5:24:576 # 576 datapoints w/ 288*5 minute averaged = 576 days @ 1 day avg. RRA:AVERAGE:0.5:288:576 Would I be correct saying that if I *add / append* the following lines, this would include the LAST value to all new graphs created still keepign the AVERAGE? # 576 datapoints w/ 5 minute interval = 48 hours @ 5 min avg. RRA:LAST:0.5:1:576 # 576 datapoints w/ 6*5 minute averaged = 12 days @ 30 min avg. RRA:LAST:0.5:6:576 # 576 datapoints w/ 24*5 minute averaged = 48 days @ 2 hour avg. RRA: LAST:0.5:24:576 # 576 datapoints w/ 288*5 minute averaged = 576 days @ 1 day avg. RRA: LAST:0.5:288:576 Thanks, James > Message: 1 > Date: Fri, 30 Mar 2012 12:21:38 +0200 > From: James McDonald <j.mcdo73 at gmail.com> > To: xymon at xymon.com > Subject: [Xymon] Change default RRD graph definitions > Message-ID: > <CAE4zdC1WB8F+zyTFjTRX2bO8aV8K6ON3UkMbwL2Xt2-=PqgSyg at mail.gmail.com > > > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > I'm looking to change the graph definitions for one of the built-in checks > e.g. [http]. > > The default creation method for the RRD graphs is "average", but I want to > display the "last" value instead. The graphs.cfg file has this to create > http graphs: > > [http] > > DEF:p at RRDIDX@=@RRDFN@:sec:*AVERAGE* > LINE2:p at RRDIDX@#@COLOR@:@RRDPARAM@ > GPRINT:p at RRDIDX@:AVERAGE: \: %5.1lf%s (avg) > > > What needs to be done to change the existing graphs on the system to > display *LAST* instead? > > > Thanks, > James >

1 0

IPv6 support in xymon
by John.Gibbins＠csiro.au 01 Apr '12

01 Apr '12

Thanks Henrik, That is good to hear. We did find that fping on SuSE Linux Enterprise was an ancient one that did not support IPv6. Even on SLES 11 SP2 it is still fping-2.4b2-94.22. We downloaded and installed fping-2.4b2_to-ipv6 (which is over 10 years old!) in order to support IPv6. I don't know what other distributions provide. Great work. I look forward to the upcoming release. regards johng -- John Gibbins Team Leader - IT Security/Authentication (and IPv6 Evangelist) CSIRO Information Management & Technology (IM&T) Phone: +61 2 6124 1419 | Fax: +61 2 6124 1414 | Mob: 0419 605 562 John.Gibbins at csiro.au | www.csiro.au PO BOX 225, Dickson ACT 2602 The only way of discovering the limits of the possible is to venture a little way past them into the impossible. - Clarke's Second Law -----Original Message----- Date: Fri, 30 Mar 2012 23:20:53 +0200 From: Henrik St?rner <henrik at hswn.dk> To: xymon at xymon.com Subject: Re: [Xymon] IPv6 support in xymon Message-ID: <4F7623B5.70909 at hswn.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 30-03-2012 11:05, John.Gibbins at csiro.au wrote: > We are deploying IPv6 across our organisation (spread across > Australia) and use xymon for a lot of our monitoring. We have > scripts which allow xymon to ping hosts via IPv6 to monitor IPv6 > connectivity although it is a bit ugly. > > I understand that IPv6 support is coming in a later release. I'm > curious whether there is an estimate of when this might come out. It is actually fairly close. I have IPv6 working on the Xymon server main daemon (xymond), and the client-side tool (xymon) that communicates with xymond also supports it. So basic IPv6 support is working. Support in the xymonnet tool - that runs the network tests - is underway; it is taking longer than I first expected because I've ended up writing a completely new network test tool instead of hacking the old code. The original xymonnet tool was almost 10 years old, and I've learned a lot about C programming during that time. Also, I wanted to make network tests be analysed in a manner similar to client data - i.e. feed it all into the Xymon server, then have a tool analyse and correlate data centrally. This is currently at a point where the new "xymonnet2" tool can perform the network tests, also against IPv6 enabled hosts and send the data to Xymon, but I have only started doing the analysis module. "ping" tests also haven't been implemented yet, but that should be a very simple thing to do - it will rely on "fping" for both IPv4 and IPv6 hosts. I hope to have it finished for release in a few months. Regards, Henrik ------------------------------ _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon End of Xymon Digest, Vol 14, Issue 27 *************************************

3 2

IPv6 support in xymon
by John.Gibbins＠csiro.au 30 Mar '12

30 Mar '12

Hi I'm brand new to this list, so hopefully this has not already been done to death. We are deploying IPv6 across our organisation (spread across Australia) and use xymon for a lot of our monitoring. We have scripts which allow xymon to ping hosts via IPv6 to monitor IPv6 connectivity although it is a bit ugly. I understand that IPv6 support is coming in a later release. I'm curious whether there is an estimate of when this might come out. Also, I just hit an issue with some Windows systems that run BBwin. They were complaining that they could not talk to the xymon server. The problem turned out to be that clients were configured with the DNS name of the xymon server and the server had both an A record (IPv4 address) and a AAAA record (IPv6 address) in DNS. The operating system chooses the IPv6 address first and BBWin was trying to contact the server using IPv6. The server responded with a RST and the communication failed. The client did not fail back to IPv4. The workaround I am planning on doing is to have a separate DNS name for the server just for xymon use (the server does various things) which only has an IPv4 address in DNS until xymon supports server communication over IPv6. I don't want to hardcode the IPv4 address on the clients as that would make it harder to change later. In August, Josh Luthman suggested that most uses of xymon would be dual stack so would not need IPv6 support. I completely agree that most people are going to be using dual-stack for the foreseeable future, but wanted to point out that we want to be able to monitor our IPv6 network as well as our IPv4 network so IPv6 support is important. In a dual stack environment, IPv6 is used in preference, but if there is a problem with IPv6 connectivity systems will normally fail back to IPv4. This can hide IPv6 network problems. As a result it is important to monitor IPv6 and IPv4 independently otherwise you may not know you have a problem. Also as indicated above, having IPv6 support on the server means we can avoid ugly kludges. My 2c worth. Regards johng -- John Gibbins Technical Lead - IT Security/Authentication CSIRO Information Management & Technology (IM&T)

2 1

Change default RRD graph definitions
by j.mcdo73＠gmail.com 30 Mar '12

30 Mar '12

Hello, I'm looking to change the graph definitions for one of the built-in checks e.g. [http]. The default creation method for the RRD graphs is "average", but I want to display the "last" value instead. The graphs.cfg file has this to create http graphs: [http] DEF:p at RRDIDX@=@RRDFN@:sec:*AVERAGE* LINE2:p at RRDIDX@#@COLOR@:@RRDPARAM@ GPRINT:p at RRDIDX@:AVERAGE: \: %5.1lf%s (avg) What needs to be done to change the existing graphs on the system to display *LAST* instead? Thanks, James

1 0