question to check_disk

Werner Flamme werner.flamme at ufz.de
Tue Mar 12 12:24:02 CET 2024


Am 2024-02-21 um 18:06 schrieb Astrid Kuhr:
> Hello!
> 
> I am using check_disk
> (check_disk v2.3.1 (monitoring-plugins 2.3.1))
> for some filesystems.
> 
> But for one filesystem of this, the perfdata
> has strong values inside.
> 
> As example:
> 
> df -h
> /dev/mapper/raid-home                  4,0T    3,4T  553G   87% /home
> /dev/mapper/raid-other                 197G    155G   41G   80% /other
> 
> /usr/lib/nagios/plugins/check_disk -w 12% -c 10%  --unit GB -p /home
> DISK OK - free space: /home 552 GB (13% inode=97%);|
> /home=3474GB;3547;3627;0;4031
> 
> /usr/lib/nagios/plugins/check_disk -w 12% -c 10%  --unit GB -p /other
> DISK OK - free space: /usr/local/cfx 40 GB (20% inode=88%);|
> /other=154GB;172;176;0;196
> 
> But if I look into NagiosGrid I will find this for /home:
> 
> Status Information:    DISK OK - free space: /home 1 GB (90% inode=99%):
> Performance Data:    /home=0GB;0;0;0;1
> 
> Which I do not understand, because it does not fit to the data, which
> the command at console has as output.
> 
> For the filesystem /other it is similar to command:
> 
> Status Information:    DISK OK - free space: /other 40 GB (20% inode=88%):
> Performance Data:    /other=154GB;166;176;0;196
> 
> Is it possible, that Nagios can not do with terrabyte disks?
> 
> Nagios is Nagios Core 4.4.7 from Suse Leap 15.5.
> 
> Thanx.
> 
> Regards, Astrid

Hello Astrid,

nagios does not know anything about the filesystem size. It just
executes a command, normally using a plugin, and uses the returned text
output and return values (aka "errorlevel").

Can it be that nagios executes a check_nrpe command that triggers
something other on the monitored host than you execute yourself
manually? I had this several times, because some plugins store their
default config in /etc/nrpe.d and thus nrpe commands may be defined
multiple times. You can never be sure which of the definitions are used.
So I have nrpe checking in /etc/nrpe.ufz.d instead of the standard
/etc/nrpe.d, which often gets infested when updates roll in ;)

You can execute "grep -rn check_disk /etc/nrpe.d/*" to check this. And
make sure that you change all commands in /etc/nrpe.cfg to comments.

HTH, Werner


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5918 bytes
Desc: Kryptografische S/MIME-Signatur
URL: <https://www.monitoring-plugins.org/archive/help/attachments/20240312/3a101bc4/attachment.bin>


More information about the Help mailing list