Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Need help fixing the error 54.

Updated: 21 May 2010 | 7 comments
Rockey jay's picture
0 0 Votes
Login to vote
Hi,
 
 I unable to fix an issue for the error code 54. After adding the client to the master server client list , running the backup failed with error 54. Added the client host name entry on Master/Media server , There is no network issue between client and server (checked using ping,nslookup commands). Using command bpclntcmd checked the name resolution on both client /master/media ..looks good. The version of NB on both Master and client is NB 5.1 MP5. Required NB services are running on the client and server and bpcd on client side is having status Listning. But backup is still getting failed with error 54. And finally i checked using below commands in Master server.
 
./bpgetconfig -g <client name> gives o/p as network connection timed out
./bpgetconfig -M <client name> gives o/p as  invalid error number
 
 I tried to use IP address and FQDN name of the client as well on the command gives same error,
 
Can you pls guide me how to proceed with this issue to fix it?
 
Thanks.


Comments

Don McAra's picture
17
Apr
2007
0 Votes 0
Login to vote

Hi Jay, can you try issuing the telnet to the bpcd port (13782).   If you are not able to telnet to this
port then it is possible that the server's  ports are not set up correctly.  Port 13782 needs to be
enabled,  either through inetd.conf file (Unix) or port setting on Wintel.
 
If these all check out,  you may want to peruse the "Solving Network Issues"  chapter in the
Netbackup Troubleshooting guide. 
Peter Bevington's picture
17
Apr
2007
0 Votes 0
Login to vote

Hi Jay,
 
I once (no laughs is SC is looking at this ;-) had a real problem re name resolution, check the following :
  • If there needs to be any persistent routes setup if your using a backup LAN
  • The NetBackup logs that are useful to troubleshoot are bprd and bpsched logs on master server. Also bpcd from the media server useful to check from the media server side. If bpcd on media server is fine, then next process is bpbrm from the media server and you can see bpbrm logs for any backup/restore failure.If there are some tape device issue, bptm on media server is useful. If there are some connection failure on a paticular client machine from media server, then bpcd from that client machine is also to be checked.
  • Check the name resolution between the Master & each Media server. The bpclntcmd function can be found in d:\veritas\netbackup\bin (see http://support.veritas.com/docs/261393)

  • Check DNS entries and the domain which they are entered in with their respect PTR records

  • if a client has two separate FQDN entries, it is vitally important that the client checks under the correct FQDN domain first, otherwise it'll resolve the wrong entry and the IP link will fail

I hope this is of some use.

Rockey jay's picture
19
Apr
2007
0 Votes 0
Login to vote

Hi,
 
     We tried in all ways of troubleshooting , but unable to find the exact solution. At last we found some TCP wrappers blocking the ports and not establishing the client/server connectivity.. disabled those wrappers , problem fixed.. :smileyhappy:
 
PRJUANL's picture
06
Jul
2007
0 Votes 0
Login to vote

Hi,
 
Where exactly do you found the TCP wrappers  blocking the ports in the Client or Server side?
How\where you disable those TCP wrappers?
 
Thanks, PRJUANL
Stumpr2's picture
06
Jul
2007
0 Votes 0
Login to vote

yes, please do followup. thanks.
 
 
sdw303's picture
06
Jul
2007
0 Votes 0
Login to vote

Did you try several consecutive:
$ nslookup <ip>
...to check whether multiple DNS names are setup for either master, media or client?
 
Have you tried the following:
$ bpclntcmd -hn <name>
$ bpclntcmd -ip <ip>
....twice each for master to media, master to client, media to master, media to client and client to master and client to media.
 
i.e. you need to test that every box can properly resolve DNS lookup and DNS reverse lookup from every box to every other box.
 
HTH,
Regards,
Dave.
sdw303's picture
06
Jul
2007
0 Votes 0
Login to vote

There is a guide for resolving status 54:
 
...and many other status codes, if you search here: