folke wrote:
>
> beanfield wrote:
> >
> > Again, that's all if I understand this correctly. :)
>
>
> The thing is that the disk is full before it sends out an alert.
> I have put that value to 98% ( [Embarassed] ) so when the small disks shows
> the wrong value things go bad :p
>
> Off course i can change the value for critical, but it would be better if
> the graphs where correct..
>
> Did you change anything in you graph template so that it showed the correct
> value?
>
> --
> Regards Folke
hmmm....when you say "the disk is full before it sends out an alert", how are
you finding out that the disk is full? Are you getting errors when you try and
write to the disk in your terminal...and more accurately are you getting errors
in /var/log/messages to the effect "no space left on device"?
The only reason I ask is because some utilities/scripts that watch disk space
actually just do a "df -h", which as pointed out before will incorrectly round
up and say the disk is full when it still may have some space available. For
instance, logwatch does this (at least on debian it does). I installed
logwatch and looked at the script that calculates free space
/usr/share/logwatch/scripts/services/zz-disk_space:
Code:
if ($OSname eq "Linux") {
$df_options = "-h -l -x tmpfs";
Can you provide the following output from a server that you know has this issue?
> 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.[/quote]
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=22460#22460
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
