cancel
Showing results for 
Search instead for 
Did you mean: 

Solaris 10u9. Unable to connect new client: Status 24/25

Alex_Collins
Level 2

Hi all.

We have a long standing netbackup 6.5 solution which has been working for years.
I have replaced a server and need to connect the new server to netbackup.

I did an FTP Install of the client from the server, just the same as I always do.

Netbackup is running on the client

From the client:

# ./bpclntcmd -hn shake6
host shake6: shake6 at 10.22.211.40 (0xa16d328)
checkhname: aliases:
# ./bpclntcmd -hn riv-login
host riv-login: riv-login at 194.66.XXX.XXX(0xc242a0ae)
checkhname: aliases:

From the NBU server:

# ./bpclntcmd -hn shake6
host shake6: shake6 at 10.22.211.40 (0xa16d328)
checkhname: aliases:
# ./bpclntcmd -hn riv-login
host riv-login: RIV-LOGIN at 194.66.XXX.XXX (0xc242a0ae)
checkhname: aliases:
#
 

Again from the NBU server:

# ./bptestbpcd -client shake6 -debug -verbose
13:10:53.504 [3545] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2034: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
13:10:53.505 [3545] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: service: bpcd
13:10:53.509 [3545] <2> logconnections: BPCD CONNECT FROM 194.66.XXX.XXX.45861 TO 10.22.211.40.13724
13:10:53.513 [3545] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.178: msg: VNETD CONNECT FROM 194.66.XXX.XXX.45862 TO 10.22.211.40.13724 fd = 5
13:10:53.530 [3545] <2> vnet_vnetd_connect_forward_socket_end: vnet_vnetd.c.529: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
13:10:53.537 [3545] <2> vnet_vnetd_connect_forward_socket_end: vnet_vnetd.c.546: ipc_string: /tmp/vnet-08588311768701512228000000000-iPaGXq
13:10:53.539 [3545] <2> sighdl: pipe signal
13:10:53.540 [3545] <2> put_long: (11) network write() error: Broken pipe (32); socket = 4
13:10:53.540 [3545] <2> bpcr_put_vnetd_forward_socket: put_string /tmp/vnet-08588311768701512228000000000-iPaGXq failed: 32
13:10:53.540 [3545] <2> bpcr_connect: bpcr_put_vnetd_forward_socket failed: 24
13:10:53.540 [3545] <2> ConnectToBPCD: bpcd_connect_and_verify(shake6, shake6) failed: 24
<16>bptestbpcd main: Function ConnectToBPCD(shake6) failed: 24
13:10:53.542 [3545] <16> bptestbpcd main: Function ConnectToBPCD(shake6) failed: 24
<2>bptestbpcd: socket write failed
13:10:53.543 [3545] <2> bptestbpcd: socket write failed
<2>bptestbpcd: EXIT status = 24
13:10:53.544 [3545] <2> bptestbpcd: EXIT status = 24
socket write failed
#

On the Client:

# ndd -get /dev/tcp tcp_recv_hiwat
262144
# ndd -get /dev/tcp tcp_xmit_hiwat
262144
# ndd -get /dev/tcp tcp_max_buf
102400000
#
 

Any clues here are more than welcome.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Yogesh9881
Level 6
Accredited

i hope below will help you

https://www-secure.symantec.com/connect/forums/bptestbpcd-fails-self

can u make /etc/hosts entry with FQDN & try same command (bptestbpcd)

View solution in original post

3 REPLIES 3

Yogesh9881
Level 6
Accredited

i hope below will help you

https://www-secure.symantec.com/connect/forums/bptestbpcd-fails-self

can u make /etc/hosts entry with FQDN & try same command (bptestbpcd)

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Might be hosts.allow on the client

 

http://www.symantec.com/docs/TECH56080

Alex_Collins
Level 2

Hi

Thankyou for your help here.

It was for no aparent reason a name resolution issue.
Asdding the machines FQDN's to /etc/hosts has solved the problems.