Grrrr... this is getting annoying... it goes critical every day or two,
too; still can't figure out what's generating it... (hence the blank
agent section)
This is an old Solaris host still running Perl 5.005.02... looks like
this could be a "disk" generating these? (though the "0 0" in there is a
bit weird - so I'm guessing there's two of these running around in the
system somewhere?)
Sun Mar 17 00:00:11 2002 []: DEVICE VAR 9 5 LEVEL Warning
LOGLEVEL Warning STATE down
Sun Mar 17 00:10:11 2002 []: DEVICE VAR 0 5 LEVEL Info
LOGLEVEL Warning STATE up
Sun Mar 17 03:10:10 2002 []: DEVICE VAR 50 50 LEVEL Warning
LOGLEVEL Warning STATE down
Sun Mar 17 03:20:11 2002 []: DEVICE VAR 40 50 LEVEL Info
LOGLEVEL Warning STATE up
Wed Mar 20 12:13:16 2002 []: DEVICE VAR 98 70 LEVEL Warning
LOGLEVEL Warning STATE down
Wed Mar 20 12:23:15 2002 []: DEVICE VAR 98 70 LEVEL Error
LOGLEVEL Error STATE down
Wed Mar 20 12:33:15 2002 []: DEVICE VAR 98 70 LEVEL Critical
LOGLEVEL Critical STATE down
Sat Mar 23 10:13:15 2002 []: DEVICE VAR 99 70 LEVEL Warning
LOGLEVEL Warning STATE down
Sat Mar 23 10:23:14 2002 []: DEVICE VAR 99 70 LEVEL Error
LOGLEVEL Error STATE down
Sat Mar 23 10:33:14 2002 []: DEVICE VAR 99 70 LEVEL Critical
LOGLEVEL Critical STATE down old
Wed Mar 20 12:33:15 2002 []: DEVICE VAR 98 70 LEVEL Critical
LOGLEVEL Critical STATE down
Sat Mar 23 10:33:14 2002 []: DEVICE VAR 99 70 LEVEL Critical
LOGLEVEL Critical STATE down old
Wed Mar 20 12:13:16 2002 []: DEVICE VAR 0 0 LEVEL Warning
LOGLEVEL Warning STATE down
Wed Mar 20 12:23:15 2002 []: DEVICE VAR 0 0 LEVEL Error
LOGLEVEL Error STATE down
Sat Mar 23 10:13:15 2002 []: DEVICE VAR 0 0 LEVEL Warning
LOGLEVEL Warning STATE down
Sat Mar 23 10:23:14 2002 []: DEVICE VAR 0 0 LEVEL Error
LOGLEVEL Error STATE down
Anyone else seeing stuff like this, by chance? Wonder if I just have a
variable name somewhere that's throwing off the parser...
Looking for "50" and "70" in the config files, I get...
etherload-confg:bw 30 50 70
hostmon-confg:FileTable * 50 70 90
hostmon-confg:CtxtSw * 50 150 999
hostmon-confg:CPUus * 50 60 70
hostmon-confg:CPUsy * 50 60 70
snmpmon-confg:RTR.ifInBW * 10 50 70 Serial.+
snmpmon-confg:RTR.ifInBW * 10 50 60
snmpmon-confg:RTR.ifOutBW * 10 50 70
snmpmon-confg:HOST.proctable_%used * 50 40 30
I guess this looks like it's probably a hostmon problem? Slight chance
of it being an snmpmon issue, though those thresholds are wrong, there.
If I had to guess, I'd almost hazard it being a hostmon issue for the
DFspace_%used where I have entries like:
/usr+host.domain.com host.domain.com 03/18 00:43 hostmon
DFspace_%used 93 90 %full 002 Error
Any ideas?
Russell
--
Russell M. Van Tassell
russell at loosenut com
In the force if Yoda's so strong, construct a sentence with words in
the proper order then why can't he?
|