OK, I didn't wait long enough for the service to update, sorry.
Changing the check_command definition to check_nrpe_1arg with the $HOSTADDRESS$
argument worked.
It appears that the NRPE manual is incorrect on this. The examples it gives
have just check_nrpe for argument-less commands on the remote server. That just
consumed 3 hours or so, so quite painful.
Sort of a bug in the documentation. How does one file a bug report on nagios? I
couldn't find it at sourceforge or on www.nagios.org. I'm also happy to modify
the source for the document if added as a developer on the sourceforge project
(but the join link wasn't clear either).
thanks,
Peter
On May 2, 2012, at 4:34 PM, Peter N. Steinmetz wrote:
> I also just tried changing the service definition to
>
> # NRPE load check
> define service {
> use generic-service
> host_name rm16
> service_description nrpe-load
> check_command check_nrpe_1arg!check_load!$HOSTADDRESS$
> }
>
> but the same complaint is showing up in the server output for this service,
> which seems a bit odd given then the command should now be check_nrpe_1arg
> rather than check_nrpe.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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
