March 2011 - Xymon - Xymon mailman web

make: Fatal error: Command failed for target `rrdtoolmodule.o' [Sun Solaris 5.10]
by jayantak007＠gmail.com 13 Mar '11

13 Mar '11

Hi All, In Sun Solaris 5.10 i am trying to install rrdtool-1.2.19. 1. #./configure [It's success] 2. # make [It's giving following error:] creating rrdcgi Making all in bindings Making all in python if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -g -O2 -fno-strict-aliasing -Wall -std=gnu99 -pedantic -Wshadow -Wpointer-arith -Wcast-align -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -W -fPIC -DPIC -I../../src -I/usr/sfw/include/python2.3 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -I/usr/include/libart-2.0 -I/usr/include/freetype2 -I/usr/sfw/include -I/usr/sfw/include/freetype2 -g -O2 -fno-strict-aliasing -Wall -std=gnu99 -pedantic -Wshadow -Wpointer-arith -Wcast-align -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -W -fPIC -DPIC -MT rrdtoolmodule.o -MD -MP -MF ".deps/rrdtoolmodule.Tpo" -c -o rrdtoolmodule.o rrdtoolmodule.c; \ then mv -f ".deps/rrdtoolmodule.Tpo" ".deps/rrdtoolmodule.Po"; else rm -f ".deps/rrdtoolmodule.Tpo"; exit 1; fi In file included from /usr/include/limits.h:18, from /usr/sfw/include/python2.3/Python.h:19, from rrdtoolmodule.c:42: /usr/include/sys/feature_tests.h:332:2: #error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications" rrdtoolmodule.c: In function `PyRRD_fetch': rrdtoolmodule.c:202: warning: implicit declaration of function `__builtin_isnan' rrdtoolmodule.c:202: warning: nested extern declaration of `__builtin_isnan' rrdtoolmodule.c: In function `PyRRD_info': rrdtoolmodule.c:449: warning: nested extern declaration of `__builtin_isnan' rrdtoolmodule.c:469: warning: nested extern declaration of `__builtin_isnan' *** Error code 1 make: Fatal error: Command failed for target `rrdtoolmodule.o' Current working directory /RRDTool/rrdtool-1.2.19/bindings/python *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list=' python'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /RRDTool/rrdtool-1.2.19/bindings *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src bindings doc examples'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /RRDTool/rrdtool-1.2.19 *** Error code 1 make: Fatal error: Command failed for target `all' [root at dc1u011 rrdtool-1.2.19]# Kindly provide me the solution. With Regards, Jayanta.

2 1

Zymon 4.2.3 libssl error (64bit)
by skoupi＠gmail.com 12 Mar '11

12 Mar '11

Hi, I tried to install Zymon 4.2.3 in a Centos 64 bit and get the following message when I run make install : etcfiles; (echo "bb-hosts"; echo "hobbit-alerts.cfg"; echo "hobbit-clients.cfg"; echo "bbcombotest.cfg"; echo "client-local.cfg") | ../../build/setup-newfiles /home/xymon/server/etc/ ../../build/setup-newfiles: error while loading shared libraries: libssl.so.6: cannot open shared object file: No such file or directory make[1]: *** [install-cfg] Error 127 make[1]: Leaving directory `/home/xymon/xymon-4.2.3/hobbitd' make: *** [install-hobbitd] Error 2 It seems the installation needs the openssl and openssl-devel 32 bit instead of 64, I have tried to create a symbolic link to the 64 version but it confirms the error with a message regarding ELF-64.. Can some one please tell me if Xymon is official compatible with 64 bit systems and if yes how can I proceed with this problem ? Regards, Skou.

1 0

Alternative DB to RRD
by henrik＠hswn.dk 11 Mar '11

11 Mar '11

Den 10-03-2011 16:11, Gautier Begin skrev: > > My version of XYMON should have a bug. It won't work ! and my script is > in 777 and the path is the good one. Try using the 2-line shell script I posted and let it run for 10-15 minutes. Then take the output file and feed it as input to your script and see what happens. >> I tried this on the www.xymon.comdemo-site using this miniature >> shell script: >> >> #!/bin/sh >> exec /bin/cat >>/var/tmp/rrdfeed.txt >> >> and it seems to work ok. Here's some sample data: >> >> la 1299755931:63 renoir.hswn.dk la >> la 1299755931:145 renoir.hswn.dk procs Regards, Henrik

2 1

hpux-meminfo.c, modified ksh script.
by jasonajfredricksen＠gmail.com 10 Mar '11

10 Mar '11

Hello, Another way to do it via top: #!/usr/bin/ksh # 10 DEC 2010 Daniel Grahek # This script properly calculates memory values on HP-UX 11iv3 Itanium systems # This script replaces the binary hpux-meminfo in client/bin directory. # version 1.0 # Distributed under GPL v2 license. TMPF=/tmp/`basename $0`.$$ top -d 1 -s 1 -f $TMPF FREEKB=`grep Memory $TMPF | awk ' { print $8 } ' | tr -d K` rm $TMPF FREEREPORT=`echo $FREEKB / 1024 |/usr/bin/bc` TOTAL=`/usr/sbin/swapinfo |grep ^memory |awk {'print $2'}` TOTALREPORT=`echo $TOTAL / 1024 |/usr/bin/bc` echo Total:$TOTALREPORT echo Free:$FREEREPORT may be better ways. Tanks everyone, Jason F.

1 0

multicast network monitoring
by olivier＠audry.fr 10 Mar '11

10 Mar '11

hello someone already do this ? I found this : http://opensource.ok.is/trac/browser/nagios-okconfig/trunk/okconfig/templat… oau

2 1

Working : Simple xymonclient on openwrt
by xymon＠jonmail.co.uk 10 Mar '11

10 Mar '11

Hi, I am happy to say I have a xymon client running on Openwrt. I thought other people might find this useful in three ways: 1) If you are running openwrt you can take this code and run a xymon client to monitor your openwrt system. 2) People using other small unix-like systems can use the same design to run a xymon client, even if the code doesn't fit exactly. 3) My approach uses only shell scripts, none of the xymon binaries need to be cross compiled. So anyone struggling to compile xymon client for a foreign system can use this approach; all they need to do is add a few shell scripts and they don't need to compile anything. Details below. jonty --- * Equipment I used the following pieces to put this together: 1) xymon 4.3.0 from : http://sourceforge.net/projects/xymon 2) openwrt 10.03 from : http://openwrt.org 3) Linksys WAG354G modem and router : 150MHz, 4MB flash, 16MB ram --- * Design I already have a xymon server running in my network. It monitors web servers, mail servers, and so on. I wanted to add monitoring to the broadband modem, which runs openwrt. The broadband modem must send xymon status messages to the xymon server every five minutes. These messages are generated by the shell scripts xymonclient-linux.sh and xymonclient.sh. These are started every five minutes by cron. 1) xymonclient-linux.sh - This is part of the source of xymon 4.3.0. It generates the "body" of each message by running tools such as df, ps, and top. I had to make a few changes to this so it would run on openwrt but I tried to keep these changes as small as possible (see below). 2) xymonclient.sh - This started from the source of xymon 4.3.0 but had to change so much you could consider this a rewrite. The purpose of this script is to take the output from xymonclient-linux.sh, add a "header" and "footer" to the output, and then transmit the finished message over the local network to the xymon server (see below). 3) cron - The xymon package includes a tool called xymonlaunch which runs other parts of the package to a configured schedule. But the schedule on this client is so simple it can be handled by cron, which is already included in openwrt (see below). No other parts of the xymon package are used on openwrt. The two shell scripts xymonclient-linux.sh and xymonclient.sh use only core linux utilities which are already included in openwrt. There is no need to copy xymon binaries or config files to openwrt. --- * xymonclient-linux.sh I copied this script from the source of xymon 4.3.0 onto openwrt and put it in the file /bin/xymonclient-linux.sh. I ran it to see what happened. It executed but it produced a few errors. Redirecting the usual output to /dev/null let me see just the errors and start fixing them: openwrt$ /bin/xymonclient-linux.sh >/dev/null 1) Configure openwrt busybox to include the core utilities: who, nohup. These tools are missing from a standard build of openwrt but they are needed by the xymonclient. See http://wiki.openwrt.org/doc/howto/build 2) Add the package procps. This includes a "real" ps, rather than the minimal ps that is part of busybox. It also includes vmstat. 3) The df tool in openwrt busybox doesn't support -l or -x. And openwrt uses a rom filesystem as root. So the commands to run df become: > echo "[df]" > EXCLUDES=`cat /proc/filesystems | grep nodev | awk '{print $2}' | xargs echo iso9660 rom root | sed -e 's! !|!g'` > df -P | grep -v -E "$EXCLUDES" | sed -e '/^[^ ][^ ]*$/{ 4) If you run ps you will get the simple one in openwrt busybox. But if you run /usr/bin/ps you will get the full featured one from the procps package. So the command to run ps becomes: > echo "[ps]" > /usr/bin/ps -Aww -o pid,ppid,user,start,state,pri,pcpu,time,pmem,rsz,vsz,cmd 5) Top is not configured by the install utility. So the command to run it becomes: > echo "[top]" > top -b -n 1 6) To run vmstat we don't have the usual xymon configuration variables such as MACHINEDOTS to build temporary files. Fortunately we can use mktemp and do something simple: > echo "[vmstat]" > TMPFILE=`mktemp -t` > nohup sh -c "vmstat 300 2 1>$TMPFILE 2>&1; mv $TMPFILE /tmp/xymon_vmstat" </dev/null >/dev/null 2>&1 & > if [ -f /tmp/xymon_vmstat ]; then > echo "[vmstat]" > cat /tmp/xymon_vmstat > rm -f /tmp/xymon_vmstat > fi --- * xymonclient.sh This script is a wrapper around xymonclient-linux.sh. When it runs it has to add a header and a footer to the output and then copy the output over the network to the xymon server. The server is running on some machine in the local network and listening at port 1984. If you use the code below put the address of your xymon server machine in the XYMSRV variable. The original script xymonclient.sh is part of xymon 4.3.0. But this uses a few of the xymon binaries to generate parts of the header and footer, then it uses another binary to transmit the message. I decided to replace the calls to binaries with core utilities that are already included in openwrt. In particular I used netcat to transmit the message over the network. I started from the original xymonclient.sh script that is part of xymon 4.3.0 and simplified it step by step to reduce it to only what is needed. I ended up with a top-to-bottom rewrite of the script. I put this in /bin/xymonclient.sh : > #!/bin/sh > > # Configuration for the local machine. > # This is hardcoded until I find a better way to do it. > MACHINE=`hostname | tr . ,` > SERVEROSTYPE=linux > CONFIGCLASS=linux > XYMSRV=192.168.1.1 > > # Must make sure core utilities return standard (english) texts. > LANG=C > LC_ALL=C > LC_MESSAGES=C > export LANG LC_ALL LC_MESSAGES > > # Use a temporary file to build the status message > TMPFILE=`mktemp -t` > > # Header line describes the source of this status message > echo "client $MACHINE.$SERVEROSTYPE $CONFIGCLASS" >> $TMPFILE > > # Information from core utilities > /bin/xymonclient-linux.sh >> $TMPFILE > > # Client version > echo "[clientversion]" >> $TMPFILE > echo "" >> $TMPFILE > > # System clock > NOW=`date "+%Y-%m-%d %H:%M:%S"` > echo "[clock]" >> $TMPFILE > date -d "$NOW" "+epoch: %s" >> $TMPFILE > date -d "$NOW" "+local: %Y-%m-%d %H:%M:%S %Z" >> $TMPFILE > date -d "$NOW" -u "+UTC: %Y-%m-%d %H:%M:%S GMT" >> $TMPFILE > > # Transmit status message to server > nc $XYMSRV 1984 < $TMPFILE > > # Remove temporary file > rm -f $TMPFILE > > # Done > exit 0 --- * cron All that is needed is a single line in /etc/crontabs/root on the openwrt machine that tells crond to run xymonclient.sh every five minutes: > */5 * * * * /bin/xymonclient.sh

3 2

Alternative DB to RRD
by gbegin＠csc.com 10 Mar '11

10 Mar '11

Hello, I have heard that we could store measurements not only in RRD files but also in standard DataBase (mySQL for expl) using a task through xymon channel. Where can I find such dev ? Cordialement, Regards,Mit freundlichen Grüßen, Gautier BEGIN Admin and Tools Team CSC - Luxembourg Global Outsourcing Service | p:+352 24 834 276 | m:+352 621 229 172 | gbegin at csc.com | www.csc.com CSC • This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose • CSC Computer Sciences SAS • Registered Office: Immeuble Le Balzac, 10 Place des Vosges, 92072 Paris La Défense Cedex, France • Registered in France: RCS Nanterre B 315 268 664

2 3

hobbit-clients.cfg
by shailesh.paudyal＠gmail.com 10 Mar '11

10 Mar '11

hello, I have installed new xymon-4.3.0 version, I wanted to modify the threshold as I used to on older xymon releases using file hobbit-clients.cfg, I could not locate that file in the new one. Can anyone point me to the right direction? Thank you! -- Shailesh K. Paudyal shailesh.paudyal at gmail.com

4 4

Rrd file isn't created
by henrik＠hswn.dk 10 Mar '11

10 Mar '11

>>> I have a test on a machine titled 'AMOS'. Xymon >> server is 4.2.3. > > No, the test is named AMOS, the machine is mdsobj3. OK, I misunderstood then - I thought the name of the machine was "AMOS". > MESSAGE="rows : $3" > . > . > . > > $BB $BBDISP "status $MACHINE.$TEST $COLOR $MESSAGE $id" Try putting a line-break before the $MESSAGE. Like $BB $BBDISP "status $MACHINE.$TEST $COLOR $MESSAGE $id" Regards, Henrik

2 2

BBWin word pattern
by Daniel.Nordquist＠orlandohealth.com 09 Mar '11

09 Mar '11

No problem. I'm no pro with xymon, but I'm learning and I'm glad I could help! From: Camelia Anghel [mailto:canghel at cjh.org] Sent: Wednesday, March 09, 2011 2:43 PM To: Nordquist, Daniel Subject: RE: BBWin word pattern Thank you, I'll work with it. Camelia From: Nordquist, Daniel [mailto:Daniel.Nordquist at orlandohealth.com] Sent: Wednesday, March 09, 2011 1:34 PM To: Camelia Anghel; xymon at xymon.com Subject: RE: BBWin word pattern It seems you could use a combination of match and ignore settings to achieve what you're looking for? Might take some work but I'm sure you could get there. <match logfile="System" value="text string you're looking for" source="source of the event" eventid="0000" /> <ignore logfile="System" value="text string you don't want" type="types you don't want" /> <ignore logfile="Application" source="source types you don't want" type="types you don't want" /> <ignore logfile="Security" source="source types you don't want" type="types you don't want" eventid="id's you don't want" /> Etc Etc Etc Might work? From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Nordquist, Daniel Sent: Wednesday, March 09, 2011 1:08 PM To: Camelia Anghel; xymon at xymon.com Subject: Re: [Xymon] BBWin word pattern Does the word pattern you want to search for show up in the data on your hobbit server when you click on the msgs icon? From: Camelia Anghel [mailto:canghel at cjh.org] Sent: Wednesday, March 09, 2011 12:59 PM To: Nordquist, Daniel Subject: RE: BBWin word pattern Yes, I want to look in the data of the log for word pattern. Thanks Camelia From: Nordquist, Daniel [mailto:Daniel.Nordquist at orlandohealth.com] Sent: Wednesday, March 09, 2011 12:55 PM To: Camelia Anghel; xymon at xymon.com Subject: RE: BBWin word pattern No difference in the type or source of the event logs? You want to look in the data of the log for your word pattern? From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Camelia Anghel Sent: Wednesday, March 09, 2011 12:35 PM To: xymon at xymon.com Subject: [Xymon] BBWin word pattern Hello, I have BBWin-0.12 and I am trying to shrink the EventLog msgs . Is there a way to use word pattern in the local-config.cfg file on the windows client? I would like to keep some EventLog id's with a certain pattern, but not all. Thanks, Camelia Camelia Anghel Database Coordinator Center for Jewish History 15 West 16 St, New York, NY 10011 phone:(917)606-8248 canghel at cjh.org ________________________________ This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandohealth.com . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Health by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Health. ________________________________ This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandohealth.com . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Health by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Health. ________________________________ This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandohealth.com . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Health by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Health. ________________________________ This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandohealth.com . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Health by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Health.

1 0