|
Re: [Networker] Cannot contact nsrexecd service on client, Service not available
2006-12-07 08:51:33
On Dec 7, 2006, at 5:18 AM — 12/7/06, Turgay Çavdar wrote:
Our server on the version 7.2 and the client also 7.2 running on
tru64unix
5.1b.
Our backups are ended with the fallowing error:
12/07/06 11:20:49 nsrd: client:/x/y saving to pool
'pool1' (Opool1.069)
* client:/x/y 2 retries attempted
* client:/x/y NetWorker: Cannot contact nsrexecd service on client,
Service
not available.
* client:/x/y
* client:/x/y lost connection to server, exiting
There is no name resolution issue, server can ping with the name
and vice
versa. When i get rpcinfo from the client i found that there is no
nsrexec
there. Why does the client cant register nsrexec RPC ? Any idea?
client#rpcinfo <client@r/bin#rpcinfo> -p
Are the client and server different systems? Your email is vague on
that point. If your server and client are different, are they on the
same subnet or different subnets? Is there a firewall sitting between
the client and server? If so, make sure the firewall is not causing
the problem. Also, can you see two nsrexecd processes running on the
client, there must be two processes.
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|
