February 2013 - Xymon - Xymon mailman web

EXT :Re: What tests are coming from a client?
by David.Mills＠ngc.com 21 Feb '13

21 Feb '13

Many thanks to all who replied: you were right on the money! FWIW, can anyone point out where I can look on the server side to make sure current data has arrived for the expected tests? Thanks! david From: Novosielski, Ryan [mailto:novosirj at umdnj.edu] Sent: Tuesday, February 19, 2013 5:27 PM To: Mills, David (IS); 'jlaidman at rebel-it.com.au' Cc: 'xymon at xymon.com' Subject: Re: [Xymon] EXT :Re: What tests are coming from a client? Like he said, check the ghost client report and make sure your client software is even running at all on the client machine. From: Mills, David (IS) [mailto:David.Mills at ngc.com] Sent: Tuesday, February 19, 2013 06:23 PM To: Jeremy Laidman <jlaidman at rebel-it.com.au<mailto:jlaidman at rebel-it.com.au>> Cc: xymon at xymon.com<mailto:xymon at xymon.com> <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] EXT :Re: What tests are coming from a client? Jeremy / Dan – I think you’re on the right track. How can I check from the server side to make sure current data has arrived for the expected tests? david From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Tuesday, February 19, 2013 5:16 PM To: Mills, David (IS) Cc: xymon at xymon.com<mailto:xymon at xymon.com> Subject: EXT :Re: [Xymon] What tests are coming from a client? David Those tests that are showing are server-side "probe" tests. They can work even if the target host is not running a Xymon client, and they involve the Xymon server (specifically xymonnet) sending ping packets and attempting TCP socket connections. The other tests you want (CPU, memory, iostat) require the Xymon client to be running on the host. If you have that installed and running, it might not be sending the client-side messages to the server, and you should try to find out why. Start by checking your ghost client report. Cheers Jeremy On 20 February 2013 09:49, Mills, David (IS) <David.Mills at ngc.com<mailto:David.Mills at ngc.com>> wrote: Hi, all… My boss just walked up and asked me “why all the tests aren’t available for this host on Xymon?” I had to confess I didn’t know the answer and am hoping you can help. The entry for the host in hosts.cfg is: <ip> <hostname> # ssh ntp TRENDS:*,zonestat:zonestatcpu|zonestatmem|zonestatnproc|zonestatsize|zonersssize What shows on the screen is just the results from ntp, ssh, info and trends. For the life of me, I can’t get it to display cpu, memory, mem2, iostat, or any of the other usual column “tests”. I’ve tried using the following configuration variations in hosts.cfg, all with the same results: <ip> <hostname> # and <ip> <hostname> # cpu disk iostat iostat2 mem memory ntp ssh TRENDS:*,zonestat:zonestatcpu|zonestatmem|zonestatnproc|zonestatsize|zonersssize but I can’t get more than the original four columns mentioned above to populate. It is painfully obvious to me at this point that I do not fully understand the rules at work as to what causes columns to appear / disappear. Help? / Thanks! david ~~~~~~~~~~~~~~~~~~~ David Mills Systems Administrator Northrop Grumman 512-595-1238 david.mills at ngc.com<mailto:david.mills at ngc.com> _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

3 2

What tests are coming from a client?
by David.Mills＠ngc.com 21 Feb '13

21 Feb '13

Hi, all... My boss just walked up and asked me "why all the tests aren't available for this host on Xymon?" I had to confess I didn't know the answer and am hoping you can help. The entry for the host in hosts.cfg is: <ip> <hostname> # ssh ntp TRENDS:*,zonestat:zonestatcpu|zonestatmem|zonestatnproc|zonestatsize|zonersssize What shows on the screen is just the results from ntp, ssh, info and trends. For the life of me, I can't get it to display cpu, memory, mem2, iostat, or any of the other usual column "tests". I've tried using the following configuration variations in hosts.cfg, all with the same results: <ip> <hostname> # and <ip> <hostname> # cpu disk iostat iostat2 mem memory ntp ssh TRENDS:*,zonestat:zonestatcpu|zonestatmem|zonestatnproc|zonestatsize|zonersssize but I can't get more than the original four columns mentioned above to populate. It is painfully obvious to me at this point that I do not fully understand the rules at work as to what causes columns to appear / disappear. Help? / Thanks! david ~~~~~~~~~~~~~~~~~~~ David Mills Systems Administrator Northrop Grumman 512-595-1238 david.mills at ngc.com

5 7

Services false positive
by MatthewHarris＠air-watch.com 21 Feb '13

21 Feb '13

Hey Everyone, I think I found a bug in xymon, I am monitoring a few hundred servers and I found that servers with similar names but different purposes are trying to report the same services. For instance, XXXXXXXXXXX486 and XXXXXXXXXXX487 is duplicating the service checks for XXXXXXXXXXX48. Is there any way that anyone knows of to get xymon to look at the entire machine name instead of just the first 12 characters of it? Matthew Harris DC.Ops O | 404.902.4426 C | 678.357.1505 MatthewHarris at air-watch.com<mailto:MatthewHarris at air-watch.com> www.air-watch.com<http://www.air-watch.com/> [AirWatch Connect 2013 - Feb. 25-28 - Learn More]<http://www.air-watch.com/connect/barcelona-2013> 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.

4 4

Library Errors on Solaris 9
by everett.vernon＠gmail.com 21 Feb '13

21 Feb '13

Hi all Encountered an interesting problem installing my Xymon client on Solaris 9. I have solved it, but it's interesting enough that I felt it was worth sharing with the list. And maybe get some feedback on other approaches. The client was compiled on Solaris 10, so I was expecting the Solaris binary compatibility thing to make it all "just work" when I copied the client to Solaris 9. But that would be too easy. :-/ Most of the binaries gave this issue. ld.so.1: /usr/local/xymon/client/bin/msgcache: fatal: *libresolv.so.2*: version `SUNW_2.2.2' not found (required by file /usr/local/xymon/client/bin/msgcache) zsh: killed /usr/local/xymon/client/bin/msgcache Looks like *libresolve.so.2* is missing The library is there # grep libresolv.so.2 /var/sadm/install/contents /usr/lib/libresolv.so=./libresolv.so.2 s none SUNWcsl */usr/lib/libresolv.so.2* f none 0755 root bin 316552 9398 1268771224 SUNWcsl /usr/lib/sparcv9/libresolv.so=libresolv.so.2 s none SUNWcslx /usr/lib/sparcv9/libresolv.so.2 f none 0755 root bin 385952 24889 1268771224 SUNWcslx And we have the LD_LIBRARY_PATH set correctly. % echo $LD_LIBRARY_PATH /opt/svrexp/dvlpr/2.2/lib:/usr/openwin/lib:*/usr/lib* :/opt/cics/lib:/opt/dcelocal/lib:/opt/encina/lib:. So I checked to see if there was another issue, and it turns out it can see libresolv.so.2, but wants a specific version. # ldd /usr/local/xymon/client/bin/msgcache libresolv.so.2 => /usr/lib/libresolv.so.2 * libresolv.so.2 (SUNW_2.2.2) => (version not found)* libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 librt.so.1 => /usr/lib/librt.so.1 libc.so.1 => /usr/lib/libc.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libmp.so.2 => /usr/lib/libmp.so.2 libaio.so.1 => /usr/lib/libaio.so.1 libmd5.so.1 => /usr/lib/libmd5.so.1 /usr/platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1 /usr/platform/SUNW,Sun-Fire-V240/lib/libmd5_psr.so.1 Then I recalled hearing about the LD_NOVERSION parameter you can set, which causes the the runtime linker to ignore version requirements. A bit of reading here also helped. http://docs.oracle.com/cd/E19963-01/html/819-0690/docinfo.html I added the following 2 lines to the top of the ~/client/runclient.sh script *LD_NOVERSION=1 export LD_NOVERSION* Restarted, and it all worked fine. Maybe some of the programmer types can provide us with some feedback on the correctness of this approach, or even provide a better solution, but for now, it's working. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton

3 3

Repeat HTTP-Test for HTTP Response Time ?
by jlaidman＠rebel-it.com.au 21 Feb '13

21 Feb '13

You could probably do this by adding an alternative HTTP check such as "cont" or "post" or "httpstatus" with the same URL as for the HTTP check. J On 21 February 2013 02:30, Werner Maier <werner at maiers.de> wrote: > Hi, > > I'm trying to set up a test for HTTP Response Time. > This works ok for most things out of the box. > > Now the problem: > I have a page that will be generated and then cached > into memcache by the application on the webserver. > > I now want to record both - cached and uncached - http response times. > > I can fetch an uncached result with a special get parameter like this: > http://server/?nocache > so that is not a problem. > But for the cached content, I need to ensure that the page is > fetched two times and only record the second request response time. > (the first one might be the one that generates the page and stores > it into the cache so it might have wrong timings). > > Is there a possibility to do this with the onboard xymonnet things > or do I have to write my own test for this? > > kind regards > > Werner Maier > -- > Dipl.-Ing. Univ. Werner Maier > http://www.maiers.de/ > ______________________________**_________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/**mailman/listinfo/xymon<http://lists.xymon.com/mailman/listinfo/xymon> >

1 0

Date issue with enable/disable page on 4.3.8
by tlewick＠apsaranetworks.com 20 Feb '13

20 Feb '13

I'm running xymon 4.3.8. Recently I disabled a couple of alerts via the web-page. Two issues, first it works for a while, but then some random and pretty short time later, the page shows red again. Also, the second or third time, I just set the alert out quite a ways, like disable until February 2014, and I noticed xymon reports funky dates like the one below. Disabled until Tue Oct 19 07:48:44 1926 Is this a known bug with xymon in this verison? Thanks, T

4 5

Repeat HTTP-Test for HTTP Response Time ?
by werner＠maiers.de 20 Feb '13

20 Feb '13

Hi, I'm trying to set up a test for HTTP Response Time. This works ok for most things out of the box. Now the problem: I have a page that will be generated and then cached into memcache by the application on the webserver. I now want to record both - cached and uncached - http response times. I can fetch an uncached result with a special get parameter like this: http://server/?nocache so that is not a problem. But for the cached content, I need to ensure that the page is fetched two times and only record the second request response time. (the first one might be the one that generates the page and stores it into the cache so it might have wrong timings). Is there a possibility to do this with the onboard xymonnet things or do I have to write my own test for this? kind regards Werner Maier -- Dipl.-Ing. Univ. Werner Maier http://www.maiers.de/

1 0

sepparated disk alerts
by aiqueneldar＠gmail.com 20 Feb '13

20 Feb '13

Greetings I don't know if this is the correct forum for this question or more like it, new feature request. How ever I'm gonna post here and hope someone will point me right if this is the wrong place. For the issue at hand. At my company we use Xymon to monitor thousands of servers. And sometimes disks gets filled and thus generates an alert. Sometimes this won't get looked into for a couple of days since our clients have specified that they want to remove data themselves (and not buy more storage). And as several servers have 3 - 8 disk and/or partitions we sometimes have trouble monitoring the other disks since one is already sending an alert. Example: Server1 has 3 monitored partitions of a disk: / /srv/important/data /srv/database with the same limits on all three: 80% -> yellow alert; 90% -> red alert Then if /srv/important/data reaches 82% the client wants us to notify them and they will free up space. This normaly takes around 3 - 5 working days. But they also wants us to monitor /srv/database. And say that 1 day after /srv/important/data gets filled, /srv/database reaches 84%. That will not trigger a new alert in the non-green status view which is what we monitor. The question/request is then as this: Is there a way to get the client to report each disk/partition as a separate alert, so we can disable the alert for one disk while receiving alerts for the other disks/partions. To use the example I want to be able to temporarily set /srv/important/data in disabled mode while still getting alerts from /srv/database I know this could be solved by writing my own script for the client, but that was disapproved of from management as they want as few custom scripts to maintain as possible (we already have dozens of custom scripts). All help and feedback is appreciated, thanks. Kind regards Calle Lejdbrandt

6 6

Questions regarding installation of Xymon
by dl1025＠att.com 19 Feb '13

19 Feb '13

I am looking to install xmon on our linux server, however, our SA's will not give me root to install it. Can I install xymon without root and get it up and running? If so, is there an installation manual that I can see. When I used BigBrother, I installed everything using root and could not do it otherwise, I wonder if it is possible to install Xymon without the use of root.

3 2

sepparated disk alerts
by aiqueneldar＠gmail.com 19 Feb '13

19 Feb '13

I include the list in this response as I think it was left out by mistake. That is a good answer, and will probably help people in similar situations out. This will however not work for us as we don't use the email-functionality at all in xymon. Also this is a decision from management. So I need a solution that will show up in the non-green systems view in xymon. And also I need to get alerts based on that a filesystem changes state, not based on one disk changes state on a host as it is natively. I do know this is very specefic. But I have tried several workarounds and have been shot down from management because they want changes to the client to come upstream since the disk alert technically is working. It is just annoying for us who have to work with it this way. Kind regards Calle Lejdbrandt On Fri, Feb 15, 2013 at 10:51 PM, Mike Burger <mburger at bubbanfriends.org> wrote: > While I don't have a Xymon specific, technical answer, I do have a > suggestion, which I've put to use in other places, with other monitoring > tools. > > Send the emails to an account on the Xymon server, maybe even xymon, itself. > > For the user in question, create a .procmailrc file and make use of > Procmail's ability to filter and forward. You can then filter the alarms > based on subject and/or body content, forward out the messages that need a > response, and send the rest to /dev/null. > -- > 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 > > >> Greetings >> >> I don't know if this is the correct forum for this question or more >> like it, new feature request. How ever I'm gonna post here and hope >> someone will point me right if this is the wrong place. >> >> For the issue at hand. At my company we use Xymon to monitor thousands >> of servers. And sometimes disks gets filled and thus generates an >> alert. Sometimes this won't get looked into for a couple of days since >> our clients have specified that they want to remove data themselves >> (and not buy more storage). And as several servers have 3 - 8 disk >> and/or partitions we sometimes have trouble monitoring the other disks >> since one is already sending an alert. >> >> Example: >> Server1 has 3 monitored partitions of a disk: >> / >> /srv/important/data >> /srv/database >> >> with the same limits on all three: 80% -> yellow alert; 90% -> red alert >> Then if /srv/important/data reaches 82% the client wants us to notify >> them and they will free up space. This normaly takes around 3 - 5 >> working days. But they also wants us to monitor /srv/database. And say >> that 1 day after /srv/important/data gets filled, /srv/database >> reaches 84%. That will not trigger a new alert in the non-green status >> view which is what we monitor. >> >> The question/request is then as this: Is there a way to get the client >> to report each disk/partition as a separate alert, so we can disable >> the alert for one disk while receiving alerts for the other >> disks/partions. To use the example I want to be able to temporarily >> set /srv/important/data in disabled mode while still getting alerts >> from /srv/database >> >> I know this could be solved by writing my own script for the client, >> but that was disapproved of from management as they want as few custom >> scripts to maintain as possible (we already have dozens of custom >> scripts). >> >> All help and feedback is appreciated, thanks. >> >> Kind regards >> Calle Lejdbrandt >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon >> > -- Med vänliga hälsningar Aiquen Eldar ---Blessed be by the darkness---

2 1