Hello
I have recently upgraded to 5.7.1 after a pending state issue found in 5.7.0. I now have a new issue that gives the following message.
CHECK_NRPE: Invalid packet version received from server.
I do get the result of the query at the end of the message.
I have included the latest profile file from our system.
Regards
Terrence
CHECK_NRPE issue after 5.7.1 upgrade
CHECK_NRPE issue after 5.7.1 upgrade
You do not have the required permissions to view the files attached to this post.
Re: CHECK_NRPE issue after 5.7.1 upgrade
sounds like your using non-ssl communcations?
we see the same.
our default appears to be to use ssl but since we migrated to a new centos VM, our migrated/imported data started to get ssl errors.
manually running '/usr/local/nagios/libexec/check_nrpe -H HOSTNAME -n' (-n for no-ssl) shows your error even though it does return info.
for us, this is the nail in the coffin for nrpe. deployment & management of nsclient is a pain so i'm currently looking at moving to NCPA.
sorry i cant help, but just letting you know you're not alone!
we see the same.
our default appears to be to use ssl but since we migrated to a new centos VM, our migrated/imported data started to get ssl errors.
manually running '/usr/local/nagios/libexec/check_nrpe -H HOSTNAME -n' (-n for no-ssl) shows your error even though it does return info.
for us, this is the nail in the coffin for nrpe. deployment & management of nsclient is a pain so i'm currently looking at moving to NCPA.
sorry i cant help, but just letting you know you're not alone!
Re: CHECK_NRPE issue after 5.7.1 upgrade
We had to add -2 to the check to resolve this.
Here is a quote from support:
Here is a quote from support:
Regarding, the issue with NRPE checks, please add a -3, for version 3 packets, argument to your check command, and let me know if the error is cleared.
Reference:
https://support.nagios.com/kb/article/n ... s-786.html
Re: CHECK_NRPE issue after 5.7.1 upgrade
Thanks the help,@nickap.
@veehexx, please test with the -2 and -3 options and let us know your results.
@veehexx, please test with the -2 and -3 options and let us know your results.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: CHECK_NRPE issue after 5.7.1 upgrade
Hello
I have added -2 to my NRPE request on the command and it now works.
Thanks nickap for the solution.
Regards
Terrence
I have added -2 to my NRPE request on the command and it now works.
Thanks nickap for the solution.
Regards
Terrence
Re: CHECK_NRPE issue after 5.7.1 upgrade
thanks to ssax in my 'sucessful migration - mysql issues' thread, our issue was with the DH key length. default seems to be 512, but need 2048 or higher.
since generating 2048 & deploying to clients, both -2 and -3 forced version work.
Re: CHECK_NRPE issue after 5.7.1 upgrade
I am glad your issue has been resolved! Let us know if it is OK to close this topic. Thank you!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: CHECK_NRPE issue after 5.7.1 upgrade
Yes, please close this ticket.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: CHECK_NRPE issue after 5.7.1 upgrade
Greattpwebb wrote:Yes, please close this ticket.
Locking thread