socket write failed (Status 24)

[Shakil_Qureshi]

hi team,

i have Netbackup 6.5.4 installed on Solaris. 

now i want to have a clinet linux connected, but every time i try to install NBU client on linux, it installed sucessfully.

but in NBU console, it gives me error " socket write failed (Status 24) "

 i am also attaching the intall log file, any body check and tells me, what is the issue, i have looked in to it on goole, symantec tek forums, but got no clue.

[lu]

On the client, does this work ? bpclntcmd -sv And on the server : bpgetconfig -g linuxbox ?

[Andy_Welburn]

every one we deal with has been set up differently.

Things to check (maybe?):

• Did you restart xinetd? (Is xinetd installed even?)
• Are bpcd/vnetd listening? (netstat -a | grep bpcd or netstat -a | grep vnetd)
• Firewall settings?
• SELinux interfering?

***EDIT***
By 'Firewall' I was referring to the firewall on the linux box, not a corporate firewall you may have set up.

Also, have you looked at using bptestbpcd? e.g. bptestbpcd -client linuxclient -verbose -debug

[Shakil_Qureshi]

yes, i have restarted xinetd, although bpcd/vnetd are running. Red hat Firewall is disabled. SELinux interfering is disabled. [root@linuxbox ~]# netstat -a | grep vnetd tcp 0 0 *:vnetd *:* LISTEN [root@linuxbox ~]# netstat -a | grep bpcd tcp 0 0 *:bpcd *:* LISTEN [root@linuxbox ~]# but still i am facing status 24. i don't know what to do. even i can send u bpcd logs etc.. any thing u want.?

[lu]

we could help you more if you could run : bpclntcmd -sv, bpgetconfig -g linuxbox, bptestbpcd -client linuxclient -verbose -debug, etc

[MOHAMED_PATEL]

Linux to Windows...hmm
Add the master server hostname and IP address on the linuxbox hosts file.
add the hostanme and Ip address on the master server.
This should eliminate dns lookups -

And as LU pointed out above - run the NB commands as well from both ends.

[Shakil_Qureshi]

one thing which i have noticed, i was trying to install NBU Client on linuxbox, but on NBU Console giving status error 24.
then i installed BMR Server on that client as well... again on NBU Console error 24, but under BMR Management, Linuxbox was mentioned as a BMR Server.
it means it has a communciation with linuxbox, but there is something due to which proper communciation is disturbed. and giving error 24.

kindly help me out.... here is the output for the follwoing command

1) root@pdbbackup # /usr/openv/netbackup/bin/bpclntcmd -sv
6.5

2) root@pdbbackup # /usr/openv/netbackup/bin/admincmd/bpgetconfig -g linuxbox
socket write failed

3) root@pdbbackup # /usr/openv/netbackup/bin/admincmd/bptestbpcd -client linuxbox
<16>bptestbpcd main: Function ConnectToBPCD(linuxbox) failed: 12149
invalid error number

4) root@pdbbackup # /usr/openv/netbackup/bin/admincmd/bptestbpcd -client bmrlinux -verbose -debug
14:56:56.629 [5453] <2> bptestbpcd: VERBOSE = 5
14:56:56.631 [5453] <2> read_client: ?
14:56:56.632 [5453] <2> read_client: opendir() failed: bmrlinux: No such file or directory (2)
14:56:56.632 [5453] <2> ConnectToBPCD: db_getCLIENT(bmrlinux) failed: 227
14:56:56.634 [5453] <2> vauth_get_user_name: vauth_comm.c.687: cached_user_name: root
14:56:56.634 [5453] <2> vauth_get_user_name: vauth_comm.c.689: cached_user_name: :root
14:56:56.634 [5453] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :root
14:56:56.635 [5453] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect_opts2 = 0x01000100
14:56:56.635 [5453] <2> local_bpcr_connect: bpcr.c.283: connect_opts = 0x01000100
14:56:56.635 [5453] <2> local_bpcr_connect: bpcr.c.322: daemon_port_type = 0
14:56:56.636 [5453] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
14:56:56.636 [5453] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
14:56:56.637 [5453] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
14:56:56.637 [5453] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
14:56:56.637 [5453] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
14:56:56.637 [5453] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
14:56:56.637 [5453] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
14:56:56.638 [5453] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
14:56:56.638 [5453] <2> vnet_async_connect: vnet_vnetd.c.4033: connect in progress: 0 0x00000000
14:56:56.651 [5453] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2046: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
14:56:56.652 [5453] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2060: service: bpcd
14:56:56.692 [5453] <2> vnet_async_connect: vnet_vnetd.c.4219: in progress connect: 0 0x00000000
14:56:56.692 [5453] <2> vnet_async_connect: vnet_vnetd.c.4222: connect: async CONNECT FROM 192.168.50.240.33370 TO 192.168.50.246.13724 fd = 4
14:56:56.692 [5453] <2> logconnections: BPCD CONNECT FROM 192.168.50.240.33370 TO 192.168.50.246.13724
14:56:56.693 [5453] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication required
14:56:56.694 [5453] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
14:56:56.694 [5453] <2> bpcr_authenticate_connection: no authentication required
14:56:56.695 [5453] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.180: msg: VNETD CONNECT FROM 192.168.50.240.33371 TO 192.168.50.246.13724 fd = 5
14:56:56.707 [5453] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.533: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
14:56:56.749 [5453] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.550: ipc_string: /tmp/vnet-07482271278204694422000000000-eqKCAZ
14:56:56.750 [5453] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.561: hash_str1: bfe493f908e23e424f6ac7613c487f31
14:56:56.750 [5453] <2> put_long: (11) network write() error: Broken pipe (32); socket = 4
14:56:56.751 [5453] <2> bpcr_put_vnetd_forward_socket: put_string /tmp/vnet-07482271278204694422000000000-eqKCAZ failed: 32
14:56:56.751 [5453] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 24
14:56:56.751 [5453] <2> ConnectToBPCD: bpcd_connect_and_verify(bmrlinux, bmrlinux) failed: 24
<16>bptestbpcd main: Function ConnectToBPCD(bmrlinux) failed: 24
14:56:56.752 [5453] <16> bptestbpcd main: Function ConnectToBPCD(bmrlinux) failed: 24
<2>bptestbpcd: socket write failed
14:56:56.753 [5453] <2> bptestbpcd: socket write failed
<2>bptestbpcd: EXIT status = 24
14:56:56.754 [5453] <2> bptestbpcd: EXIT status = 24
socket write failed
root@pdbbackup #

[Andy_Welburn]

Unable to connect to Linux clients with xinetd banners enabled on the client

Can you also confirm that the master name is the first entry in the bp.conf file on the client (SERVER=master)

For completeness:

How to verify name resolution for Veritas NetBackup (tm) systems, using the "bpclntcmd" command

[Shakil_Qureshi]

yes,  in bp.conf the first entry is the Master Server name

[lu]

You can also check your /etc/hosts.allow hosts.deny files on the client. Maybe they are blocking incoming connections.

[Christoph_Linde]

Enable verbose logging on client by putting

VERBOSE = 5

int bp.conf on client.

Second enable vnetd logging by creating the following directory:

/usr/openv/netbackup/logs/bpcd
/usr/openv/netbackup/logs/vnetd

Then try bptestbpcd to client again.

Then try the following on master:

bpclient -client bmrlinux -modify -connect_options 2 2 2

Then retry bptestbpcd

And then look into vnetd and bpcd logs what happend.