[Date Prev] [Date Next] | [Thread Prev] [Thread Next] | [Date Index] [Thread Index] |
[nocol-users] Hostmon/Noclogd repeating
|
Hi, I recently had a problem where hostmon and noclog seemed to get a little cranky. I was wondering if anyone has seen this? We had a site go "Error" on disk space for a volume. We normally would get 1 page via : ## ## SENDER LEVEL LOGFILE or PIPEFILE ## * error |/usr/home/nocol/bin/beep.error * warning |/usr/home/nocol/bin/beep.warning For some reason after installing 4.2.1, we received 6, one of which I also was suprised to get. I received 4 which said we were AT limit. Then I got one, AT ERROR LEVEL, that said it was 1 % less than the limit, but still warning level. The final one said I was at limit again before I stopped the nonsense. When my script is invoked, I get a log, and the log said : Warning - Mon Nov 16 20:36:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === Error - Mon Nov 16 20:36:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === But then ............. Warning - Mon Nov 16 20:51:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === Error - Mon Nov 16 20:51:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down And.................... Warning - Mon Nov 16 21:06:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === Error - Mon Nov 16 21:06:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down More..................... Warning - Mon Nov 16 21:16:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === Error - Mon Nov 16 21:16:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === Even more.................. Warning - Mon Nov 16 21:21:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 84 75 %full LEVEL Warning LOGLEVEL Error NOCOP down === Error - Mon Nov 16 21:21:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 84 75 %full LEVEL Warning LOGLEVEL Error NOCOP down === Yet more.................... Warning - Mon Nov 16 21:31:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === Error - Mon Nov 16 21:31:00 1998 [hostmon]: SITE e3000b.amkingdo /local11 VAR DFspace_%used 85 85 %full LEVEL Error LOGLEVEL Error NOCOP down === At no time, however, did it go "UP"! Any ideas why it didn't notice that it was in a down state and stop generating the errors, or why when it was set as : DFspace_%used e3000b.amkingdom.com 75 85 95 /local11$ I got an Error warning when it went to 84? Thanks, Tuc/TTSG |