Page 1 of 1

Is there a way to alert against the inode counts?

Posted: Mon Apr 29, 2019 9:23 am
by dlukinski
Hello XI Support

Is there a way to alert against the inode counts?

NRPE plugins tracks them, but how to create an alert?
- unless there is another plugin?

Thank you

Re: Is there a way to alert against the inode counts?

Posted: Mon Apr 29, 2019 9:33 am
by scottwilkerson
Using check_disk you can use the following arguments to alert if inodes are less that the % specified

Code: Select all

 -W, --iwarning=PERCENT%
    Exit with WARNING status if less than PERCENT of inode space is free
 -K, --icritical=PERCENT%
    Exit with CRITICAL status if less than PERCENT of inode space is free

Re: Is there a way to alert against the inode counts?

Posted: Thu May 09, 2019 12:47 pm
by dlukinski
scottwilkerson wrote:Using check_disk you can use the following arguments to alert if inodes are less that the % specified

Code: Select all

 -W, --iwarning=PERCENT%
    Exit with WARNING status if less than PERCENT of inode space is free
 -K, --icritical=PERCENT%
    Exit with CRITICAL status if less than PERCENT of inode space is free

Hello Scott

No luck with that. How the Arguments and the command should look like?

Thank you

Re: Is there a way to alert against the inode counts?

Posted: Thu May 09, 2019 1:00 pm
by scottwilkerson
Example

Code: Select all

/usr/local/nagios/libexec/check_disk --iwarning=20 --icritical=10 -p /

Re: Is there a way to alert against the inode counts?

Posted: Fri May 10, 2019 8:10 am
by dlukinski
scottwilkerson wrote:Example

Code: Select all

/usr/local/nagios/libexec/check_disk --iwarning=20 --icritical=10 -p /

Does not work for us:

[[email protected] ~]$ /usr/local/nagios/libexec/check_nrpe -H 10.102.35.26 -t 30 -c check_disk --iwarning=20 --icritical=10 -p
NRPE Plugin for Nagios
Version: 3.2.1

Copyright (c) 2009-2017 Nagios Enterprises
1999-2008 Ethan Galstad ([email protected])

Last Modified: 2017-09-01

License: GPL v2 with exemptions (-l for more info)

SSL/TLS Available: OpenSSL 0.9.6 or higher required

Usage: check_nrpe -H <host> [-2] [-4] [-6] [-n] [-u] [-V] [-l] [-d <dhopt>]
[-P <size>] [-S <ssl version>] [-L <cipherlist>] [-C <clientcert>]
[-K <key>] [-A <ca-certificate>] [-s <logopts>] [-b <bindaddr>]
[-f <cfg-file>] [-p <port>] [-t <interval>:<state>] [-g <log-file>]
[-c <command>] [-E] [-a <arglist...>]

Options:
-H, --host=HOST The address of the host running the NRPE daemon
-2, --v2-packets-only Only use version 2 packets, not version 3
-4, --ipv4 Bind to ipv4 only
-6, --ipv6 Bind to ipv6 only
-n, --no-ssl Do no use SSL
-u, --unknown-timeout Make connection problems return UNKNOWN instead of CRITICAL
-V, --version Print version info and quit
-l, --license Show license
-E, --stderr-to-stdout Redirect stderr to stdout
-d, --use-dh=DHOPT Anonymous Diffie Hellman use:
0 Don't use Anonymous Diffie Hellman
(This will be the default in a future release.)
1 Allow Anonymous Diffie Hellman (default)
2 Force Anonymous Diffie Hellman
-P, --payload-size=SIZE Specify non-default payload size for NSClient++
-S, --ssl-version=VERSION The SSL/TLS version to use. Can be any one of:
SSLv2 SSL v2 only
SSLv2+ SSL v2 or above
SSLv3 SSL v3 only
SSLv3+ SSL v3 or above
TLSv1 TLS v1 only
TLSv1+ TLS v1 or above (DEFAULT)
TLSv1.1 TLS v1.1 only
TLSv1.1+ TLS v1.1 or above
TLSv1.2 TLS v1.2 only
TLSv1.2+ TLS v1.2 or above
-L, --cipher-list=LIST The list of SSL ciphers to use (currently defaults
to "ALL:!MD5:@STRENGTH". THIS WILL change in a future release.)
-C, --client-cert=FILE The client certificate to use for PKI
-K, --key-file=FILE The private key to use with the client certificate
-A, --ca-cert-file=FILE The CA certificate to use for PKI
-s, --ssl-logging=OPTIONS SSL Logging Options
-b, --bind=IPADDR Local address to bind to
-f, --config-file=FILE Configuration file to use
-g, --log-file=FILE Log file to write to
-p, --port=PORT The port on which the daemon is running (default=5666)
-c, --command=COMMAND The name of the command that the remote daemon should run
-a, --args=LIST Optional arguments that should be passed to the command,
separated by a space. If provided, this must be the last
option supplied on the command line.

NEW TIMEOUT SYNTAX
-t, --timeout=INTERVAL:STATE
INTERVAL Number of seconds before connection times out (default=10)
STATE Check state to exit with in the event of a timeout (default=CRITICAL)
Timeout STATE must be a valid state name (case-insensitive) or integer:
(OK, WARNING, CRITICAL, UNKNOWN) or integer (0-3)

Note:
This plugin requires that you have the NRPE daemon running on the remote host.
You must also have configured the daemon to associate a specific plugin command
with the [command] option you are specifying here. Upon receipt of the
[command] argument, the NRPE daemon will run the appropriate plugin command and
send the plugin output and return code back to *this* plugin. This allows you
to execute plugins on remote hosts and 'fake' the results to make Nagios think
the plugin is being run locally.

Re: Is there a way to alert against the inode counts?

Posted: Fri May 10, 2019 8:32 am
by scottwilkerson
In NRPE the command would look line this

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 10.102.35.26 -t 30 -c check_disk -a '--iwarning=20 --icritical=10 -p /' 

Re: Is there a way to alert against the inode counts?

Posted: Fri May 17, 2019 10:02 am
by dlukinski
scottwilkerson wrote:In NRPE the command would look line this

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 10.102.35.26 -t 30 -c check_disk -a '--iwarning=20 --icritical=10 -p /' 
Thank you, this worked perfectly !

Re: Is there a way to alert against the inode counts?

Posted: Fri May 17, 2019 11:58 am
by scottwilkerson
dlukinski wrote:
scottwilkerson wrote:In NRPE the command would look line this

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 10.102.35.26 -t 30 -c check_disk -a '--iwarning=20 --icritical=10 -p /' 
Thank you, this worked perfectly !
Great!

Locking thread