Re: nrpe errors when too many hosts

The error itself just means that Nagios can't find the plugin that you've
told it to use. Every time I've ever encountered this error it boils down
to something very simple; normally a typo or a mis-pasted file path.

When you added the hosts did you also add the service, or were you using a
service that has already been defined and used previously? Too, did you
make any changes to your check definitions at all?


On Thu, Jun 20, 2013 at 3:13 AM, Aleksandr Miroslav
<[email protected]>wrote:

> hi,
>
> We have nagios server that is working for long time.
>
> We note recently when we add new hosts, all NRPE checks fail with:
>
> Return code of 127 is out of bounds - plugin may be missing
>
> However, the plugin is there and we know it run fine from command line.
> Only when some new hosts added this happens.  When you take  new hosts
> out,  errors go away.
>
> We don't have too many hosts in our file, only about 250.
>
> This problem is identical to the one find here:
>
> http://readlist.com/lists/lists.sourceforge.net/nagios-users/5/29272.html
>
>
> Alex
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-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
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-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