January 2013 - Xymon - Xymon mailman web

Error compiling Xymon Client in client mode
by fdeschamps.ext＠orange.com 04 Jan '13

04 Jan '13

Hi, I'm trying to compile to compile the Xymon client in client mode (configuration files on the client). I'm using xymon 4.3.10. I'm compiling on ubuntu lucid with pcre and pcre-dev installed. I'm stuck at the build of xymond_client, where it needs xymonclient.a but there is no rule to build it. Indeed, in xymond/Makefile : ../client/xymond_client: $(CLIENTOBJS) ../lib/xymonclient.a $(CC) -o $@ $(RPATHOPT) $(CLIENTOBJS) ../lib/xymonclient.a $(PCRELIBS) $(NETLIBS) $(LIBRTDEF) I didn't find any rules to build xymonclient.a (only a libxymonclient.a in lib/Makefile) Any help would be appreciated. Here are the detailed steps I made : xymon-4.3.10# ./configure --client Configuration script for Xymon client This script asks a few questions and builds a Makefile to compile Xymon Checking your make-utility Xymon normally keeps all of the client configuration files on the Xymon server. If you prefer, it is possible to use a local client configuration file instead - if so, answer 'client' to the next question. NB: Local configuration requires the PCRE libs on each host. Server side client configuration, or client side [server] ? client Checking for the PCRE libraries Checking for PCRE ... Compiling with PCRE library works OK Linking with PCRE library works OK Checking for Large File Support ... Large File Support OK Checking for clock_gettime() requiring librt ... clock_gettime() requires librt What userid will be running Xymon [xymon] ? Found passwd entry for user xymon:x:1005:1000:Xymon user:/home/xymon:/bin/sh Where do you want the Xymon installation [/home/xymon] ? OK, will configure to use /home/xymon as the Xymon toplevel directory What is the IP-address of your Xymon server [127.0.0.1] ? ** NOTE: Using 127.0.0.1 (loopback), but it is probably not what you want ** Using Linux Makefile settings Created Makefile with the necessary information to build Xymon Some defaults are used, so do look at the Makefile before continuing. Configuration complete - now run make -s (GNU make) to build the tools ### Edited Makefile to add PCRE include dir xymon-4.3.10# make MAKE="make" CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/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 -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" OSDEF="-DLINUX" RPATHOPT="-Wl,--rpath," PCREINCDIR="-I/usr/include" ZLIBINCDIR="" SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="" LIBRTDEF="-lrt" XYMONTOPDIR="/home/xymon" XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="127.0.0.1" XYMONHOSTOS="" LOCALCLIENT="yes" make -C lib client make[1]: Entering directory `/root/xymon-4.3.10/lib' gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -o test-endianness test-endianness.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o osdefs.o osdefs.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o cgiurls.o cgiurls.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -DCLIENTONLY -c -o color-client.o color.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o crondate.o crondate.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o digest.o digest.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o encoding.o encoding.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -DXYMONTOPDIR=\"/home/xymon\" -DXYMONLOGDIR=\"\" -DXYMONHOSTNAME=\"\" -DXYMONHOSTIP=\"127.0.0.1\" -DXYMONHOSTOS=\"\" -DBUILD_HOME=\"/home/xymon/client\" -c -o environ-client.o environ.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o errormsg.o errormsg.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o holidays.o holidays.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o ipaccess.o ipaccess.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o md5.o md5.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o memory.o memory.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o misc.o misc.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o msort.o msort.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include `./test-endianness` -c -o rmd160c.o rmd160c.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include `./test-endianness` -c -o sha1.o sha1.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o sha2.o sha2.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o sig.o sig.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o stackio.o stackio.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o strfunc.o strfunc.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o suid.o suid.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -DCLIENTONLY -c -o timefunc-client.o timefunc.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o tree.o tree.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -I/usr/include -c -o matching.o matching.c ar cr libxymonclient.a osdefs.o cgiurls.o color-client.o crondate.o digest.o encoding.o environ-client.o errormsg.o holidays.o ipaccess.o md5.o memory.o misc.o msort.o rmd160c.o sha1.o sha2.o sig.o stackio.o strfunc.o suid.o timefunc-client.o tree.o matching.o ranlib libxymonclient.a || echo "" gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o loadhosts.o loadhosts.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o sendmsg.o sendmsg.c ar cr libxymonclientcomm.a loadhosts.o sendmsg.o ranlib libxymonclientcomm.a || echo "" gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o run.o run.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -I../include -c -o timing.o timing.c ar cr libxymontime.a run.o timing.o ranlib libxymontime.a || echo "" make[1]: Leaving directory `/root/xymon-4.3.10/lib' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" RPATHOPT="-Wl,--rpath," SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="" ZLIBLIBS="" LIBRTDEF="-lrt" XYMONHOME="/home/xymon/client" make -C common client make[1]: Entering directory `/root/xymon-4.3.10/common' gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymon.o xymon.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -o ../client/xymon xymon.o ../lib/libxymonclientcomm.a -lrt ../lib/libxymonclient.a gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymonlaunch.o xymonlaunch.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -o ../client/xymonlaunch xymonlaunch.o ../lib/libxymontime.a -lrt ../lib/libxymonclient.a gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymoncmd.o xymoncmd.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -o ../client/xymoncmd xymoncmd.o ../lib/libxymonclient.a gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymongrep.o xymongrep.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -o ../client/xymongrep xymongrep.o ../lib/libxymonclientcomm.a -lrt ../lib/libxymonclient.a gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymoncfg.o xymoncfg.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -o ../client/xymoncfg xymoncfg.o ../lib/libxymonclient.a gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymondigest.o xymondigest.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -o ../client/xymondigest xymondigest.o ../lib/libxymonclientcomm.a -lrt ../lib/libxymonclient.a make[1]: Leaving directory `/root/xymon-4.3.10/common' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" RPATHOPT="-Wl,--rpath," SSLLIBS="" NETLIBS="" LIBRTDEF="-lrt" XYMONHOME="/home/xymon/client" make -C build all make[1]: Entering directory `/root/xymon-4.3.10/build' gcc -o merge-lines -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include merge-lines.c gcc -o merge-sects -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include merge-sects.c gcc -o setup-newfiles -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include setup-newfiles.c ../lib/libxymonclient.a gcc -o renamevars -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include renamevars.c gcc -o renametasks -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include renametasks.c make[1]: Leaving directory `/root/xymon-4.3.10/build' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" RPATHOPT="-Wl,--rpath," RRDDEF="" RRDINCDIR="" PCREINCDIR="-I/usr/include" NETLIBS="" RRDLIBS="" PCRELIBS="-L -lpcre" ZLIBINCDIR="" ZLIBLIBS="" XYMONTOPDIR="/home/xymon" XYMONHOME="/home/xymon/client" XYMONVAR="" XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="127.0.0.1" XYMONHOSTOS="" XYMONUSER="xymon" CGIDIR="" SECURECGIDIR="" XYMONHOSTURL="" XYMONCGIURL="" SECUREXYMONCGIURL="" MAILPROGRAM=""mail"" RUNTIMEDEFS="" INSTALLWWWDIR="/home/xymon/client/www" INSTALLETCDIR="/home/xymon/client/etc" make -C xymond client make[1]: Entering directory `/root/xymon-4.3.10/xymond' gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymond_client.o xymond_client.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymond_worker.o xymond_worker.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o xymond_buffer.o xymond_buffer.c gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I/root/xymon-4.3.10/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include -c -o client_config.o client_config.c make[1]: *** No rule to make target `../lib/xymonclient.a', needed by `../client/xymond_client'. Stop. make[1]: Leaving directory `/root/xymon-4.3.10/xymond' make: *** [xymond-client] Error 2 root at jmeter01:~/xymon-4.3.10# root at jmeter01:~/xymon-4.3.10# vi client/Makefile root at jmeter01:~/xymon-4.3.10# vi xymon xymond/ xymongen/ xymonnet/ xymonproxy/ root at jmeter01:~/xymon-4.3.10# vi xymond/ Makefile client_config.h do_alert.h rrd/ xymon-mailack.8 xymond_alert.c xymond_channel.c xymond_filestore.c xymond_ipc.h xymond_sample.8 xymonreports.sh.DIST alerts.cfg.5 combo.cfg.5 do_rrd.c rrdcachectl.c xymon-mailack.c xymond_buffer.c xymond_client.8 xymond_history.8 xymond_locator.c xymond_sample.c xymonweb.5 analysis.cfg.5 combostatus.1 do_rrd.h trimhistory.8 xymon.sh.DIST xymond_buffer.h xymond_client.c xymond_history.c xymond_rootlogin.pl xymond_worker.c client/ combostatus.c etcfiles/ trimhistory.c xymond.8 xymond_capture.8 xymond_distribute.8 xymond_hostdata.8 xymond_rrd.8 xymond_worker.h client-local.cfg.5 convertnk.c moverrd.sh.DIST webfiles/ xymond.c xymond_capture.c xymond_distribute.c xymond_hostdata.c xymond_rrd.c xymonfetch.8 client_config.c do_alert.c new-daemon.txt wwwfiles/ xymond_alert.8 xymond_channel.8 xymond_filestore.8 xymond_ipc.c xymond_rrd.h xymonfetch.c root at jmeter01:~/xymon-4.3.10# vi xymond/Makefile root at jmeter01:~/xymon-4.3.10# make CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" OSDEF="-DLINUX" RPATHOPT="-Wl,--rpath," PCREINCDIR="-I/usr/include" ZLIBINCDIR="" SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="" LIBRTDEF="-lrt" XYMONTOPDIR="/home/xymon" XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="127.0.0.1" XYMONHOSTOS="" LOCALCLIENT="yes" make -C lib client make[1]: Entering directory `/root/xymon-4.3.10/lib' make[1]: Nothing to be done for `client'. make[1]: Leaving directory `/root/xymon-4.3.10/lib' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" RPATHOPT="-Wl,--rpath," SSLFLAGS="" SSLINCDIR="" SSLLIBS="" NETLIBS="" ZLIBLIBS="" LIBRTDEF="-lrt" XYMONHOME="/home/xymon/client" make -C common client make[1]: Entering directory `/root/xymon-4.3.10/common' make[1]: Nothing to be done for `client'. make[1]: Leaving directory `/root/xymon-4.3.10/common' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" RPATHOPT="-Wl,--rpath," SSLLIBS="" NETLIBS="" LIBRTDEF="-lrt" XYMONHOME="/home/xymon/client" make -C build all make[1]: Entering directory `/root/xymon-4.3.10/build' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/root/xymon-4.3.10/build' CC="gcc" CFLAGS="-g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -I`pwd`/include -DCLIENTONLY=1 -DLOCALCLIENT=1 -I/usr/include" LDFLAGS="" RPATHOPT="-Wl,--rpath," RRDDEF="" RRDINCDIR="" PCREINCDIR="-I/usr/include" NETLIBS="" RRDLIBS="" PCRELIBS="-L -lpcre" ZLIBINCDIR="" ZLIBLIBS="" XYMONTOPDIR="/home/xymon" XYMONHOME="/home/xymon/client" XYMONVAR="" XYMONLOGDIR="" XYMONHOSTNAME="" XYMONHOSTIP="127.0.0.1" XYMONHOSTOS="" XYMONUSER="xymon" CGIDIR="" SECURECGIDIR="" XYMONHOSTURL="" XYMONCGIURL="" SECUREXYMONCGIURL="" MAILPROGRAM=""mail"" RUNTIMEDEFS="" INSTALLWWWDIR="/home/xymon/client/www" INSTALLETCDIR="/home/xymon/client/etc" make -C xymond client make[1]: Entering directory `/root/xymon-4.3.10/xymond' make[1]: *** No rule to make target `../client/xymond_client', needed by `client'. Stop. make[1]: Leaving directory `/root/xymon-4.3.10/xymond' make: *** [xymond-client] Error 2 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you.

5 13

Sending summaries to remote Xymon servers
by t.ph＠gmx.de 04 Jan '13

04 Jan '13

Hello, I would like to send summaries from a remote Xymon server to the main Xymon server. On the remote Xymon server the hosts.cfg looks like this: page Windows Windows 3.4.5.6 Host1 ... page Linux Linux 4.5.6.7 Host2 ... summary Vengas.Windows 1.2.3.4 https://server.domain.xy/xymon/Windows/ summary Vengas.Linux 1.2.3.4 https://server.domain.xy/xymon/Linux/ A few minutes later I can see the summary on the main Xymon server. It shows one line called "Vengas" with two columns: "Windows" and "Linux". But I still got a problem: The color of "Windows" or "Linux" is the color of the overall status and not as mentioned in the manpage the color of the "Windows" or "Linux" page. Exmaple: on the remote Xymon server: Windows = red, Linux = green, overall status = red Summary on the main Xymon server shows: Windows = red, Linux = red Is this a bug or did I make a mistake? I'm using Xymon Server 4.3.10 Regards, Floh

1 0

Historical data
by Neil.Simmonds＠express-gifts.co.uk 04 Jan '13

04 Jan '13

I have a pair of Aix servers in an HACMP cluster running DB2. I realised recently that although all our Database test scripts that I have written are HACMP aware they still report to a specific machine id on Xymon. I'd like to change the scripts to report as the cluster node name but I don't want to lose the historical data. So essentially I have 3 servers listed on Xymon, Server1 Server2 Servercluster I'd like to combine the historical data from server1 and server2 then load it to servercluster. Is this even possible and if it is how would I do it? Regards, Neil Simmonds Senior Operations Analyst (Operations Support Group) Express Gifts Limited Express House Clayton Business Park Accrington Lancashire BB5 5JY T: 01254 303092 | E: neil.simmonds at Express-Gifts.co.uk Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority -------------- NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030

2 1

MTTR
by vadud3＠gmail.com 03 Jan '13

03 Jan '13

How do people measure MTTR with xymon? Looking for suggestions. Currently it is all visual and then some math. Pretty ugly. Thanks -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

1 0

Behavior of RECOVERED in alerts.cfg
by raylee88＠gmail.com 03 Jan '13

03 Jan '13

On Thu, Dec 20, 2012 at 8:23 AM, Mike Burger <mburger at bubbanfriends.org>wrote: > > Hi all, > > > > Does anyone have an answer for this? > > > >> Is it possible to configure Xymon to send a recovered notification > >> *only* if there was a > >> corresponding notification that was sent for the initial red state? > > > > If it's not possible, can I make a feature request for a future release? > > > > Thanks, > > Ray > > > > > > On Wed, Dec 12, 2012 at 4:55 PM, Raymond Lee <raylee88 at gmail.com> wrote: > >> I have a question about the RECOVERED flag in alerts.cfg. Here's an > >> example: > >> > >> PAGE=somepage COLOR=red > >> MAIL somebody at somewhere.com DURATION>7 RECOVERED REPEAT=1h > >> > >> > >> The behavior I'm seeing is that if a test on PAGE=somepage turns red > >> for less than 7 minutes and then turns green again, we'll get an email > >> for the recovery but not the initial red state. Is this the expected > >> behavior of the RECOVERED flag? Is it possible to configure Xymon to > >> send a recovered notification *only* if there was a corresponding > >> notification that was sent for the initial red state? > > That's interesting...I'm not seeing recovered emails for events that occur > and then clear within the >X timeframe. However, if I recall what I read, > correctly, from the documentation, the polling/reporting time frame is in > increments of 5 minutes...what happens if you change <7 to <10? > > Hi Mike, That shouldn't make a difference. Xymon's default polling frequency is 5 minutes, but we just happen to set ours to 7 minutes. At any rate, DURATION is just the length of time that the test was red, so it shouldn't matter what the polling period is. To confirm this, I tried changing it to DURATION>10 and got the same results. So if the intended behavior of the RECOVERED flag is to send notification whenever a test changes from red/yellow/purple back to green, regardless of how long the test was in the red/yellow/purple state, then it's working as designed. But if there's a way to make it notify only if the DURATION criterion is satisfied, then I'd be interested in hearing about it. Thanks, Ray > -- > Mike Burger > http://www.bubbanfriends.org > > "It's always suicide-mission this, save-the-planet that. No one ever just > stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 > > > >

1 0

RRD Graph stopped graphing
by Michael.Beatty＠sherwin.com 03 Jan '13

03 Jan '13

I had two custom RRD graphs setup and running fine on client systems. The script that collects the data was running every minute. After I finished testing, I changed the frequency of the scripts on the clients to 1 hour in the clientlaunch.cfg file. When I did, the RRD graph stopped displaying data. It ran like this for a couple days. I changed clientlaunch.cfg back to 1 minute... and the graphs immediately started graphing again. Is there a minimum time frame that is needed, or something else that must be done? What am I missing? -- Michael Beatty

3 7

bbwin central mode and analysis rule
by massimiliano.angei＠akhela.com 03 Jan '13

03 Jan '13

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20130103/f729ee6d/attach…>

3 3

Stack Graphs with SPLITNCV data
by everett.vernon＠gmail.com 03 Jan '13

03 Jan '13

Hi all Has anybody managed to create a stack graph with SPLITNCV data? How do we configure it? Once upon a time, I authored this http://www.xymonton.org/monitors:memstat But it had graphing problems if you didn't have ZFS running. (One field less than the RRD graph config required.) In the ToDo section, I promised to have a look at using SPLITNCV. So I am looking into it now, but struggling. To do a STACK graph, the first entry has to be AREA, and the rest need to be STACK. Configuring the RRD graph with SPLITNCV, applies the same graph type to each data set. How do we get the first to be AREA, and the rest STACK? Any assistance appreciated. Regards and a happy new year to you all Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton

3 5

Stack Graphs with SPLITNCV data [RESOLVED]
by everett.vernon＠gmail.com 03 Jan '13

03 Jan '13

Awesome! Works a treat. I have rrdtool 1.4.7 Time to upgrade some scripts on Xymonton. :-) Thanks once again. Vernon On 2 January 2013 21:42, <henrik at hswn.dk> wrote: > Hi Vernon, > > On Wed, 2 Jan 2013 20:46:05 +0800, Vernon Everett > <everett.vernon at gmail.com> wrote: > > Happy New Year! > > thanks, you too. > > > Maybe I didn't express myself correctly. > > I understand what you say below, and the problem isn't with SPLITNCV, > but > > rather with configuring the graphs. > > > > As you say below, we can do foo1 as AREA, and all the rest of > foo2...fooX > > as STACK. > > But how do do this if X is an unknown number? > > OK, now I understand your problem. It depends on what RRDtool version > you're using, but if it's the 1.2.x version then you do it like this in > graphs.cfg: > > FNPATTERN ^disk(.*).rrd > DEF:p at RRDIDX@=@RRDFN@:pct:AVERAGE > AREA:p at RRDIDX@#@COLOR@:@RRDPARAM@:@STACKIT@ > > The STACK keywork is deprecated in RRDtool 1.2.x, you do all of the > stacking with AREA definitions. The "@STACKIT@" thing adds the "STACK" > option for all datasets except the first. > > > Regards, > Henrik > > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton

1 0

Purple background / green status?
by David.Mills＠ngc.com 02 Jan '13

02 Jan '13

Very sorry for the spam, but should have included the datum that the status icon showing "purple" is the "conn" icon. Also of note, is the fact that *all* "conn" icons on this page went purple at the same time, all other statuses are green diamonds. FWIW, the precipitating event was that I deleted about 10 hosts from the hosts.cfg just above the remaining entries. On the next refresh cycle, all "conn"s on this page went purple, but all their details show "green diamonds". Ideas? Thanks so much... david _____________________________________________ From: Mills, David (IS) Sent: Wednesday, January 02, 2013 11:33 AM To: xymon at xymon.com Subject: Purple background / green status? All - Running Xymon 4.3.3... Can anyone tell me why I might be getting purple icons with accompanying page background, but when I click on the icon for detailed info, the current status shows green / unchanged ("diamond")? The hosting page showing "purple" displays the correct / current timestamp. ? Thanks! david ~~~~~~~~~~~~~~~~~~~ David Mills Systems Administrator Northrop Grumman 512-595-1238 david.mills at ngc.com<mailto:david.mills at ngc.com>

3 3