Ticket #263 (closed defect: fixed)
Problem with check_nrpe from SLES 9.3
| Reported by: | christian.braeuning@… | Owned by: | MickeM |
|---|---|---|---|
| Priority: | 1 | Milestone: | 0.4.0 |
| Component: | NRPEListener | Version: | 0.3.5 |
| Severity: | Bugs | Keywords: | |
| Cc: |
Description
Hi,
while trying execute an check with check_nrpe from SLES 9.3 i get the message
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
In the server logs i see.
2008-12-09 15:26:25: error:.\NRPEListener.cpp:329: We got more then we wanted 1036, we only got: 1048
The same check execution from SLES10 works fine with the same NSClient. I`m using check_nrpe version 2.12. The only difference i see so far is the openssl version. On SLES 9.3 it is openssl-0.9.7d-15.35, on SLES10 it is openssl-0.9.8a-18.4. But i have the same behaviour if i try the check without ssl.
Change History
comment:1 Changed 3 years ago by mickem
- Milestone changed from 0.3.6 to 0.4.0
Sounds like a problem with check_nrpe? In this case it "sends" more data then we are expecting have you changed the binary in some way?
comment:2 Changed 3 years ago by christian.braeuning@…
- Status changed from new to closed
- Resolution set to fixed
Hi mickem,
yes you´re right. I have forgotten that I changed the MAX_PACKETBUFFER_LENGTH definition in the NRPE source. I switched it back to the default value 1024 and everything works fine.
Another solution would be to set the packet length in the nsc.ini to the same value. But with this I have to support two different nsclient versions while updating all nsclients.
Thanks for your help!
