Page 1 of 1
(Return code of 255 is out of bounds)
Posted: Mon Aug 10, 2015 9:34 am
by lafargeuser
I am not able to monitor Linux server using NRPE, However, the same server being monitor by other Nagios XI. I get below error
(Return code of 255 is out of bounds)
I have two Nagios server & trying to monitor linux box with these two, with one i am able to monitor but other i didnt not. I have modified below file & entered Nagios servers separated by comma & restarted the service.
/etc/xined.d/nrpe
i
Re: (Return code of 255 is out of bounds)
Posted: Mon Aug 10, 2015 9:58 am
by jdalrymple
Are you sure you have 'check_nrpe' on your new server, and is it in the predetermined location that you've specified?
What happens if you run the check_nrpe from the command line?
Code: Select all
/path/to/your/check_nrpe -H <linux_IP>
Re: (Return code of 255 is out of bounds)
Posted: Tue Aug 11, 2015 1:16 am
by Box293
lafargeuser wrote: I have modified below file & entered Nagios servers separated by comma & restarted the service.
/etc/xined.d/nrpe
The file is:
/etc/xinetd.d/nrpe
And the only_from directive is a list of host address separated by a space (not comma).
Correct this and then restart the xinetd service.
Re: (Return code of 255 is out of bounds)
Posted: Tue Aug 11, 2015 7:17 am
by lafargeuser
Everthing looks fine. Modified xinetd.d/nrpe file & replaced existing Nagios server with New server, Strange but it worked for me.
Here, am I not able to monitor one server with multiple Nagios servers ?
Re: (Return code of 255 is out of bounds)
Posted: Tue Aug 11, 2015 7:55 am
by jdalrymple
Sorry I didn't spot this in your original post. only_from on xinetd.conf - no commas, just spaces.
Re: (Return code of 255 is out of bounds)
Posted: Wed Aug 12, 2015 1:29 am
by lafargeuser
No problem. It worked now. Thanks for brought to my notice. You may close this post.
Re: (Return code of 255 is out of bounds)
Posted: Wed Aug 12, 2015 9:37 am
by hsmith
lafargeuser wrote:No problem. It worked now. Thanks for brought to my notice. You may close this post.
Glad to hear that it worked.
Thanks for the update.