From: Ben C. <Be...@cl...> - 2004-10-07 08:11:42
|
Clif, This is a bug in the plugin. Which I though had been fixed. The numbers shown are not the same unit. The value is 'disk free MB' and the warn/crit are 'disk used MB'. These cannot be directly compared and therefore return the wrong state. I have been told by one of plugin developers that there is a version of this plugin which has been fixed. Can you try downloading the latest snapshot and see if this is correct? Regards, Ben. Clif wrote: > When doing <./check_disk -l -w 10% -c 5%> > DISK OK - free space: / 31 MB (12%); /boot 90 MB (74%); /disk1 658 MB > (90%); /dev/shm 503 MB (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); > /var 321 MB (32%);| /=30MB;225;237;0;250 /boot=90MB;108;114;0;121 > /disk1=657MB;659;696;0;733 /dev/shm=503MB;452;477;0;503 > /tmp=450MB;443;468;0;493 /usr=1728MB;3627;3828;0;4030 > /var=321MB;909;960;0;1011 > > The plugin and Nagios correctly see that all is good (DISK OK), no disks > have 10% or less free. However, PerfParse shows /dev/shm and /tmp to be > at Critical and Warning?! > > Any ideas? > > cjs > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > |