02-14-2012 10:02 AM
Hi All!
I have some Linux clients in Netbackup 6.5.5, when I try to back them up I am getting a code 58 error, but I am able to ping and telnet to port bpcd. Anty thoughts?
Thanks!
Fred
Solved! Go to Solution.
02-14-2012 08:36 PM
The reason for status 58 is normally when the client is unable to connect back.
NBU 6.x uses vnetd (13724) to connect to bpcd on client and client needs to connect back on same port. Linux clients often experience problems when its own firewall (iptables) is enabled. Check/confirm that iptables is disabled.
Client also needs to resolve server's incoming IP address to hostname that appears as SERVER in bp.conf.
Do the following to tests comms:
On client: create bpcd log folder under /usr/openv/logs
On master (as well as media server if different from master): run the following from cmd:
bptestbpcd -client <client-name> -verbose
Check in client's bpcd log if client is able to resolve server's IP address to hostname. See how the resolved name is compared with SERVER entries.
If client cannot resolve server name, check DNS or add /etc/hosts entry on client for the server.
02-14-2012 08:36 PM
The reason for status 58 is normally when the client is unable to connect back.
NBU 6.x uses vnetd (13724) to connect to bpcd on client and client needs to connect back on same port. Linux clients often experience problems when its own firewall (iptables) is enabled. Check/confirm that iptables is disabled.
Client also needs to resolve server's incoming IP address to hostname that appears as SERVER in bp.conf.
Do the following to tests comms:
On client: create bpcd log folder under /usr/openv/logs
On master (as well as media server if different from master): run the following from cmd:
bptestbpcd -client <client-name> -verbose
Check in client's bpcd log if client is able to resolve server's IP address to hostname. See how the resolved name is compared with SERVER entries.
If client cannot resolve server name, check DNS or add /etc/hosts entry on client for the server.
02-14-2012 10:27 PM
you may need to update host file as shown below. (master media client)
192.168.0.122 myserver01 myserver01.mydomain.com
02-17-2012 07:49 AM
Jere is somthing curious I have seen in the Detailed status on the Code 58's that I am getting that I can ping the clients and telnet to bpcd port.
02/16/2012 19:37:57 - estimated 0 kbytes needed
02/16/2012 19:37:57 - started process bpbrm (pid=23429)
02/16/2012 19:39:38 - Error bpbrm (pid=23429) cannot connect to lh21049s, No such file or directory (2)
02/16/2012 19:39:38 - end writing
can't connect to client (58)
Any Thoughts?
Fred
02-17-2012 08:39 AM
It is either ports blocked or possibly, based on your last message, the netbackup daemons on those clients are not running
Try a bpps -a on one of them to see what processes are running
02-17-2012 09:12 AM
THanks so much to all of you for all of the advice!
02-17-2012 09:36 AM
Connection to bpcd is made VIA vnetd.
if you run bptestbpcd as suggested in my previous post, you will see which port is attempted.
02-19-2012 08:52 AM
on RedHat >service iptables stop
on SuSE> service SuSEFirewall2 stop
02-19-2012 07:34 PM
Scott correct iptables stop and or restarts the service /etc/init.d/xinetd
02-19-2012 08:43 PM
............. as I have pointed out on 15 Feb ................
03-03-2012 04:50 AM
Yes, the Marianne pointed iptables
Or refer my case https://www-secure.symantec.com/connect/forums/failed-connect-client