- Xymon - Xymon mailman web

Fun with xymon - xynagios and xymondboard
by betsy.schwartz＠gmail.com 07 Jun '13

07 Jun '13

I installed xynagios, which allows dropin execution of nagios plugins in xymon (and a variant xynagios.yellow ) Since there are a lot of useful nagios plugins out there, this represents a huge increase in tests we can use off-the-shelf. Using nagios plugins has an interesting ‘gotcha’. Nagios is event driven ; if it receives an alert, that alert stays unchanged until either a human clears it or a new alert arrives. Xymon however is poll-driven; it expects alert statuses at regular intervals and turns an alert purple if no updates occur within the lifetime (set clientside by the “status” variable in the returned line). As xynagios is run regularly, it does the right thing to update single alerts. But what happens if a Nagios test sends more than one sort of alert? I installed the check_hp_bladechassis plugin, which uses snmp. It sends an “hp_bladechassis” alert when snmp is up but an “snmp” alert when snmp fails. So how to keep these from going stale? What I did was use the ‘xymondboard’ feature to query board status (perl code below) If snmp has not logged recently, we know it must no longer be yellow (since xynagios would have sent a fresh yellow) so set it to green If snmp is yellow, we know the hp_bladechassis data is stale, so set it to clear. my $boardinfo = `$BB $BBDISP "xymondboard host=$blade test=snmp fields=color,logtime"`; ( $color, $logtime ) = split( '\|', $boardinfo ); if ( ( $epoch - $logtime ) > $STALE ) { $bbcmd = "$BB $BBDISP 'status+2h $blade.snmp green $date SNMP now OK on $blade'"; system($bbcmd); } if ( $color eq "yellow" ) { $bbcmd = "$BB $BBDISP 'status+2h $blade.hp_bladechassis clear $date SNMP error unable to run HP test on $blade'"; system($bbcmd); } }

1 0

Xymon 4.3.11 released
by Bernd.Frick＠t-systems.com 07 Jun '13

07 Jun '13

Hello Henrik, to evaluate a replacement for the discontinued "Big Brother Professional Edition" I installed Xymon 4.3.11 on a Solaris 10 SPARC and experienced the same as Matt Goebel did in April: a crashing xymongen. In this thread you announced to fix this with release 4.3.12. Do you already have a ETA for this release? Is there a workaround for this issue (apart from compiling release 4.3.10 and using the older binary)? Thank you. Kind regards Bernd Frick T-Systems DDM GmbH Archive Applications Bernd Frick Josef-Eggler-Straße 8, 88250 Weingarten +49 751 5695-318 (Tel.) E-Mail: bernd.frick at t-systems.com<mailto:hans.mustermann at t-systems.com> Internet: http://www.t-systems.de<http://www.t-systems.de/> Geschäftsführer: Peter Dehm Josef-Bayer-Str. 5, 88250 Weingarten, Deutschland Sitz der Gesellschaft Weingarten Amtsgericht Ulm HRB 552722 WEE-Reg.Nr.DE176062543 Notice: This transmittal and/or attachments may be privileged or confidential. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you.

1 0

cannot update RRD using "data $MACHINE.trends"
by p3yeung＠gmail.com 06 Jun '13

06 Jun '13

I am using xymon 4.3.11. I sent data to multiple RRD files in one data message from the xymon client, but these data are not updated in the RRD files in the xymon server. Any suggestion how to update multiple RRD files in one data message? In the client side, I sent 2 values to each of the 2 RRD files. > cat /tmp/test.data [Test1.rrd] DS:value1:GAUGE:3600:0:U 101 DS:value2:GAUGE:3600:0:U 102 [Test2.rrd] DS:count1:GAUGE:3600:0:U 201 DS:count2:GAUGE:3600:0:U 202 > xymoncmd xymon $XMON_IP "data ct6-metrics.localdomain.trends `cat /tmp/test.data`" In the server side, /var/log/xymon/rrd-data.log shows the RRD files are created. But all the values in both RRD files are 0. Subsequent data message sent using different data does not change anything in the RRD files. 7176 2013-06-05 17:17:12 Creating rrd /var/lib/xymon/rrd/ct6-metrics.localdomain/Test1.rrd 7176 2013-06-05 17:17:12 RRD create param 00: 'rrdcreate' 7176 2013-06-05 17:17:12 RRD create param 01: '/var/lib/xymon/rrd/ct6-metrics.localdomain/Test1.rrd' 7176 2013-06-05 17:17:12 RRD create param 02: '-s' 7176 2013-06-05 17:17:12 RRD create param 03: '300' 7176 2013-06-05 17:17:12 RRD create param 04: 'DS:value1:GAUGE:3600:0:U' 7176 2013-06-05 17:17:12 RRD create param 05: 'DS:value2:GAUGE:3600:0:U' 7176 2013-06-05 17:17:12 RRD create param 06: 'RRA:AVERAGE:0.5:1:576' 7176 2013-06-05 17:17:12 RRD create param 07: 'RRA:AVERAGE:0.5:6:576' 7176 2013-06-05 17:17:12 RRD create param 08: 'RRA:AVERAGE:0.5:24:576' 7176 2013-06-05 17:17:12 RRD create param 09: 'RRA:AVERAGE:0.5:288:576' 7176 2013-06-05 17:17:12 Creating rrd /var/lib/xymon/rrd/ct6-metrics.localdomain/Test2.rrd 7176 2013-06-05 17:17:12 RRD create param 00: 'rrdcreate' 7176 2013-06-05 17:17:12 RRD create param 01: '/var/lib/xymon/rrd/ct6-metrics.localdomain/Test2.rrd' 7176 2013-06-05 17:17:12 RRD create param 02: '-s' 7176 2013-06-05 17:17:12 RRD create param 03: '300' 7176 2013-06-05 17:17:12 RRD create param 04: 'DS:count1:GAUGE:3600:0:U' 7176 2013-06-05 17:17:12 RRD create param 05: 'DS:count2:GAUGE:3600:0:U' 7176 2013-06-05 17:17:12 RRD create param 06: 'RRA:AVERAGE:0.5:1:576' 7176 2013-06-05 17:17:12 RRD create param 07: 'RRA:AVERAGE:0.5:6:576' 7176 2013-06-05 17:17:12 RRD create param 08: 'RRA:AVERAGE:0.5:24:576' 7176 2013-06-05 17:17:12 RRD create param 09: 'RRA:AVERAGE:0.5:288:576' 7176 2013-06-05 17:17:12 Want msg 219, startpos 233160, fillpos 233160, endpos -1, usedbytes=0, bufleft=295223 P Yeung

1 0

flapping DNS error
by dboldt＠usgs.gov 05 Jun '13

05 Jun '13

I have recently downloaded xymon version 4.3.11 to experiment with as a replacement for the last publicly available version of Big Brother. It is running on Solaris 10 x86. The http test on the Display server, for itself, has a flapping status for http with DNS errors. I've experimented with the following, restarting the xymon server application each time server/etc/tasks.cfg CMD xymonnet --report --ping --checkresponse --concurrency=64 CMD xymonnet --report --ping --checkresponse --no-ares server/etc/tasks.cfg/hosts.cfg 130.11.50.48 owipm1.er.usgs.gov # bbd http://owipm1.er.usgs.gov =130.11.50.48 I am only monitoring the server itself and one remote host. xymond.log shows 2013-06-05 00:49:40 Flapping detected for owipm1.er.usgs.gov:cron - 5 changes in 1507 seconds xymonlaunch.log shows many of these 2013-06-05 10:35:04 Task xymongen terminated by signal 6 2013-06-05 10:36:04 Task xymongen terminated by signal 6 2013-06-05 10:37:06 Task xymongen terminated by signal 6 I've run a script which uses dig on the FQDN for the server once every second, and have never seen even a significant delay, let alone a failure. -- -- David Boldt <dboldt at usgs.gov> "Your manuscript is both good and original, but the part that is good is not original and the part that is original is not good." --Samuel Johnson [1709 - 1784], (attributed)

1 0

Has anyone played around with a Nagios wrapper for xymon?
by betsy.schwartz＠gmail.com 05 Jun '13

05 Jun '13

There are so many Nagios plug-ins out there, and we've grabbed a few for xymon and rewritten them, but I'm wondering how feasible it would be to just write a generic nagios wrapper script that called a nagios test and returned the results in xymon format. Seems like it should be straightforward, so I'm wondering if anyone out there has done this already? Betsy -never write what you can steal

4 5

way to tell what version of the client is running
by Paul.Root＠CenturyLink.com 05 Jun '13

05 Jun '13

Hi, Is there a way from the server, to find out what version the client is running? I looked in the xymon command man page, but didn't find anything. Paul.

7 7

what does "O" mean in the [bind] section in graphs.cfg
by jlaidman＠rebel-it.com.au 05 Jun '13

05 Jun '13

Guys The graphs.cfg file has a [bind] section, obviously for graphing BIND DNS query counts for different resource record types (A, SOA, MX, etc). The DS names match the resource record types. One of those types RR types is called "O". As far as I know there's no such record type. So I'm guessing this means "Other", or all other record types. Can anyone confirm that "O" means "Other"? I haven't found anything in doco about this, but it's probably there for compatibility with Hobbit or BigBrother graphs. I could just make a new [bind] section, but I'd like to maintain backwards compatibility. Cheers Jeremy

2 2

IGNORE ignored
by Nick＠Pettefar.com 04 Jun '13

04 Jun '13

In the server/etc/analysis.cfg file I have the following: HOST=ourserver1 LOG=/var/adm/messages IGNORE="%terminal-device not specifiedby login%" # LOG=/var/adm/messages IGNORE="terminal-device not specifiedby login" I want to ignore messages containing the string "terminal-device not specifiedby login" May 31 17:22:53 ourserver1 bpjava-msvc[7112]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module. Unfortunately it doesn't work. From: system user for Xymon Subject: Xymon [214797] ourserver1-ge1:msgs CRITICAL (RED) red Wed May 29 12:52:59 IST 2013 - System logs NOT ok &red Critical entries in <a href="/xymon-cgi/svcstatus.sh? CLIENT=ourserver1&SECTION=msgs:/var/adm/messages">/var/adm/messages</a> &red May 29 12:51:56 ourserver1 bpjava-msvc[12541]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module. &red May 29 12:51:56 ourserver1 bpjava-msvc[12541]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module. <pre> </pre> <pre> </pre> <pre> </pre> What am I doing wrong? Regards, Nick Pettefar

4 4

Xymon application is not working
by Siddesha.Hanumantharayappa＠ness.com 03 Jun '13

03 Jun '13

Hi Team, Xymon application is not working I am finding error logs, please help me someone on this. Below logs in "xymond.log" 2013-05-31 14:49:02 xymond servername MACHINE='uspvldmzlx29' not listed in hosts.cfg, dropping xymond status Below logs in "xymongen.log" 2013-05-27 11:01:35 xymond status-board not available, code 7 2013-05-27 11:01:35 Failed to load current Xymon status, aborting page-update 2013-05-27 11:02:32 Whoops ! Failed to send message (timeout) 2013-05-27 11:02:32 -> 2013-05-27 11:02:32 -> Recipient '161.230.144.78', timeout 15 2013-05-27 11:02:32 -> 1st line: 'xymondboard fields=hostname,testname,color,flags,lastchange,logtime,validtime,acktime,disabletime,sender,cookie,line1,acklist' Below logs in "xymonlaunch.log" 2013-05-31 10:28:53 Setting up logfiles 2013-05-31 11:59:01 xymonlaunch starting 2013-05-31 11:59:01 Loading tasklist configuration from /home/xymon/server/etc/tasks.cfg 2013-05-31 11:59:01 Cannot open directory /home/xymon/server/etc/tasks.d 2013-05-31 11:59:01 Loading hostnames 2013-05-31 11:59:01 Loading saved state 2013-05-31 11:59:01 Setting up network listener on 0.0.0.0:1984 2013-05-31 11:59:01 Setting up signal handlers 2013-05-31 11:59:01 Setting up xymond channels 2013-05-31 11:59:01 Setting up logfiles Below logs in "xymonnetagain.log" 2013-05-28 11:48:21 Execution of '/usr/local/sbin/fping -Ae' failed with error-code 4 2013-05-28 11:48:21 /usr/local/sbin/fping: can't create raw socket (must run as root?) : Operation not permitted Thanks, Siddesh The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by forwarding this email to MailAdmin at ness.com and then delete it from your system. Ness technologies is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

3 15

Monitoring SNMP devices : devmon is still the way to go ?
by linuxmasterjedi＠free.fr 31 May '13

31 May '13

Hi, Most of my colleagues wants to leave XYmon to a crappy monitoring tool such as WhatsUp Gold or Centreon :-( I have to monitor now a bunch of VMware ESXi servers or EMC Data Domain appliances via SNMP or so. Are you doing this ? With Devmon ? Any advices/best pratices ? Thanks ! -- LMJ "May the source be with you my young padawan"

3 9