Problem with starting RPC services after mmrecov to the new server

Question

Maybe somebody knows what can be problem here: - I've installed NW software (7.6.3) to a new server (same as old one - in terms of OS, name, IP, hosts files) - runs fine, - recovered bootstrap from old server using mmrecov - after renaming res.R to res and restarting services - it fails to start all daemons - as it can bee seen in rpcinfo output: C:\Program Files\Legato
sr\bin>rpcinfo -p NW_SERVER program vers proto   port 100000    2   tcp   7938 100000    2   udp   7938 390436    1   tcp   8379 390435    1   tcp   8307 390113    1   tcp   7937 (from netstat I can see these are all nsrexecd demons) - only after I disable / enable network interface, it starts rest of the services: C:\Program Files\Legato
sr\bin>rpcinfo -p NW_SERVER program vers proto   port 100000    2   tcp   7938 100000    2   udp   7938 390436    1   tcp   8379 390435    1   tcp   8307 390113    1   tcp   7937 390103    2   tcp   9602 [nsrd.exe] 390109    2   tcp   9602 [nsrd.exe] 390110    1   tcp   9602 [nsrd.exe 390120    1   tcp   9602 [nsrd.exe] 390109    2   udp   8932 [nsrd.exe] 390107    5   tcp   8318 [nsrmmdbd.exe] 390107    6   tcp   8318 [nsrmmdbd.exe] 390105    5   tcp   8013 [nsrindexd.exe] 390105    6   tcp   8013 [nsrindexd.exe] 390433    1   tcp   7984 [nsrjobd.exe] But after service restart - it fails to start RPC services again. Odd thing is that nsrd process starts as the services are started, but attaches to UDP port only and needs net interface enable/disable to attach to TCP. So question is - what setting gets recovered along with old server configuration that keeps NW services from starting properly?

Bartuus · Accepted Answer

Hi

In my case the root problem was misconfiguration of DNS on the new       server, to which NW was restored.
It looks like Networker tends do resolve all server names it has       configured in its bowels, and when DNS is failing - a lot of       timeouts need to pass before all services start. Fresh instalation       is far less prone to lack of DNS server, this is why problem rises       after renaming res.R.
Swithing lan off and on deletes these timeouts and shortens start       up procedure - so possibly this is not your case.

B

mridul_singh · Answer

Did you get any messages/error in daemon.log. I would suggest starting the networker services in debug mode and see where it is complaining, if it is.

Thierry101 · Answer

FW?

0p98nFjndg12186 · Answer

I have te similar problem. NW 8.0.0.5 on W2K8 R2 server. Same hostname, same ip, same OS. Everything works fine before i rename the res.R folder. After it i have the same problem with the connection and rpc services. Tried that disable/enable lan trick but it didnt help.

ble1 · Answer

Try to run in in debug.  This means: - stop NW services - open at 3 CMD windows - in 1st wiindows run $NSRHOME\bin
srxecd -D9 > nsrexecd.D9 2>&1 - check log file to see how it works and if there are any messages about something being wrong - in 2nd window run $NSRHOME\bin
srd -D9 > nsrd.D9 2>&1 - check log file to see how it works and if there are any messages about something being wrong - at this pont there should be something wrong already if you can reproduce the issue

Thierry101 · Answer

have you tried rename the /tmp? stop the services, rename and restart

0p98nFjndg12186 · Answer

You were right. I cleared the DNS servers from the windows ip configuration and the NW started without any problem and its working fine. Thx.

RFreund1 · Answer

The NW server in fact checks the name resolution/connectivy to all clients and SNs when it starts. For test purposes i restored the mm and the res directory to a VM test system and restarted the daemons. On this small VM, it took about 30mins for the NW server to 'become available' just because it has about 500 clients which he could not reach.

The behavior is fine - i appreciate it in general.

The only complaint is that the program could be a bit more chatty at this point. You do not see anything unless you look at the daemon.raw file or start the server manually (not as a service, with added verbosity).

NetWorker

Problem with starting RPC services after mmrecov to the new server

Was this post helpful?