January 2013 - Xymon - Xymon mailman web

Xymon with Bacula
by denicoloj＠gmail.com 10 Jan '13

10 Jan '13

Xymon Users, I was wondering if anybody had experience with using xymon to monitor a bacula backup server. I am running a dedicated xymon server, and the bacula backup server is offsite for backup reasons. I have a xymon client only installation on the bacula server so I can receive cpu, disk, and the other system monitors. I came across this xymon extension script ( http://www.revpol.com/xymon_bacula_check_script ) and I installed in on the client side ( bacula backup server ). I followed the instructions (using method 2 bconsole access & modifying the script to fit my environment ) and the test of the xymon user ability to use bconsole works fine. I am not seeing a backup or bacula section on the xymon server webpage. My guess is that I have to add it somehow to the hosts.cfg file on the server side but this is my first custom script / xymon extension that I had to use so I'm not sure what the syntax should look like for the hosts.cfg. Should I specify the full script name like this ( 155.x.x.101 backup # ssh xymon_bacula_check.sh )? Perhaps there is something else im missing server side that needs to be done like put the custom script in server/ext ? Appreciate the help Thanks, * * *Joseph De Nicolo* *Systems & Network Admin**istrator* *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*

2 1

QNAP
by denicoloj＠gmail.com 10 Jan '13

10 Jan '13

Xymon Friends, If it exists, what is the best way to monitor QNAP servers using xymon? I want to install a xymon client on it so I can monitor more than just network services, but I'm unsure if theres a specific way I should go about it since I'm dealing with QNAP hardware. Does anybody know any tips or third-party monitor scripts that are helpful with QNAP servers and NFS operations in general? Appreciate the responses. Thanks, * * *Joseph De Nicolo* *Systems & Network Admin**istrator* *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*

2 1

TS - Program crashed - Fatal signal caught! - 2nd try
by d.tom.schmitt＠L-3com.com 10 Jan '13

10 Jan '13

In the 3 years I have been running Xymon 4.3.0-0.beta2 on my CentOS system, I have never seen this error: Under the ICON 'hobbitd_client' on the primary Xymon server: Program crashed Fatal signal caught! The HISTORY shows nothing to give me a idea of what happened. The Client data doesn't show anything either (it is attached). If I 'restart' Xymon, the ICON stays RED. If I reboot the server, the ICON stays RED. How do I get the ICON back to GREEN? Does anyone know what is going on? Thanks, Tom Schmitt Senior IT Staff - R&D L-3 Communication Systems West 640 North 2200 West P.O. Box 16850 Salt Lake City, UT 84116 Phone (801) 594-3030 Cell (801) 231-7230 \\\\||//// \ ~ ~ / | @ @ | --oOo---(_)---oOo-- Have A Nice Day ! It is not necessary to change. Survival is not mandatory. -- W. Edwards Deming

2 1

[Newbie] Smaller, lighter Xymon based program?
by MatthewHarris＠air-watch.com 09 Jan '13

09 Jan '13

I am very new to linux and xymon is my first project, can anyone help me add a test to test the clusters we are monitoring? I am very new, I have only really touched the hosts.cfg and the analysis.cfg to add the infrastructure and a few services to be monitored on the servers we have set up. I have installed roughly 600 xymon clients manually, we have no method that we are allowed to use to push them. Now I just need to customize the monitoring more for our environment. I also need to figure out how to make a test that will monitor the Microsoft Message Queuing, I have no clue on how I will do that. Can anyone help me out, I need some specific instructions to work with, I am doing my best to set this up with very little knowledge on linux. Thanks in advance!!! Matthew Harris Datacenter Ops O | +1 404.902.4426 C | +1 678.357.1505 F | +1 404.902.4554 MatthewHarris at air-watch.com<mailto:MatthewHarris at air-watch.com> www.air-watch.com<http://www.air-watch.com/> [Description: Description: Description: cid:3420106421_29290231] This communication is confidential and is intended to be privileged pursuant to applicable law. If you are not a designated recipient of this message, please do not read, copy, use or disclose this message or its attachments. Notify the sender by replying to this message and delete or destroy all copies of this message and attachments in all media. Thank you.

3 2

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