beanfield wrote: > > So if you're basing the disk status off of something like logwatch....it > could be incorrectly reporting that the disk is full. Can you provide the > following output from a server that you know has the issue where it filled > the disk before zenoss alerted? > > > > df -h > > df > > snmpwalk -v2c -c COMMUNITY_STRING HOSTNAME 1.3.6.1.2.1.25.2.3 > > > Be sure and replace "COMMUNITY_STRING" and "HOSTNAME" appropriately.
I'm not at work for some time, but I'll try to connect to the zenoss server and see what the snmpwalk outputs. The server borked with mysql in the frontline trying to write to the disk. So I cleaned up some logs and then we where up to speed again. -- Regards Folke -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22527#22527 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
