Xymon Mailing List Archive search

Hostbased override values hobbit-clients.cfg

4 messages in this thread

list Netz-haut - Stephan Seitz · Mon, 14 Feb 2011 12:55:06 +0100 ·
Hi there,

I've got one problem with the hobbit-clients.cfg

At the top of this file, defaults are defined:

DEFAULT
	LOAD 3.0 7.0
	DISK * 86 92
	[... and others ...]

Below there are single hosts defined (mostly PROC checking), the defaults for LOAD and DISK were fine for all monitored Hosts over the last years(!! ;) ), but now, I want to monitor bigger storage spaces, where a notify level of 86% means 5 or so TB free, which is much too early ... , so I've added the following:

HOST=thisbiggerstorage.fqdn.tld
	DISK /data 95 98

But, this value is never used, the /data Mountpoints warnlevel stays at 86%

For other Hosts, I've tried the very same with the LOAD keyword, because these hosts utilize a lot of cores and can go upto 16 without any problem. But the very same: the new value is never getting uses. 3.0 / 7.0 from the DEFAULT section stays...

Restarting the hobbit server processes don't show up any effect.

Could someone please shed some light on what am I doing wrong?

Thanks!
	Stephan


Mit freundlichen Gruessen

--
Stephan Seitz
Senior System Administrator

   netz-haut GmbH
   multimediale kommunikation

   Zweierweg 22
   97074 Würzburg

   Telefon: 0931 2876247
   Telefax: 0931 2876248

   Web: www.netz-haut.de
   Amtsgericht Würzburg - HRB 10764
   Geschäftsführer: Michael Daut, Kai Neugebauer
list Henrik Størner · Mon, 14 Feb 2011 12:48:09 +0000 (UTC) ·
quoted from Netz-haut - Stephan Seitz
In <user-bfb43387ccd4@xymon.invalid> "netz-haut - stephan seitz" <user-8e07784d84e8@xymon.invalid> writes:
I've got one problem with the hobbit-clients.cfg
At the top of this file, defaults are defined:
DEFAULT
LOAD 3.0 7.0
DISK * 86 92
[... and others ...]
Below there are single hosts defined (mostly PROC checking)

That's wrong. DEFAULT settings MUST go last, anything else should
be placed above it.

It even says so in the file:

# The special DEFAULT section can modify the built-in defaults - this must
# be placed at the end of the file.


Regards,
Henrik
list Ralph Mitchell · Mon, 14 Feb 2011 08:20:40 -0500 ·
On Mon, Feb 14, 2011 at 6:55 AM, netz-haut - stephan seitz <
quoted from Netz-haut - Stephan Seitz
user-8e07784d84e8@xymon.invalid> wrote:
Hi there,

I've got one problem with the hobbit-clients.cfg

At the top of this file, defaults are defined:

DEFAULT
       LOAD 3.0 7.0
       DISK * 86 92
       [... and others ...]

Below there are single hosts defined (mostly PROC checking), the defaults
for LOAD and DISK were fine for all monitored Hosts over the last years(!!
;) ), but now, I want to monitor bigger storage spaces, where a notify level
of 86% means 5 or so TB free, which is much too early ... , so I've added
the following:

HOST=thisbiggerstorage.fqdn.tld
       DISK /data 95 98

But, this value is never used, the /data Mountpoints warnlevel stays at 86%

For other Hosts, I've tried the very same with the LOAD keyword, because
these hosts utilize a lot of cores and can go upto 16 without any problem.
But the very same: the new value is never getting uses. 3.0 / 7.0 from the
DEFAULT section stays...

Restarting the hobbit server processes don't show up any effect.

Could someone please shed some light on what am I doing wrong?
Man page for hobbit-clients.cfg says:

"The entire file is evaluated from the top to the bottom, and the first
match found is used.  So you should put specific settings first, and the
generic ones last."


 Just move the default (i.e. "generic") setting to the bottom of the file
and you should be all good.

Ralph Mitchell
list Netz-haut - Stephan Seitz · Mon, 14 Feb 2011 17:34:56 +0100 ·
	Henrik,

thank you! Sometimes it's worth reading the man pages... shame on me ...

Also to Ralph Mitchell, who offered the very same answer.

Cheers,
	Stephan
quoted from Henrik Størner

At the top of this file, defaults are defined:
DEFAULT
LOAD 3.0 7.0
DISK * 86 92
[... and others ...]
Below there are single hosts defined (mostly PROC checking)

That's wrong. DEFAULT settings MUST go last, anything else should
be placed above it.

It even says so in the file:

# The special DEFAULT section can modify the built-in defaults - this
must
# be placed at the end of the file.