Nagios Support Forum

Nagios XI 2012R2.9
RHEL 6.5
Client OS: Windows XP SP1, SP2 & SP3
Agent: NSClient NSCP-0.4.1.102-Win32

Have any of you encountered the following problem

2014-06-03 04:37:08: e:D:\source\nscp\trunk\include\socket/server.hpp:212: Socket ERROR: The semaphore timeout period has expired
The NSClient responds in port 5666 but is essentially dead when the following error happens.
Once the agent is restarted, the issues goes away.

Thanks

We have always considered 0.4.1 unstable... that said, it looks like there is a discussion on the topic here
http://www.nsclient.org/nscp/discussion/topic/1215

scottwilkerson wrote:We have always considered 0.4.1 unstable... that said, it looks like there is a discussion on the topic here
http://www.nsclient.org/nscp/discussion/topic/1215

So which version would you consider stable?

rajasegar wrote:

scottwilkerson wrote:We have always considered 0.4.1 unstable... that said, it looks like there is a discussion on the topic here
http://www.nsclient.org/nscp/discussion/topic/1215

So which version would you consider stable?

0.3.9 I believe.

BanditBBS wrote:

rajasegar wrote:

scottwilkerson wrote:We have always considered 0.4.1 unstable... that said, it looks like there is a discussion on the topic here
http://www.nsclient.org/nscp/discussion/topic/1215

So which version would you consider stable?

0.3.9 I believe.

Hmm ..This is 3 years old and does not support Windows 2012.

I would honestly check with the nsclient people on this one, unfortunately you almost need to use 4.x versions with it, which is why I suggest you bring this up on their support tracker. You could also try using NCPA, though it does not support performance counters at this time.

slansing wrote:I would honestly check with the nsclient people on this one, unfortunately you almost need to use 4.x versions with it, which is why I suggest you bring this up on their support tracker. You could also try using NCPA, though it does not support performance counters at this time.

Ok. Noted. Thanks.

Yeah it seems it's more of a networking timeout within the windows server itself, possibly an issue with port conflicts. If you get a chance, and they have anything that can help, let us know!