- Xymon - Xymon mailman web

BBWIN Central Mode - Auto Reset Services
by C.Simmons＠criflending.com 09 Jan '13

09 Jan '13

It seems that after switching to central mode on all of our BBWIN clients we have lost the ability to auto restart services. This would work with the client using a local bbwin.cfg: <setting name=" Symantec_AntiVirus" value="started" autoreset="true" alarmcolor="red" /> However, now that we have moved to a central config the autoreset doesn't work. SVC " Symantec_AntiVirus" startup=automatic status=started autoreset=true Is there a certain syntax that needs be used in analysis.cfg? Any help would be greatly appreciated. Thanks in advance! Clint Simmons This e-mail (and any attachment) is strictly confidential and for use only by intended recipient(s). The opinions therein expressed are those of the author. Its contents, therefore, do not represent any commitment between the company and the recipient(s) and no liability or responsibility is accepted by the company for the above mentioned content. If you are not an intended recipient(s), please notify the author promptly and delete this message.

3 3

Bug in xymonping reporting wrong data when pinging multiple hosts
by Michael.Beatty＠sherwin.com 09 Jan '13

09 Jan '13

Using Xymon 4.3.7 OS Linux SuSE I've been struggling to understand why certain hosts are almost always reporting the exact same ping response time. I've determined, that xymonping isn't working, it is reporting incorrect data for half of the hosts tested. I start by pinging 6 hosts, one at a time, everything is correct /[xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.22 X.X.X.22 is alive (0.06 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.70 X.X.X.70 is alive (0.56 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.138 X.X.X.138 is alive (826 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137 X.X.X.137 is alive (980 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.201 X.X.X.201 is alive (0.75 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.202 X.X.X.202 is alive (0.66 ms) / Then, put them in the same command, the first, second, and fifth values are wrong /[xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.70 X.X.X.22 X.X.X.138 X.X.X.137 X.X.X.201 X.X.X.202 X.X.X.70 is alive (40 ms) X.X.X.22 is alive (20 ms) X.X.X.138 is alive (1307 ms) X.X.X.137 is alive (1738 ms) X.X.X.201 is alive (20 ms) X.X.X.202 is alive (0.64 ms)/ Switch the order of the pings, the first, second, and fifth value are exactly the same as the first time, and still wrong [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.201 X.X.X.202 X.X.X.137 X.X.X.138 X.X.X.70 X.X.X.22 X.X.X.201 is alive (40 ms) X.X.X.202 is alive (20 ms) X.X.X.137 is alive (1598 ms) X.X.X.138 is alive (2069 ms) X.X.X.70 is alive (20 ms) X.X.X.22 is alive (0.04 ms) [xymon at mxbscs tmp]$ Switch the order again, now the third, fourth, and fifth values are wrong. /[xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137 X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 X.X.X.137 is alive (1537 ms) X.X.X.138 is alive (2016 ms) X.X.X.201 is alive (40 ms) X.X.X.202 is alive (20 ms) X.X.X.70 is alive (20 ms) X.X.X.22 is alive (0.06 ms)/ Another thing I have noticed is that by altering the max-pps value, you get completely different results. [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137 X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=1 X.X.X.137 is alive (2000 ms) X.X.X.138 is alive (1000 ms) X.X.X.201 is alive (2000 ms) X.X.X.202 is alive (1000 ms) X.X.X.70 is alive (1000 ms) X.X.X.22 is alive (0.06 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137 X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=5 X.X.X.137 is alive (1500 ms) X.X.X.138 is alive (1479 ms) X.X.X.201 is alive (400 ms) X.X.X.202 is alive (200 ms) X.X.X.70 is alive (200 ms) X.X.X.22 is alive (0.06 ms) [xymon at mxbscs tmp]$ /home/xymon/server/bin/xymonping X.X.X.137 X.X.X.138 X.X.X.201 X.X.X.202 X.X.X.70 X.X.X.22 --max-pps=25 X.X.X.137 is alive (765 ms) X.X.X.138 is alive (896 ms) X.X.X.201 is alive (80 ms) X.X.X.202 is alive (40 ms) X.X.X.70 is alive (40 ms) X.X.X.22 is alive (0.04 ms) It doesn't appear to be a problem with my configuration. I checked the www.xymon.com demo site, and there seems to be the same issue there. The signature of the bad data is easy to see in the graphs as good data has and diverse line, where as bad data is a generally flat line. These hosts look good: http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=pto.linuxbog.dk&SERVICE=co… http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=dali.hswn.dk&SERVICE=conn These hosts look bad: http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=blixen.hswn.dk&SERVICE=conn http://www.xymon.com/xymon-cgi/svcstatus.sh?HOST=wifi.hswn.dk&SERVICE=conn -- Michael Beatty

2 3

One client not showing deatails
by Siddesha.Hanumantharayappa＠ness.com 09 Jan '13

09 Jan '13

Hi Team, One of the client below not show resource details (cpu, disk, memory etc.,), I have installed BBwin on client system, copied BBWin.conf file from working system and just changed host name in that. Still it is not working. Port is also open and I able to telnet port 1984 to Xymon server. Can anyone please help me on this. [cid:image001.png at 01CDEE01.8404AF90] 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.

4 3

Xymon metric data into Graphite?
by craig＠cookitservices.com 09 Jan '13

09 Jan '13

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20130108/0944eeba/attach…>

1 0

strange history issue
by bb4＠richter-it.net 08 Jan '13

08 Jan '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi XYmonians and XYmonettes, I'am running an self-compiled XYmon 4.3.7 on Debian 6. Last week the company I'm working for at the moment experienced a big network outage. After 2 hours everything came back online and XYmon started to get back to green again. Today I saw on a lot of tests, when I click on the "History" button, that they show "clear" or "purple" since the outage although the became "green" again after the network issue was fixed. I also saw in data/histlogs/<SERVER>/<TEST> that the last entry there is the one from the time of the outage when the test went "clear" or "purple". Has this ever happened to someone else and if so, how did you fix it? Or is this a problem with my version that has been fixed in a later one? Thanks Torsten - -- +---------------------------------------------------------+ | E-mail : bb4 [at] richter-it.net | | | | Homepage: http://www.richter-it.net/ | +---------------------------------------------------------+ Download my public key from: http://gpg-keyserver.de/pks/lookup?search=0x899093AC&op=get -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iEYEARECAAYFAlDq87gACgkQ7DlmxomQk6zI4wCg2cYkpuR9C3HRW18BAHnFMbLW +0cAnjIC3AgDFRY1TBMnup8rTkuXNY8Q =RFYU -----END PGP SIGNATURE-----

3 4

Ping tests showing different levels percision
by Michael.Beatty＠sherwin.com 08 Jan '13

08 Jan '13

I just noticed that different hosts are displaying ping results with very different levels precision. On 3 of the hosts, the test seems to be retuning results that are much more precise than on the other 3. If you look at the graphs and data, data points are frequently changing up and down with an active graph. On the other 3, the data is basically a flat line, almost always showing the same value. The one thing that that I can see that the more precise graphs are showing is that all of those systems have ping results measured in milisecods and are on the same network, where as the 3 that are not as precise are not. One of them is my local system itself pinging itself and its data points are measured microseconds. The other two are over a satellite and their pings are between 1 and 3 seconds. For example, one of the hosts is almost always showing 40 ms where as another is changing with ever report between about 1000 ms and 3000 ms. Is this normal, is there some kind of normalization that happens on hosts whos tests don't change much in value? -- Michael Beatty

2 1

help with xymon client configuration
by ciprian.parfon＠gmail.com 08 Jan '13

08 Jan '13

Hello I have just installed a fresh xymon server with the latest xymon version. I have also managed to install the client on some external host. Both are running fine and the monitoring page is showing correctly. However I haven't managed to find how can I configure multiple checks on the client side, as for the single host I have added all I have is "conn", "info" and "trends" columns. On the host which is running the xymon client I have the following files which you can see below: zeratul etc # pwd /home/xymon/client/etc zeratul etc # ls -la total 40 drwxr-xr-x 2 xymon root 4096 2013-01-06 19:31 . drwxr-xr-x 8 xymon root 4096 2013-01-06 16:58 .. -rw-r--r-- 1 xymon root 975 2013-01-06 16:58 clientlaunch.cfg -rw-r--r-- 1 xymon root 20959 2013-01-06 16:58 localclient.cfg -rw-r--r-- 1 xymon root 1850 2013-01-06 16:58 xymonclient.cfg I would like to enable at least cpu, load, memory, disk etc ... Where can I make this available?

3 5

check for Windows service NOT installed?
by david.baldwin＠ausport.gov.au 07 Jan '13

07 Jan '13

We are in the process of migrating between management tools here, and I was wondering if there is a way of configuring analysis.cfg to check that a Windows service is not installed. This would allow me to check that machines with the old tool installed do not have the new one, and vice versa. I tried checking for stopped, but that fails because it's Not Found. I'm hoping to set up something similar to below # running old AV but not new AV CLASS=win32 HOST=%^(host1|host2)\. SVC "InoTask" startup=automatic status=started SVC "MsMpSvc" startup=%.* status=stopped COLOR=yellow # running new AV but not old AV CLASS=win32 EXHOST=%^(host1|host2)\. SVC "InoTask" startup=%.* status=stopped COLOR=yellow SVC "MsMpSvc" startup=automatic status=started If the functionality doesn't exist at present, I'll submit it as a feature request. If all else fails, I can monitor the client channel and roll my own check in perl against the [svcs] section. David. -- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617 ------------------------------------------------------------------------------------- Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender. -------------------------------------------------------------------------------------

1 1

Xymon metric data into Graphite?
by cleaver＠terabithia.org 07 Jan '13

07 Jan '13

> I see that there is a xymond_rrd "--processor=/path/to/script" option. > In theory, could that be used to send all metric data to graphite? > If so, is there also an option to disable Xymon RRD graphs? > If I had to, I could probably create some sort or RAM disk for RRD graphs > and have them contain 1 metric each, but would be nice to just disable RRD. > I found people have created monitoring of Graphite files and send results > to Xymon, but I want to store Xymon metric data in Graphite. > > Thanks > Craig That's exactly what you'd want to do; a while back I was running an RRD processor pipe into an OpenTSDB instance running locally (the processor fixup script did some trivial, and cheap, rewriting) the same way. In terms of preventing xymond_rrd from doing the actual writing of rrd files (even though you're using it for raw data parsing still), I agree that that's annoying. I've only done cursory testing on it, but the attached patch adds a ---no-rrd option to xymond_rrd, which should do what you want. Regards, -jc

1 0

Bug / Feature request rrd files heartbeat.
by Michael.Beatty＠sherwin.com 07 Jan '13

07 Jan '13

Due to network limitations and the number of hosts involved, I decided to back the frequency of reports for the clients back to 15 mintues. I updated the INTERVAL parm in clientlauch.cfg.... easy enough. However, now, none of my graphs are working. Reason being, all of my rrd files have heartbeats of 10 mintues. After looking through the code, I was disappointed to see that the 600 second heartbeat is hardcoded into all of the /xymond/rrd/do_*.c files. This leaves me with two options. 1. Recode all of those programs to create the RRD's from a variable. Or 2. Run rrdtool tune on all of rrds after they are created. Or am I missing something? I would like to see that the heartbeat for rrds that are created would always be equal to 2 X Client INTERVAL. Also, it would be helpful to have in the documentation that you can set the rrd STEP parameter in rrddefinitions.cfg -- Michael Beatty

1 0