[NSClient++] Topic #104 - bind failed: 10038

Topic #104 - bind failed: 10038

mike m — Mon, 10 Mar 2008 02:19:19 GMT

I assumed my nsc.ini file had bad syntax. After a few hours of trial and error I can't get past this error. Full error - e \Socket.h(635) bind failed: 10038: An operation was attempted on something that is not a socket. and the config file (only uncommented lines) -

[modules]
FileLogger.dll
CheckSystem.dll
CheckDisk.dll
NSClientListener.dll
CheckEventLog.dll
CheckHelpers.dll
[Settings]
password=manageme
allowed_hosts=192.168.1.0/24
use_file=1
[log]
date_mask=%Y-%m-%d %H:%M:%S
[NSClient]
allowed_hosts=192.168.1.5
port=12489
bind_to_address=192.168.1.3
socket_timeout=30
[NRPE]
[Check System]
CPUBufferSize=1h
CheckResolution=100
[External Script]
[External Scripts]
[External Alias]

Any suggestions are welcome.

Reply #275 to topic #104 - bind failed: 10038

mike m — Mon, 10 Mar 2008 23:50:32 GMT

I should have known better, when in doubt with windows reboot. I did have to comment the bind to line but it works fine after a reboot. THANK YOU mickem!

FYI - i may be reading this backward but i thought zero (0) means use the ini file, in testing it looks like one (1) means use the ini file. ;# USE THIS FILE ; Use the INI file as opposed to the registry if this is 0 and the use_reg in the registry is set to 1 ; the registry will be used instead.

Fantastic work on this. Please don't stop!

Reply #274 to topic #104 - bind failed: 10038

mickem — Mon, 10 Mar 2008 21:00:23 GMT

does it work without the bind_to_address line?

The error indicates you are trying to use something that is not a "socket"....

MickeM

Reply #273 to topic #104 - bind failed: 10038

mike m — Mon, 10 Mar 2008 02:22:28 GMT

running NSClient++ 0.3.1-RC3 on Vista home premium current patches, no obvious conflicts with the firewall and various nag/nuisance systems.