Re: [Nagios-users] nrpe: incorrect command line arguments supplied
Denny Schierz wrote: > hi, > > Am Mittwoch, den 19.07.2006, 17:34 +0200 schrieb Denny Schierz: > > >>check_command check_nrpe!check_disk -w 20 -c 10 -p /dev/sda1 >>} > > > here was my error. I had to remove the arguments from the line. Now it > is working. I know that i can use args, if i compiled the option into > nrpe :-) The arguments get put into nrpe.conf on the remote host side, not on the Nagios check_nrpe side. Max - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] nrpe: incorrect command line arguments supplied
hi, Am Mittwoch, den 19.07.2006, 17:34 +0200 schrieb Denny Schierz: > check_command check_nrpe!check_disk -w 20 -c 10 -p /dev/sda1 > } here was my error. I had to remove the arguments from the line. Now it is working. I know that i can use args, if i compiled the option into nrpe :-) -- Sicherheit verständlich http://www.sides.de GnuPG Key http://pgpkeys.pca.dfn.de:11371/pks/lookup?op=get&search=0x2A5CE192AB7D3FE0 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] nrpe: incorrect command line arguments supplied
Denny Schierz wrote:
> hi,
>
> first: i have on all remote hosts the same nrpe version from plugin,
> daemon and with ssl.
>
> NRPE seems to be working, but something went wrong:
>
> Current Load UNKNOWN (No output returned from plugin)
> Root Partition UNKNOWN Incorrect command line arguments supplied
>
>
> my nagios minimal.cfg:
>
> ## space ##
>
>
> #mx02 space
>
> define service{
> use generic-service ; Name of service template to use
> host_name mx02
> service_description Root Partition
> is_volatile 0
> check_period24x7
> max_check_attempts 4
> normal_check_interval 5
> retry_check_interval1
> contact_groups admins
> notification_optionsw,u,c,r
> notification_interval 960
> notification_period 24x7
> check_command check_nrpe!check_disk -w 20 -c 10 -p /dev/sda1
> }
>
>
> ## load ##
>
> # MX02
>
> define service{
> use generic-service ; Name of service template to use
> host_name mx02
> service_description Current Load
> is_volatile 0
> check_period24x7
> max_check_attempts 4
> normal_check_interval 5
> retry_check_interval1
> contact_groups admins
> notification_optionsw,u,c,r
> notification_interval 960
> notification_period 24x7
> check_command check_nrpe!check_load -w 15,10,5 -c 30,25,20
> }
>
> my nrpe config:
>
>
> command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c
> 30,25,20
>
> command[check_disk1]=/usr/lib/nagios/plugins/check_disk -w 20 -c 10
> -p /dev/sda1
>
>
> The plugins are on both systems the same. What is my mistake?
>
Get rid of the arguments in your service containers:
check_command check_nrpe!check_load (get rid of -w 15,10,5 -c
)check_command check_nrpe!check_disk (get rid of -w 20 -c 10 -p /dev/sda1)
The arguments you passed will get plugged in on the remote NRPE host
that you are checking. Looks like your NRPE config is good. Try that.
Max
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
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
Re: [Nagios-users] nrpe: incorrect command line arguments supplied
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Denny Schierz
> Sent: Wednesday, July 19, 2006 8:35 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] nrpe: incorrect command line
> arguments supplied
>
> define service{
> use generic-service ; Name of service template to use
> host_name mx02
> service_description Current Load
> is_volatile 0
> check_period24x7
> max_check_attempts 4
> normal_check_interval 5
> retry_check_interval1
> contact_groups admins
> notification_optionsw,u,c,r
> notification_interval 960
> notification_period 24x7
> check_command check_nrpe!check_load -w 15,10,5 -c 30,25,20
> }
>
> my nrpe config:
>
>
> command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c
> 30,25,20
> The plugins are on both systems the same. What is my mistake?
You're specifying the same arguments twice. Take them out of the
service definition.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
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
