HI,
Thanks for answear.
Indeed, it doesn't seem to work correctly with this hobbit version:
HOST=*
PROC %(/usr/sbin/cron|crond).* 1 5 EXHOST=mrtg-wat,test-host
PROC %(/usr/sbin/cron|crond).* 1 30 HOST=mrtg-wat
PROC %(/usr/sbin/cron|crond).* 1 6 HOST=test-host
The results for test-host on PROC was:
&unknown %(/usr/sbin/cron|crond).* (found 6, req. between 1 and 5)
green %(/usr/sbin/cron|crond).* (found 6, req. between 1 and 30)
green %(/usr/sbin/cron|crond).* (found 6, req. between 1 and 6)
Other servers which are'nt in EXHOST have this behaviour:
green %(/usr/sbin/cron|crond).* (found 1, req. between 1 and 5)
green %(/usr/sbin/cron|crond).* (found 1, req. between 1 and 30)
green %(/usr/sbin/cron|crond).* (found 1, req. between 1 and 6)
As you suggested, i changed conf like this (list the hosts explicitly) :
HOST=*
PROC %(/usr/sbin/cron|crond).* 1 5 EXHOST=mrtg-wat,gie-s2if-front2
HOST=test-host
PROC %(/usr/sbin/cron|crond).* 1 6
HOST=mrtg-wat
PROC %(/usr/sbin/cron|crond).* 1 30
it seems to work but there is a strange behaviour for the global rule and
EXHOST:
test-host PROC show this:
&unknown %(/usr/sbin/cron|crond).* (found 6, req. between 1 and 5)
green %(/usr/sbin/cron|crond).* (found 6, req. between 1 and 6)
Others hosts are OK (only the global PROC).
Do you know what the "unknown" state means ? is it obstructing ?
Thanks
Nicolas
Le Jeu 20 juillet 2006 23:06, Henrik Stoerner a écrit :On Thu, Jul 20, 2006 at 04:02:14PM +0200, Nicolas wrote:
DEFAULT
UP 1h
LOAD 5.0 10.0
DISK * 90 95
MEMPHYS 100 101
MEMSWAP 60 80
MEMACT 95 97
PROC %(/usr/sbin/cron|crond).* 1 5
Putting PROC entries in the DEFAULT section is generally a bad idea,
unless you never - ever - want to have exceptions from the rule.
I'd suggest removing it from the default section, and using this
instead:
HOST=*
PROC %(/usr/sbin/cron|crond).* 1 5 EXHOST=mrtg-wat
PROC %(/usr/sbin/cron|crond).* 1 HOST=mrtg-wat
or some similar configuration.
Hobbit version: hobbit-4.1.2p1
Ouch, there's some problems with the config file parsing in the 4.1.2
releases. I'm not entirely sure the above will work in 4.1.2p1; you may
have to list the hosts explicitly for this. It's fixed in the 4.2 release
candidate currently being tested.
Regards,
Henrik