Nagios Graph not displaying correct values

[James Osbourn]

I have a weird situation where the Nagios Graph values are not the actual values for a filesystem

Eg I have a filesystem and if I run a df I get

$ df -h .
Filesystem            Size  Used Avail Use% Mounted on
filer01:/vol/data1    443G  400G   44G  91% /mnt/filer01_data1

If I run the Nagios check_disk command I get the correct values

# ../libexec/check_disk -w 10% -c 5% -p /usr/groups/sources
DISK WARNING - free space: /usr/groups/sources 44073 MB (9% inode=48%);| /usr/groups/sources=409354MB;408084;430755;0;453427

But when you look at the graph the figures are all wrong



Has anyone else seen this?  I was going to look at the usage to try and forecast usage but it will now be very hard.  I have just installed Nagios Graph based on the default installation and using the default check_disk plugin.

Thanks

James


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20111213/afaa9ce9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture (Device Independent Bitmap) 1.jpg
Type: image/jpeg
Size: 31748 bytes
Desc: Picture (Device Independent Bitmap) 1.jpg
URL: <https://www.monitoring-lists.org/archive/users/attachments/20111213/afaa9ce9/attachment.jpg>
-------------- next part --------------
------------------------------------------------------------------------------
Systems Optimization Self Assessment
Improve efficiency and utilization of IT resources. Drive out cost and 
improve service delivery. Take 5 minutes to use this Systems Optimization 
Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null