network protocol error (39)
hello All,
This we are getting when running vmoprcmd -h media server -d from the master server..on the media server when we run bpps -a we get the following:
-bash-3.2$ sudo bpps -a
Password:
NB Processes
------------
MM Processes
------------
root 12732 1 0 08:30:16 ? 0:00 ltid
root 12764 12732 0 08:30:22 ? 0:00 avrd
root 12751 12732 0 08:30:18 ? 0:00 acsd
root 11495 1 0 07:41:16 ? 0:00 vmd
root 11690 1 0 07:41:28 ? 0:00 acsssi 13741
root 13353 11495 0 08:30:49 ? 0:00 /usr/openv/volmgr/bin/oprd -sockfd 6 -nosig
root 19964 11495 0 08:41:38 ? 0:00 /usr/openv/volmgr/bin/oprd -sockfd 6 -nosig
root 29709 11495 0 08:57:41 ? 0:00 /usr/openv/volmgr/bin/oprd -sockfd 6 -nosig
root 9429 11495 0 09:13:44 ? 0:00 /usr/openv/volmgr/bin/oprd -sockfd 6 -nosig
root 11661 1 0 07:41:23 ? 0:00 acssel -s 13740
-bash-3.2$
please help me in resolving the same
Comments
One possible root cause of this error
is the existence of unresolvable server names in the <install_path>\VERITAS\NetBackup\Remote_Versions directory.
Any master to media server communication will spawn a named server entry in this directory. Decommissioned media server names may still exist in this directory.
Resolution:
Deleting the entire contents of the <install_path>\VERITAS\NetBackup\Remote_Versions directory (without deleting the directory itself) on the master server and all media servers is the resolution to this issue.
http://seer.entsupport.symantec.com/docs/289917.htm
~ Bill
media server
these entries are not there in the media server .....according to the document the entries should be there..rite..i found out the master server has these entries...can i remove the entry of the particular media server and try...
This type of problem mostly
This type of problem mostly comes because of SSO environment trying to get the status of all the drives from master to media. In master server you will see lot of "oprd -sockfd 6 -nosig" messages increasing thus as a result you will get "Network protocol timeout error(39)".
Even if you run vmoprcmd -d you will get network protocol timeout error. So you need to check if all the DRIVE NAMES and INDEX are same across all the media servers and bring down netbackup services completely on master and all the media servers once. We used to get the same issue and we used to do the same
Would you like to reply?
Login or Register to post your comment.