[WARN && CRIT] check_disk

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
ceeper
Posts: 5
Joined: Wed Feb 13, 2013 9:06 am

[WARN && CRIT] check_disk

Post by ceeper »

Hello everybody,

One simple questions:

With this command:

/check_disk -M -w 20% -c 10% -E -p /
DISK CRITICAL - free space: /dev/sda1 5840 MB (10% inode=86%);| /dev/sda1=48902MB;46137;51904;0;57672

Are you agree with me if I write this for the perf data:

Current use: 48902MB
Warning level: 46137MB
Critical level: 51904MB
Scale 0 to 57672

Why is the disk critical??? The critical is by 51904MB and the current is 48902MB. There should be not a Warning??

Thanks in advance.

Best Regards
User avatar
gshergill
Posts: 231
Joined: Tue Aug 07, 2012 5:08 am

Re: [WARN && CRIT] check_disk

Post by gshergill »

Hi ceeper,

Code: Select all

(10% inode=86%)
So you have 10% left (critical value).
The 86% is the inode usage.

Run on the server:

Code: Select all

df -hi /
To view the inode usage.

Run:

Code: Select all

df -h /
To view the free space (this will correspond to 10%).

Kind Regards,

Gary Shergill
ceeper
Posts: 5
Joined: Wed Feb 13, 2013 9:06 am

Re: [WARN && CRIT] check_disk

Post by ceeper »

gshergill wrote:Hi ceeper,

Code: Select all

(10% inode=86%)
So you have 10% left (critical value).
The 86% is the inode usage.

Run on the server:

Code: Select all

df -hi /
To view the inode usage.

Run:

Code: Select all

df -h /
To view the free space (this will correspond to 10%).

Kind Regards,

Gary Shergill
Hi Gary,

Thanks for your repply.

Ok I understand, but The performance data say me that the critical is at 51904MB, and the current is 48902MB...

Why my graph show me a Warning?

Image

Thanks,

Best Regards,

C.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: [WARN && CRIT] check_disk

Post by slansing »

It is showing you a warning because your warning value is below where the actual amount of space left is. If it passes the threshold then it will trigger a warning.
ceeper
Posts: 5
Joined: Wed Feb 13, 2013 9:06 am

Re: [WARN && CRIT] check_disk

Post by ceeper »

slansing wrote:It is showing you a warning because your warning value is below where the actual amount of space left is. If it passes the threshold then it will trigger a warning.
Yes the graph say me the truth, I'm over the Warning threshold, I'm agree with this.

But the plugin output give me a CRITICAL.

DISK CRITICAL - free space: /dev/sda1 5840 MB (10% inode=86%);| /dev/sda1=48902MB;46137;51904;0;57672

Why this differencie?

Regards,

C.
User avatar
gshergill
Posts: 231
Joined: Tue Aug 07, 2012 5:08 am

Re: [WARN && CRIT] check_disk

Post by gshergill »

Hi creeper,

When you run the command:

Code: Select all

df -h /
Do you get the Use% as 90%?

Kind Regards,

Gary Shergill
ceeper
Posts: 5
Joined: Wed Feb 13, 2013 9:06 am

Re: [WARN && CRIT] check_disk

Post by ceeper »

gshergill wrote:Hi creeper,

When you run the command threshold

Code: Select all

df -h /
Do you get the Use% as 90%?

Kind Regards,

Gary Shergill
Hi,

Yes exactly, it's possible to adapt warning and critical threshold in the graph (perfs data) to acording with the reallity?

Regards.
User avatar
gshergill
Posts: 231
Joined: Tue Aug 07, 2012 5:08 am

Re: [WARN && CRIT] check_disk

Post by gshergill »

Hi creeper,

Sorry, I'm not sure about the graphs, I don't know what data they use, just wanted to confirm that the check_disk is correct on the command line (which it is).

Sorry can't be of more help.

Kind Regards,

Gary Shergill
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: [WARN && CRIT] check_disk

Post by slansing »

How large is the entire disk that you are monitoring? Are you asking how to change the graph so it shows the total size? And not the critical threshold?
ceeper
Posts: 5
Joined: Wed Feb 13, 2013 9:06 am

Re: [WARN && CRIT] check_disk

Post by ceeper »

slansing wrote:How large is the entire disk that you are monitoring? Are you asking how to change the graph so it shows the total size? And not the critical threshold?
I find out the problem, there are 5% of the space used by the root. And this 5% is not calculed by the performance data.

--> https://github.com/nagios-plugins/nagio ... ns/pull/22

Regards,
Locked