I do indeed; just double-checked.

• Chris

-----Original Message----- From: Dennis Riley [mailto:driley at malone.edu] Sent: Thursday, October 20, 2016 1:37 PM To: Seip, Christopher (HPN SIS team) <chris.seip at hpe.com>; xymon at xymon.com Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris, You do have your entries above the DEFAULT entry so that you match your entry first, right? Dennis

-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher (HPN SIS team) Sent: Thursday, October 20, 2016 4:03 PM To: xymon at xymon.com Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't gotten per-host filesystem thresholds to work for that host yet. In /etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert. I've played with a few different syntaxes, wildcards, and other config files. This looks to me like the right way to do it... Feels like I'm overlooking something really basic here. Thanks,

• Chris [Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big Brother years ago.]

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

Seip, Christopher (HPN SIS team) wrote:

An update:

This was an apt-managed package named "xymon" (4.3.25) for Ubuntu.

I just compiled and installed Xymon 4.3.27; it exhibits the same behavior, so this strongly looks like I'm doing something wrong in the xymon configs.

Thanks,

• Chris

Root-# egrep -v '^#' /usr/local/xymon/server/etc/analysis.cfg

HOST=fqdn.of.my.monitored.host DISK /disk/data 96 98

DEFAULT

Ignore some usually uninteresting tmpfs mounts.

DISK /dev IGNORE DISK /dev/shm IGNORE DISK /lib/init/rw IGNORE DISK /run IGNORE

These are the built-in defaults. You should only modify these

lines, not add new ones (no PROC, DISK, LOG ... lines).

UP 1h LOAD 5.0 10.0 INODE * 70 90 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97

Root-#

-----Original Message----- From: Seip, Christopher (HPN SIS team) Sent: Thursday, October 20, 2016 2:04 PM To: 'Dennis Riley' <driley at malone.edu>; xymon at xymon.com Subject: RE: [Xymon] Configure per-host filesystem threshold

I do indeed; just double-checked.

• Chris

-----Original Message----- From: Dennis Riley [mailto:driley at malone.edu] Sent: Thursday, October 20, 2016 1:37 PM To: Seip, Christopher (HPN SIS team) <chris.seip at hpe.com>; xymon at xymon.com Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris, You do have your entries above the DEFAULT entry so that you match your entry first, right? Dennis

-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher (HPN SIS team) Sent: Thursday, October 20, 2016 4:03 PM To: xymon at xymon.com Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't gotten per-host filesystem thresholds to work for that host yet. In /etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert. I've played with a few different syntaxes, wildcards, and other config files. This looks to me like the right way to do it... Feels like I'm overlooking something really basic here. Thanks,

• Chris [Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big Brother years ago.]

What is in hosts.cfg? Is it 'fqdn.of.my.monitored.host' or is it just 'host'? Try

HOST=%host DISK /disk/data 96 98

-- Andy

On Fri, October 21, 2016 6:00 am, Mike Burger wrote:

On 2016-10-21 1:59 am, Andy Smith wrote:

...

Seip, Christopher (HPN SIS team) wrote:

...

An update:

This was an apt-managed package named "xymon" (4.3.25) for Ubuntu.

I just compiled and installed Xymon 4.3.27; it exhibits the same behavior, so this strongly looks like I'm doing something wrong in the xymon configs.

Thanks,

• Chris

Root-# egrep -v '^#' /usr/local/xymon/server/etc/analysis.cfg

HOST=fqdn.of.my.monitored.host DISK /disk/data 96 98

DEFAULT

Ignore some usually uninteresting tmpfs mounts.

DISK /dev IGNORE DISK /dev/shm IGNORE DISK /lib/init/rw IGNORE DISK /run IGNORE

These are the built-in defaults. You should only modify these

lines, not add new ones (no PROC, DISK, LOG ... lines).

UP 1h LOAD 5.0 10.0 INODE * 70 90 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97

Root-#

-----Original Message----- From: Seip, Christopher (HPN SIS team) Sent: Thursday, October 20, 2016 2:04 PM To: 'Dennis Riley' <driley at malone.edu>; xymon at xymon.com Subject: RE: [Xymon] Configure per-host filesystem threshold

I do indeed; just double-checked.

• Chris

-----Original Message----- From: Dennis Riley [mailto:driley at malone.edu] Sent: Thursday, October 20, 2016 1:37 PM To: Seip, Christopher (HPN SIS team) <chris.seip at hpe.com>; xymon at xymon.com Subject: RE: [Xymon] Configure per-host filesystem threshold

Hi Chris, You do have your entries above the DEFAULT entry so that you match your entry first, right? Dennis

-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Seip, Christopher (HPN SIS team) Sent: Thursday, October 20, 2016 4:03 PM To: xymon at xymon.com Subject: [Xymon] Configure per-host filesystem threshold

I'm new to Xymon, have set up my first client monitoring config, and haven't gotten per-host filesystem thresholds to work for that host yet. In /etc/xymon/analysis.cfg, I've got these lines:

HOST=my.hosts.fqdn DISK /disk/data 96 98

But my 95% filesystem-full condition continues to come up as a red alert. I've played with a few different syntaxes, wildcards, and other config files. This looks to me like the right way to do it... Feels like I'm overlooking something really basic here. Thanks,

• Chris [Running Xymon 4.3.25 on Ubuntu 16.04.1. New to Xymon; used to use Big Brother years ago.]

What is in hosts.cfg? Is it 'fqdn.of.my.monitored.host' or is it just 'host'? Try

HOST=%host DISK /disk/data 96 98

In addition to the question from Andy, did you remember to add a host specific wildcard DISK monitor?

I ran into a similar situation, back when I first started out and was told that once you've added any host specific DISK monitors, they override all DEFAULT disk monitor settings. As a result, you have to follow them up with a host specific wildcard entry, a la:

DISK   /disk/data 96 98
DISK   * 90 95

Also: Can you confirm that your client is running in the default server/centrally-configured mode -- that is, without the "--local" option. That can sometimes be a trip-up for people coming directly from BB. In that mode, the localclient.cfg file on the client is used for evaluation and processing via analysis.cfg never happens.

It's also helpful when debugging thresholds to validate through xymond_client that it's doing what you're thinking it's doing. You can have it dump its (processed) config by running:

xymoncmd xymond_client --dump-config | grep DISK

HTH, -jc

Mike Burger [mailto:mburger at bubbanfriends.org] wrote:

In addition to the question from Andy, did you remember to add a host specific wildcard DISK monitor?

I ran into a similar situation, back when I first started out and was told that once you've added any host specific DISK monitors, they override all DEFAULT disk monitor settings. As a result, you have to follow them up with a host specific wildcard entry, a la:

 DISK   /disk/data 96 98
 DISK   * 90 95

Thank you very much! That's new to me.

Duly added.

--Chris--