- Xymon - Xymon mailman web

Ignoring file system when two "/" (root partitions) are reported
by waa-hobbitml＠revpol.com 14 Sep '11

14 Sep '11

Hi Larry... Thanks for the reply (moving your reply to the list) Sure I could, but this looks like something where I will not be the only one affected, so I figured I'd report it and see if there was either 1. A correct way in analisys.cfg that I was just missing somehow or 2. Have it 'fixed' in the default (eg: in the release version) rather than me making a one-off fix to some internal variables Having said that, it looks like your solution will probably immediately fix my problem and I will take a look at it as soon as I have a few minutes late today or tomorrow. Thanks -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/ On 09/13/11 14:40, Larry Barber wrote: > Could you insert a "grep -v rootfs" in the 'df' section of > xymonclient-linus.sh? > > echo "[df]" > EXCLUDES=`cat /proc/filesystems | grep nodev | awk '{print $2}' | xargs echo > | sed -e 's! ! -x !g'` > df -Pl -x iso9660 -x $EXCLUDES | grep -v rootfs | sed -e '/^[^ ][^ > ]*$/{ > N > s/[ ]*\n[ ]*/ / > }' > > Thanks, > Larry Barber > > On Tue, Sep 13, 2011 at 12:45 PM, Bill Arlofski <waa-hobbitml at revpol.com>wrote: > >> On a Gentoo Linux system, after a recent baselayout update to openrc 2.x >> (at >> least I believe that to be the culprit) xymon clients are now reporting >> back >> TWO "/" (root) filesystems, and xymon v4.3.4 is reporting and graphing >> them >> both like so: >> >> >> Tue Sep 13 13:16:58 EDT 2011 - Filesystems NOT ok >> >> (yellow) / (92% used) has reached the WARNING level (90%) >> (yellow) / (92% used) has reached the WARNING level (90%) >> >> Filesystem 1024-blocks Used Available Capacity Mounted on >> rootfs 96571704 88758608 7813096 92% / >> /dev/root 96571704 88758608 7813096 92% / >> >> In analyze.cfg I have tried to ignore rootfs and then the regular >> expression >> versions just in case xymon matched the whole line reported, and not just >> the >> info in the "Mounted on" column: >> >> HOST=hostname.domain.tld >> DISK rootfs IGNORE >> >> or >> >> HOST=hostname.domain.tld >> DISK %rootfs IGNORE >> >> or >> >> HOST=hostname.domain.tld >> DISK %^rootfs IGNORE >> >> or >> >> HOST=hostname.domain.tld >> DISK /dev/root IGNORE >> >> >> but these of course will not work since the docs for analyze.cfg say that >> the >> DISK test works on the MOUNT POINT, not the device, or partition. >> >> Is there any way to ignore ONE of the two disk reports that are essentially >> the same exact thing, only reported in two different formats? >> >> >> >> Also, as a side note/suggestion, the docs might be a bit >> ambiguous/confusing >> with regards to "filesystem" and "mount point", using them >> semi-interchangeably which can be needlessly confusing: >> >> # DISK filesystem warnlevel paniclevel >> # DISK filesystem IGNORE >> # If the utilization of "filesystem" is reported to exceed "warnlevel" >> >> Then filesystem is described as... >> # "filesystem" is the mount-point where the filesystem is mounted, e.g. >> >> >> Perhaps that could be more clear if the test was defined like so: >> >> # DISK mountpoint warnlevel paniclevel >> # DISK mountpoint IGNORE >> >> Then, there would be no need for the "filesystem is the mount point..." >> line >> since it would be self-evident >> >> Thanks! >> >> -- >> Bill Arlofski >> Reverse Polarity, LLC >> http://www.revpol.com/ >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon >> >

1 1

AIX df command problem
by sholmes42＠mac.com 13 Sep '11

13 Sep '11

I am having a problem similar to one recently posted, but this is on an AIX host and is caused (I think) by a problem in the way xymon does df on AIX. The xymon version is 4.2.3 and the AIX OS version is 3.5 (I think, I'm a Solaris Admin). Anyway, I can find no way to force the df on AIX to use POSIX formatting AND to report only local file systems. Even if I could, I don't think I can override what xymon uses for df since the comments in the hobbitclient.cfg file say that the envariable definition is only there for compatibility and it is not used. The problem is that an NFS mount file system line in the df output is being parsed wrong and the number in the usage column is being used for the percent used (Available) so that is a huge number. Not only that, again similar to the previous problem, the file system name is being picked up as the contents of the last 3 fields in the output line, i.e. it is not /mnt/tsmupdates (which is what it should be) but "3020485 50% /tsm/updates", which, of course, prevents me from effectively ignoring that file system. I've tried using DISK %.*/mnt/.* IGNORE and that doesn't work. Does anyone have any suggestions? We have a big red page where we shouldn't have. Thanks, Steve -- The test of a democracy is not the magnificence of buildings or the speed of automobiles or the efficiency of air transportation, but rather the care given to the welfare of all the people. -Helen Adams Keller, lecturer and author (1880-1968) Truth never damages a cause that is just. -Mohandas Karamchand Gandhi (1869-1948)

3 4

Ignoring file system when two "/" (root partitions) are reported
by waa-hobbitml＠revpol.com 13 Sep '11

13 Sep '11

On a Gentoo Linux system, after a recent baselayout update to openrc 2.x (at least I believe that to be the culprit) xymon clients are now reporting back TWO "/" (root) filesystems, and xymon v4.3.4 is reporting and graphing them both like so: Tue Sep 13 13:16:58 EDT 2011 - Filesystems NOT ok (yellow) / (92% used) has reached the WARNING level (90%) (yellow) / (92% used) has reached the WARNING level (90%) Filesystem 1024-blocks Used Available Capacity Mounted on rootfs 96571704 88758608 7813096 92% / /dev/root 96571704 88758608 7813096 92% / In analyze.cfg I have tried to ignore rootfs and then the regular expression versions just in case xymon matched the whole line reported, and not just the info in the "Mounted on" column: HOST=hostname.domain.tld DISK rootfs IGNORE or HOST=hostname.domain.tld DISK %rootfs IGNORE or HOST=hostname.domain.tld DISK %^rootfs IGNORE or HOST=hostname.domain.tld DISK /dev/root IGNORE but these of course will not work since the docs for analyze.cfg say that the DISK test works on the MOUNT POINT, not the device, or partition. Is there any way to ignore ONE of the two disk reports that are essentially the same exact thing, only reported in two different formats? Also, as a side note/suggestion, the docs might be a bit ambiguous/confusing with regards to "filesystem" and "mount point", using them semi-interchangeably which can be needlessly confusing: # DISK filesystem warnlevel paniclevel # DISK filesystem IGNORE # If the utilization of "filesystem" is reported to exceed "warnlevel" Then filesystem is described as... # "filesystem" is the mount-point where the filesystem is mounted, e.g. Perhaps that could be more clear if the test was defined like so: # DISK mountpoint warnlevel paniclevel # DISK mountpoint IGNORE Then, there would be no need for the "filesystem is the mount point..." line since it would be self-evident Thanks! -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/

1 0

xymon iostat causing problems on loaded box, how to mitigate?
by betsy.schwartz＠gmail.com 13 Sep '11

13 Sep '11

We're seeing problems with xymon iostat hanging on heavily loaded, massively large database servers. These boxes are on Oracle RAC clusters with EMC storage devices attached. iostat -x shows 16572 lines. When the box starts to have problems for *other* reasons, all of the iostat commands start hanging or taking forever, further bogging the system down. And making xymon look really bad ... I'm wondering - what does xymon do with all this information? How much of it can I turn off without confusing the server? (part of a PS from 12:13, showing some iostats that have been running for over half an hour) # ps -ef|grep iostat xymon 102 98 2 11:55:47 ? 7:18 iostat -dxsrP 300 2 xymon 16934 16931 0 12:10:00 ? 0:04 iostat -c 300 2 xymon 16911 1 0 11:51:02 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 xymon 566 1 0 12:05:38 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 xymon 16931 1 0 12:10:00 ? 0:00 sh -c iostat -c 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatcpu.db6.bo3. xymon 16932 1 0 12:10:00 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 xymon 15575 15566 2 12:00:47 ? 5:53 iostat -dxsrP 300 2 xymon 15566 1 0 12:00:47 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 xymon 1349 1344 2 11:45:55 ? 9:34 iostat -dxsrP 300 2 xymon 17276 17271 2 11:40:55 ? 10:55 iostat -dxsrP 300 2 xymon 16935 16932 2 12:10:00 ? 2:57 iostat -dxsrP 300 2 xymon 17271 1 0 11:40:55 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 xymon 1344 1 0 11:45:55 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 xymon 572 566 2 12:05:38 ? 5:13 iostat -dxsrP 300 2 xymon 16914 16911 2 11:51:02 ? 8:24 iostat -dxsrP 300 2 xymon 98 1 0 11:55:47 ? 0:00 sh -c iostat -dxsrP 300 2 1>/export/home/xymon/client/tmp/hobbit_iostatdisk.db6 <etc>

2 2

Odd named errors, perhaps related to Xymon or Devmon?
by sberkley＠mcclatchyinteractive.com 13 Sep '11

13 Sep '11

We've been getting an average of 40+/day of these messages from the caching nameserver process on one of our Xymon/Devmon servers: named[N]: sockmgr 0xN: maximum number of FD events (64) received This server is running bind-9.3.6-16.P1 (old, I know, but it's the latest for the distro we are using). I was wondering if anyone else out there was seeing the same errors? I'm making an assumption that Xymon/Devmon (or one of our ext scripts) might be inducing this condition, since this server doesn't have any other processes on it that would be doing a large amount of DNS lookups. This server has over 600 entries in hosts.cfg and 92 entries in the Devmon hosts.db. I have tried reproducing the problem by making a large amount of DNS lookups as simultaneously as possible, but with no luck. The xymonnet status only lists 42 failed DNS lookups out of 797 calls to dnsresolve. Any suggestions on how to find out what specific process is causing named to make periodic high demands for sockets? -- S i m e o n B e r k l e y Systems Engineer McClatchy Interactive phone: 919-861-1244 fax: 919-861-1300 mobile: 919-302-3063 e-mail: sberkley at mcclatchyinteractive.com AIM: sberkleymi www.mcclatchyinteractive.com

2 1

TS - NTP testing
by d.tom.schmitt＠L-3com.com 13 Sep '11

13 Sep '11

Is there a way to select the NTP variance information from each server? I know there is a line at the top of the CPU icon for Linux that says: "System clock is 0 seconds off" I cannot find an equivalent in the Windows client info - we use the BB client currently but I have the BBwin client on my PC and do not see any NTP information. We need a report that will show how our NTP services are doing. We have the BBwin client running on most of our Windows servers. 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 eFax (470) 201-6644 \\\\||//// \ ~ ~ / | @ @ | --oOo---(_)---oOo-- Have A Nice Day !

2 1

migrating from i386 to x86_64
by martin.flemming＠desy.de 12 Sep '11

12 Sep '11

Hi ! Got somebody already a script for migrating all rrd's from i386 to x86_64 ? I want to migrate in the near future to SL6 and we will provide only x86_64 as platform anymore ... Thanks & Cheers, Martin

2 2

bbd srvs oddity and <procs> config
by jewel.brueggeman-makda＠washburn.edu 12 Sep '11

12 Sep '11

I have two separate issues. I am running Xymon 4.3.5 #1 On my server one of my hosts (Lawprint) it is trying to monitor the bbd service but I have not specified it anywhere. I checked both the hosts.cfg and my client BBwin.cfg and there in no reference to bbd. Here is what is in my hosts.cfg file: 127.0.0.1 Xymon #bbd http://Xymon 555.55.55.5 Lawprint #conn cpu msg #2 How do I configure the BBwin.cfg file to monitor particular processes? I have the following in my BBWin.cfg file but they are not working. It is green but it says "No process to check". Other changes I have made do so I know the two are able to communicate. ... <procs> PROC pc-app.exe PROC pc-server.exe </procs> ...

1 1

Process monitoring on Xymon 4.3.4
by paul.jacobs2＠produban.co.uk 12 Sep '11

12 Sep '11

Hi, I am setting up Xymon to monitor process running on a host but when I modify the analysis.cfg file its taking ages to change colour on the main page? PROC "conf/log4j/log4j_AggregationCommonIn.xml" 6 6 So we I can change this from 6 to 7 it should go RED but its taking ages. How do I increase the monitoring period as I need to know quicker when processes have failed? I did the change well over 5 minutes ago and my page is still green. Any help greatly appreciated Paul Emails aren't always secure, and they may be intercepted or changed after they've been sent. Produban doesn't accept liability if this happens. If you think someone may have interfered with this email, please get in touch with the sender another way. This message and any documents attached to it do not create or change any contract unless otherwise specifically stated. Any views or opinions contained in this message are solely those of the author, and do not necessarily represent those of Produban, unless otherwise specifically stated and the sender is authorised to do so. Produban doesn't accept responsibility for damage caused by any viruses contained in this email or its attachments. Emails may be monitored. If you've received this email by mistake, please let the sender know at once that it's gone to the wrong person and then destroy it without copying, using, or telling anyone about its contents. Produban Servicios Informaticos Generales, S.L. (UK Branch). Registered office: Shenley Wood House, Chalkdell Drive, Shenley Wood, Milton Keynes MK5 6LA. Branch registration number BR 008486. Ref:[PDB#014]

1 0

Solved - Cannot load file configuration
by jewel.brueggeman-makda＠washburn.edu 09 Sep '11

09 Sep '11

It's working now. I restarted the xymon.sh service. Not sure what happened. When I click to view a report on my xymon installation I get "Cannot load host configuration". I am not sure what I messed up. I can see the main page just fine it's just when I click on a smiley face. In my apache logs I see 'Could not connect to Xymon deamon at 127.0.0.1:1984 (Connection refused); 'xymonboard fields=hostname,testname,disabletime,dismsg' All I did was reboot the server. --

2 6