Page 4 of 4
Re: CHECK_NRPE: Receive header underflow - only 0 bytes rece
Posted: Wed Nov 14, 2018 5:13 pm
by raydx
Ran with the up-dated nsclient ini file.
Re: CHECK_NRPE: Receive header underflow - only 0 bytes rece
Posted: Wed Nov 14, 2018 5:50 pm
by tgriep
When you ran the check_eventlog command on the Windows server in the nscp test window, how long did it take to run?
Re: CHECK_NRPE: Receive header underflow - only 0 bytes rece
Posted: Wed Nov 21, 2018 3:44 pm
by raydx
Now when I run check_eventlog in nscp, I'm not getting:
L cli OK: OK: No entries found
L cli Performance data: 'problem_count'=0;0;0
like I was before.
From nsclient log file:
2018-11-21 12:22:23: error:c:\source\master\include\socket/connection.hpp:139: Socket was unexpectedly closed trying to send data (possibly check your timeout settings)
Re: CHECK_NRPE: Receive header underflow - only 0 bytes rece
Posted: Mon Nov 26, 2018 9:32 am
by tgriep
Edit the nsclient.ini file on the Windows system and under this section
Change this
to
Save the change and restart the NSClient++ agent and see if the test passes.
If not, you will have to contact the author of the NSClient++ agent for more help at the following link.
http://www.nsclient.org/
Re: CHECK_NRPE: Receive header underflow - only 0 bytes rece
Posted: Mon Nov 26, 2018 12:53 pm
by raydx
Service still fails after editing nsclient.ini file per your instructions.
I will contact the author of the NSClient++ agent.
Re: CHECK_NRPE: Receive header underflow - only 0 bytes rece
Posted: Mon Nov 26, 2018 1:15 pm
by tgriep
OK, thanks. If the test fails on the Windows system, there is not much else we can do so the author may be able to help you out.
nsclient_14Nov.log