Re: [Perfparse-users] Perfparse incorrectly reporting State when using check_disk

[Julien T. <jul...@ly...>]

Clif a =E9crit :

> 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=20
> (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); /var 321 MB (32%);|=20
> /=3D30MB;225;237;0;250 /boot=3D90MB;108;114;0;121=20
> /disk1=3D657MB;659;696;0;733 /dev/shm=3D503MB;452;477;0;503=20
> /tmp=3D450MB;443;468;0;493 /usr=3D1728MB;3627;3828;0;4030=20
> /var=3D321MB;909;960;0;1011
>=20
> The plugin and Nagios correctly see that all is good (DISK OK), no=20
> disks have 10% or less free.  However, PerfParse shows /dev/shm and=20
> /tmp to be at Critical and Warning?!
>=20
> Any ideas?
yes, i've seen it. it seems to me, perfparse check only if we are above
a limit and not under (or something like that). i've seen this strange
effect on some other plugins but doesn't have time to investigate more
for now.

Regards

		Julien