Hi,
we have Nagios xi version 5.5.8 after upgrading the Nagios to last version we noticed these error from solaris 11 host that appear contentiously
the version on NRPE is 2.14
Dec 5 08:10:00 db1a-rcd nrpe[29654]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:14:58 db1a-rcd nrpe[18826]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:14:58 db1a-rcd nrpe[18826]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:19:56 db1a-rcd nrpe[11440]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:19:56 db1a-rcd nrpe[11440]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:24:54 db1a-rcd nrpe[29638]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:24:54 db1a-rcd nrpe[29638]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:29:54 db1a-rcd nrpe[19581]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:29:54 db1a-rcd nrpe[19581]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:34:51 db1a-rcd nrpe[8198]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:34:51 db1a-rcd nrpe[8198]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:39:49 db1a-rcd nrpe[28216]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:39:49 db1a-rcd nrpe[28216]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:44:46 db1a-rcd nrpe[18172]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:44:46 db1a-rcd nrpe[18172]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:49:45 db1a-rcd nrpe[7907]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:49:45 db1a-rcd nrpe[7907]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:54:44 db1a-rcd nrpe[28263]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:54:44 db1a-rcd nrpe[28263]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 08:59:43 db1a-rcd nrpe[17948]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 08:59:43 db1a-rcd nrpe[17948]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 09:04:41 db1a-rcd nrpe[12460]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 09:04:41 db1a-rcd nrpe[12460]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 09:09:39 db1a-rcd nrpe[6181]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 09:09:39 db1a-rcd nrpe[6181]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 09:14:36 db1a-rcd nrpe[29726]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 09:14:36 db1a-rcd nrpe[29726]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 09:19:35 db1a-rcd nrpe[27099]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 09:19:35 db1a-rcd nrpe[27099]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Dec 5 09:24:34 db1a-rcd nrpe[29440]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Dec 5 09:24:34 db1a-rcd nrpe[29440]: [ID 900267 daemon.error] Client request was invalid, bailing out...
please send us the solve this problem
Thanks
daemon error
-
bashar.abed
- Posts: 153
- Joined: Tue Oct 11, 2016 1:34 am
- Location: Ramallah West Bank Palestine
- Contact:
-
bolson
Re: daemon error
Hello bashar.abed,
The current version of Nagios XI ships with check_nrpe version 3. This version is backward compatible to 2.14 of nrpe. However, the check_nrpe command needs to include the -2 flag to appropriately modify the packet being sent by XI. Let us know if this resolves your issue.
Thank you for visiting the Nagios Support Forum!
The current version of Nagios XI ships with check_nrpe version 3. This version is backward compatible to 2.14 of nrpe. However, the check_nrpe command needs to include the -2 flag to appropriately modify the packet being sent by XI. Let us know if this resolves your issue.
Thank you for visiting the Nagios Support Forum!
-
bashar.abed
- Posts: 153
- Joined: Tue Oct 11, 2016 1:34 am
- Location: Ramallah West Bank Palestine
- Contact:
Re: daemon error
Hi,
Thanks for your response
this message from service side solaris 11 not from Nagios ,so how can put the suitable settinsg from remote site server not nagios server
Thanks
Thanks for your response
this message from service side solaris 11 not from Nagios ,so how can put the suitable settinsg from remote site server not nagios server
Thanks
Re: daemon error
The check_nrpe is an active check, initiated from the Nagios server, therefore you would need to modify your check there. Just add "-2" to your command as @bolson suggested.
Example:
Example:
/usr/local/nagios/libexec/check_nrpe -2 -H <ip address> -c <command> -a '<args>'
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
bashar.abed
- Posts: 153
- Joined: Tue Oct 11, 2016 1:34 am
- Location: Ramallah West Bank Palestine
- Contact:
Re: daemon error
Hi,
Thanks for your response ,
I applied the command on Nagios System as below
[[email protected] ~]$ /usr/local/nagios/libexec/check_nrpe -2 -H 10.x.x.81 -t 180 -c check_load -a '-w 60,60,60 -c 70,70,70'
OK - load average: 2.62, 2.41, 2.34|load1=2.625;60.000;70.000;0; load5=2.410;60.000;70.000;0; load15=2.344;60.000;70.000;0;
the same error still appear on remote server "linux"
Jan 8 10:58:32 ex-rdb1 nrpe[6578]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Jan 8 11:02:24 ex-rdb1 nrpe[10551]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Jan 8 11:02:24 ex-rdb1 nrpe[10551]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Jan 8 11:02:53 ex-rdb1 nrpe[10935]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Jan 8 11:02:53 ex-rdb1 nrpe[10935]: [ID 900267 daemon.error] Client request was invalid, bailing out...
so please your help
Thanks
Thanks for your response ,
I applied the command on Nagios System as below
[[email protected] ~]$ /usr/local/nagios/libexec/check_nrpe -2 -H 10.x.x.81 -t 180 -c check_load -a '-w 60,60,60 -c 70,70,70'
OK - load average: 2.62, 2.41, 2.34|load1=2.625;60.000;70.000;0; load5=2.410;60.000;70.000;0; load15=2.344;60.000;70.000;0;
the same error still appear on remote server "linux"
Jan 8 10:58:32 ex-rdb1 nrpe[6578]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Jan 8 11:02:24 ex-rdb1 nrpe[10551]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Jan 8 11:02:24 ex-rdb1 nrpe[10551]: [ID 900267 daemon.error] Client request was invalid, bailing out...
Jan 8 11:02:53 ex-rdb1 nrpe[10935]: [ID 321439 daemon.error] Error: Request packet type/version was invalid!
Jan 8 11:02:53 ex-rdb1 nrpe[10935]: [ID 900267 daemon.error] Client request was invalid, bailing out...
so please your help
Thanks
-
npolovenko
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: daemon error
@bashar.abed, I see you ran one individual command with version 2 packets, but have you actually changed the general command in the Core Configurations Manager? Go to the Core Configurations Manager in the Web Interface, click on the commands menu in the left column, search for the check_nrpe command and change it:
Then Apply Configuration.$USER1$/check_nrpe -2 -H $HOSTADDRESS$ -t 30 -c $ARG1$ $ARG2$
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
bashar.abed
- Posts: 153
- Joined: Tue Oct 11, 2016 1:34 am
- Location: Ramallah West Bank Palestine
- Contact:
Re: daemon error
Many thanks
the problem is solved now
Thanks
the problem is solved now
Thanks
-
npolovenko
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: daemon error
@bashar.abed, Great! I will be closing this thread as resolved.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.