Any one idea about bpcd with Error-57

[Baski]

Hi Team,

One policy has 5 clients, 4 clients are running fine only one client gives the problem with EC-57

All are same configuation

Master/media/clients : Solaris 10 , NBU 6.5.5

Problem client BPCD logs

20:52:42.272 [9893] <16> bpcd main: ParseArguments failed
20:52:56.291 [9952] <16> bpcd main: ParseArguments failed
20:53:28.682 [10154] <2> ListenForConnection: Unexpected working directory: /home/admin/raju
20:53:28.682 [10154] <2> bpcd main: offset to GMT -36000
20:53:28.683 [10154] <2> logconnections: getsockname(0) failed: 95
20:53:28.684 [10154] <2> bpcd main: setup_sockopts complete
20:53:28.684 [10154] <2> vauth_acceptor: vauth_comm.c.307: Function failed: 17 0x00000011
20:53:28.684 [10154] <16> bpcd main: authentication failed: 17
20:53:52.514 [10293] <2> ListenForConnection: Unexpected working directory: /home/admin/raju
20:53:52.514 [10293] <2> bpcd main: offset to GMT -36000
20:53:52.515 [10293] <2> logconnections: getsockname(0) failed: 95
20:53:52.515 [10293] <2> bpcd main: setup_sockopts complete
20:53:52.515 [10293] <2> vauth_acceptor: vauth_comm.c.307: Function failed: 17 0x00000011
20:53:52.515 [10293] <16> bpcd main: authentication failed: 17
20:54:46.976 [10709] <2> ListenForConnection: Unexpected working directory: /home/admin/raju
20:54:46.988 [10709] <2> bpcd main: offset to GMT -36000
20:54:46.988 [10709] <2> logconnections: getsockname(0) failed: 95
20:54:46.988 [10709] <2> bpcd main: setup_sockopts complete
20:54:46.989 [10709] <2> vauth_acceptor: vauth_comm.c.307: Function failed: 17 0x00000011
20:54:46.989 [10709] <16> bpcd main: authentication failed: 17
 

From Master server telnet not working
Telnet <client name> bpcd
Trying 9.97.79.6...
telnet: Unable to connect to remote host: Connection refused

Telnet <client name> vnetd
 Trying 9.97.79.6...
telnet: Unable to connect to remote host: Connection refused

bpclntcmd working from both sides ( master and client )

tracerout working ( just two hopes only)

Ping response working both sides

 

vnetd&bpcd ports is listening.
 $ netstat -an|grep -i 13782
      *.13782              *.*                0      0 49152      0 LISTEN
 $ netstat -an|grep -i 13724
      *.13724              *.*                0      0 49152      0 LISTEN

 still problem exist,

Please help on this.

[Kiran_Bandi]

Refer to the following document. It may help you.

http://www.symantec.com/business/support/index?page=answerlink&url=http%3A%2F%2Fwww.symantec.com%2Fb...

Regards.

[RiaanBadenhorst]

HI,

Quick check. Since you can't connect to the ports on the client from the master, see if you can connect to the ports from the client itself.

telnet localhost bpcd

telnet localhost vnetd

If that works, you know something in the path from the master to the client is blocking you.

If that doesn't work, you know something on the client is blocking it. Could be the hosts.allow file is not configured correctly.

[Marianne]

We need to find where this is coming from:

"ListenForConnection: Unexpected working directory: /home/admin/raju"

Please check entries in /etc/services and /etc/inetd.conf

Also check entries in /etc/hosts.allow and hosts.deny.

Similar bpcd entries in this post: https://www-secure.symantec.com/connect/forums/netbackup-solaris-10-media-server-issue

[Baski]

Hi Kiran,

I have done all steps as per doc, but no luck.

below logs from media server ( bpbrm logs)

<2> bpbrm read_parent_msg: read from parent START BACKUP -c <client name>
<2> bpbrm process_start_backup_msg: processing START BACKUP message.
<2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
<2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpdbm
 <2> logconnections: BPDBM CONNECT FROM x.x.x.x.55935 TO y.y.y.y.13724
<2> vnet_async_connect: vnet_vnetd.c.4233: getsockopt SO_ERROR returned: 146 0x00000092
 <2> vnet_async_connect: vnet_vnetd.c.4233: getsockopt SO_ERROR returned: 146 0x00000092
2> vnet_async_connect: vnet_vnetd.c.4233: getsockopt SO_ERROR returned: 146 0x00000092

 

[Baski · Accepted solution]

To fix the problem, unplumbed the  NBU Interfaces and plumbeed them back and bound them to the Non-Global zones. Now able to ping and connect to netbackup dameons from master server.

    On Global zone CSA , suspected some binary corruption and the same has been fixed.  And the netbackup services started up. Now CSA,CSAza,CSAzb all are connectable via  network and netbackup dameons are listening to their respective port now.

After that, copied NBU binaries from ohter host /usr/openv and then restarted the NBU deamons

Then started the backups and got completed successfully.