NSClient++-Win32-20070911-2123.zip - connection refused

[axel.werner@…]

after my problems with the official 0.2.7 and the "out of bound" error i now tried the latest build which was "NSClient++-Win32-20070911-2123.zip" recently.

i stoped the service, copied the whole content over my old NSCLIENT dir, modified configuration as required and restartet it.

result was that the nagios cannot access the agent. it reports "connection refused" while the agent itself (nsclient) does not report anything and does not write log neither.

the config i used is based on my old one that worked well with the official 0.2.7 version. so i guess its not the config since neither the new included one or the my old one will work with the latest client agent. only the older agent version will work.

[mickem]

if you copy the nsc.ini over to the "new" version it should work transparently, and there should not be any major changes (but I have refactored the INI-files to allow inclusions, and that might be broken) I shall check, a bit more only tested with NRPE myself.

[axel.werner@…]

negative! while the latest client agent wont work with my "working" ini, it starts to work right after i replaced the latest client (nightly build) with the "official" 0.2.7 version from sf.net . so i assume its in the code somewhere.

[axel.werner@…]

the NSClient++-Win32-20071006-1243 meanwhile works with my "working" ini file. so im trying out this version now fighting the "out of bounds" messages.

[axel.werner@…]

Latest report about "the NSClient++-Win32-20071006-1243":

since the NSClient++-Win32-20071006-1243 all sporadicly appearing "out of bound" messages disapeared! however sometimes some server reporting "no data received". i guess this happens when they are at high utilisation or HD activity (nightly backup usualy). but this is rare and is no big pain.

So THANKS FER FIXING! Great work!

[mickem]

oki, I shall see if I can dig up anything on the out on the "no data received", if it is load related it ought to be reproducible I hope :)

[mickem]

Added option (to [NRPE] and [NSClient]) to change the default timeout when reading data on the sockets. Try setting/increasing this if you still have problems (also upped the default value to 30 seconds from 10).

Try this is the "next" nightly and let me know how things are.

MickeM

[mickem]

the option is called socket_timeout (BTW) :)