socket errors with NetWorker 7.5.1 clients

Question

hello,

i have very strange problems with new NetWorker 7.5.1 build 269 clients. when i restart client it usually fails and there are following errors in client's daemon.raw file:

Failed to bind socket socket for nsrexecd service: %s 1 24 93 Only one usage of each socket address (protocol/network address/port) is normally permitted.

i receive this error almost with all clients. in windows, in linux, in hp-ux. and i even receive this error when client server is restarted. in most cases when server gets restarted NetWorker client won't start and there are these errors in logs. it starts to get very annoying already.

when i just restart daemon's then if i repeatedly try to start them they finally start. for example, in linux if i repeatedly run "/etc/init.d/networker start" command it finally succeeds. sometimes it fails 5-6 times before success. the same with windows and hp-ux.

have anybody seen similar issues with NetWorker clients? i suspect a bug because it happens with different machines.

regards,

kipz

ble1 · Answer

I currently use small number of 7.5.1 client (GA) on HPUX and Linux, but haven't see this problem.

NWadmin1 · Answer

I'm having the exact problem too. Did you solve your problem? Please let me know...

kipz1 · Answer

no, unfortunately my problem is still there. couple of days ago i did not manage to start NetWorker client on one Windows 2003 box at all. i had to restart whole server. after restart, NW client failed but then i manually managed to start it.

kaido

lpenarub · Answer

This is a known issue that has been fixed in NetWorker 7.5.2.

Sporadically after shutting down NetWorker daemons, some RPC ports such as 7937 are not getting released. This manifests when Networker daemons are stopped then immediately restarted. The workaround is simply to wait for a minute (or so) until the OS releases the bound ports before restarting Networker.

Hope this helps.

KateMcDonald · Answer

Has 7.5.2 been released to the general public yet? I have one server that I can't even get the client to start at all on due to this error.

NWadmin1 · Answer

Version 7.5.2 hasn't been released to the general public yet.

NWadmin1 · Answer

As per the SME, this is a BUG that will be fixed in version 7.5.2

kipz1 · Answer

for me it getting already very annoying. and sometimes waiting does not help. few times i had to restart server. does anybody know GA date of 7.5.2? kipz

dgreggs1 · Answer

Is there a release date announced for Networker 7.5.2? We are planning on deploying Windows 2008 R2 which isn't supported in the currently released versions of Networker. Thanks, Dana

masonb · Answer

Dana, Currently there is no firm GA date for the software but it is expected to be released in the next 4 weeks. Regards, Bill Mason

avocado1 · Answer

we just did a upgrade from 7.3.3 to 7.5.1 didn't work so we tried 7.5.2 still same issue nsrd ports files to authenticate the ports are not being release by the previous nsrd service.

don't know what to do??

ble1 · Answer

Well, if the problem is with stuck rpc ports, you can always cleanup RPC table using rpcinfo.

NetWorker

socket errors with NetWorker 7.5.1 clients

Was this post helpful?