I'm having problem with NRPE parameters while testing a new Nagios
installation.
Header Node is running RHEL AS4 U6, and Nagios v3.2.0
Client is running RHEL AS4 U4, and NRPE v2.12 (compiled with command
arguments, and with dont_blame_nrpe=1)
Standard hardcoded nrpe disk checks work fine, for example;
Service definition on Header Node -
check_nrpe!check_home
Relates to the following in nrpe.cfg on the Client -
command[check_home]=/usr/local/nagios/libexec/check_disk -w 20% -c
10% -p /home
and returns -
DISK OK - free space: /home 1878 MB (98% inode=99%);|
/home=34MB;1612;1813;0;2015
Using variables, I can get the correct results from the command line;
Service definition on Header Node -
check_nrpe!check_adisk!20%!10%!/opt
Relates to the following in nrpe.cfg on the Client -
command[check_adisk]=/usr/local/nagios/libexec/check_disk -w
$ARG1$ -c $ARG2$ -p $ARG3$
and I can enter this on the Header Node -
#../../libexec/check_nrpe -H <client> -c check_adisk -a 20 10 /opt
DISK OK - free space: /opt 432 MB (45% inode=97%);|
/opt=524MB;987;997;0;1007
However, this does not work within Nagios GUI, all the parameters passed
are blank. I see this in syslog on the Client -
Added command[check_adisk]=/usr/local/nagios/libexec/check_disk-w
$ARG1$ -c $ARG2$ -p $ARG3$
Handling the connection...
Host is asking for command \'check_adisk\' to be run...
>>>>>Running command: /usr/local/nagios/libexec/check_disk -w -c
-p
Command completed with return code 3 and output: Unknown argument
Usage: check_disk -w limit -c limit [-W limit] [-K limit] {-p path | -x
device} [-C] [-E] [-e] [-g group ] [-k] [-l] [-M] [-m] [-R path ] [-r path
] [-t timeout] [-u unit] [-v] [-X type]
Return Code: 3, Output: Unknown argument Usage: check_disk -w
limit -c limit [-W limit] [-K limit] {-p path | -x device} [-C] [-E] [-e]
[-g group ] [-k] [-l] [-M] [-m] [-R path ] [-r path ] [-t timeout] [-u
unit] [-v] [-X type]
I'm conscious that I'm probably doing something very trivial wrong, but
can't get my head around why this should work on the command line, and not
via the GUI.
Any help much appreciated.
Regards
Nigel
Nigel Leach
Grid Engineer | Front Office Risk Systems | BNP Paribas
___________________________________________________________
This communication is confidential, may be privileged and is meant only for the
intended recipient. If you are not the intended recipient, please notify the
sender by reply and delete the message from your system. Any unauthorised
dissemination, distribution or copying hereof is prohibited.
BNP Paribas Trust Corporation UK Limited, BNP Paribas UK Limited, BNP Paribas
Commodity Futures Limited, BNP Paribas Asset Management UK Limited and
Investment Fund Services Limited are authorised and regulated by the Financial
Services Authority.
BNP Paribas London Branch and BNP Paribas Wealth Management London Branch are
authorised by the CECEI and supervised by the Commission Bancaire.
BNP Paribas London Branch is authorised and subject to limited regulation by
the Financial Services Authority. Details about the extent of our authorisation
and regulation by the Financial Services Authority are available from us on
request. BNP Paribas is also a member of the London Stock Exchange.
BNP Paribas Wealth Management London Branch is subject to limited regulation by
the Financial Services Authority. Details about the extent of our
authorisation and regulation by the Financial Services Authority are available
from us on request.
BNP Paribas Securities Services London Branch is authorised by the CECEI and
supervised by the AMF, and subject to limited regulation by the Financial
Services Authority. Details on the extent of our regulation by the Financial
Services Authority are available from us on request. BNP Paribas Securities
Services is also a member of the London Stock Exchange.
BNP Paribas Trust Corporation UK Limited is registered in England and Wales
(registered no. 4042668) at registered office 55 Moorgate, London EC2R 6PA.
BNP Paribas UK Limited is registered in England and Wales (registered no.
1488108) at registered office 10 Harewood Avenue, London NW1 6AA.
BNP Paribas Commodity Futures Limited is registered in England and Wales
(registered no. 2391477) at registered office 10 Harewood Avenue, London NW1
6AA.
BNP Paribas Asset Management UK Limited is registered in England and Wales
(registered no. 2474627) at registered office 10 Harewood Avenue, London NW1
6AA.
Investment Fund Services Limited is registered in England and Wales (registered
no. 6110770) at registered office 55 Moorgate, London EC2R 6PA.
BNP Paribas London Branch is registered in England and Wales (registered no.
FC13447) at registered office 10 Harewood Avenue, London NW1 6AA.
BNP Paribas Wealth Management London Branch is registered in England and Wales
(registered no. FC023926) at registered office 10 Harewood Avenue, London NW1
6AA.
BNP Paribas Securities Services London Branch is registered in England and
Wales (registered no. BR006393) at registered office 55 Moorgate, London, EC2R
6PA.
BNP Paribas Lease Group Plc is registered in England and Wales (registered no.
2341989) at registered office Northern Cross, Basing View, Basingstoke,
Hampshire RG21 4HL.
____________________________________________________________
BNP Paribas is proud to support the Royal Academy of Arts in their presentation
of ‘Wild Thing: Epstein, Gaudier-Brzeska, Gill’ in the Sackler Wing of
Galleries from 24 October 2009 to 24 January 2010.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null