[Nagiosplug-help] Error: Request contained command arguments, but argument option is not enabled!

[Grant Lowe]

Hi Philip,

First, thanks for the reply.  I appreciate the help.

Well, I changed my nrpe configuration around, so hopefully I don't need to enable command-line arguments via the "dont_blame_nrpe" directive now.  Please let me know if this sounds and looks good.

On the nagios server, I now get this error:

[root at nagios-test objects]# /usr/lib/nagios/plugins/check_nrpe -H 172.20.60.50 -n -c check_disk
NRPE: Unable to read output
[root at nagios-test objects]#

So it seems like the syntax is ok as the remote host is not complaining in syslog.

I know the command runs ok on the remote host as I get this:

myhost /usr2/glowe> /opt/csw/libexec/nagios-plugins/check_disk -w 20 -c 10
DISK CRITICAL - free space: / 1023 MB (52% inode=83%); /usr 917 MB (47% inode=85%); /var 1735 MB (43% inode=95%); /var/run 13530 MB (99% inode=99%); /tmp 13530 MB (99% inode=99%)
nyhost /usr2/glowe>

My nrpe.cfg file for check_disk looks like this:

command[check_disk]=/opt/csw/libexec/nagios-plugins/check_disk -w 20 -c 10

So what am I doing wrong, to get the "Unable to read output" in syslog?



----- Original Message ----
From: Philip Marcus <pmarcus at structuredcommons.com>
To: Grant Lowe <glowe at sbcglobal.net>
Cc: nagiosplug-help at lists.sourceforge.net
Sent: Saturday, October 4, 2008 8:15:21 PM
Subject: Re: [Nagiosplug-help] Error: Request contained command arguments, but argument option is not enabled!

Hey Grant,

By default, the nrpe daemon does not allow remote command line
arguments to be passed to it.

To enable this, you'll need to recompile it using something like
"./configure --enable-command-args".

If you've already done this, make sure the nrpe.cfg file has the option:

dont_blame_nrpe=1 instead of the default which is 0.  (restart the
nrpe after changing config options).

These details are documented in the SECURITY file packaged in the
nrpe.tar.gz. Their are security implications with enabling remote
command line arguments to be passed to nrpe.

Of course, you can bypass all this by setting static warning,
critical, and partition arguments in the nrpe.cfg file, and just
calling that command without arguments.

Hope this helps,

Philip




On Tue, Sep 30, 2008 at 11:21 AM, Grant Lowe <glowe at sbcglobal.net> wrote:
>  Hi all,
>
> I have a nagios 3.0.3 server running on RHEL 5.2.  The client is Solaris 8 running nrpe 2.10.
>
> I get this in the Solaris logs:
>
> Sep
> 30 10:36:08 myhost nrpe[7179]: [ID 396531 daemon.error] Error: Request
> contained command arguments, but argument option is not enabled!
> Sep 30 10:36:08 myhost nrpe[7179]: [ID 900267 daemon.error] Client request was invalid, bailing out...
>
> But if I run it locally, it comes back fine:
>
> myserver /tmp>  /opt/csw/libexec/nagios-plugins/check_disk -w 90 -c 95 /dev/dsk/c0t0d0s0
> DISK OK - free space: / 1023 MB (52% inode=83%);| /=923MB;1917;1912;0;2007
> myserver /tmp>
>
> Here's what I get from the server side:
>
> [root at nagios-test
> libexec]# /usr/lib/nagios/plugins/check_nrpe -H 172.20.60.50 -t 60 -n
> check_disk -a -w 90 -c 95 /dev/dsk/c0t0d0s0
> CHECK_NRPE: Received 0 bytes from daemon.  Check the remote server logs for error messages.
> [root at nagios-test libexec]#
>
> It's
> seems to me that it's a configuration error, but I'm not sure what to
> fix.  Please help and don't be too hard on me as I'm kind of new to
> this.  :-)
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>