Can not connect on socket (25)

check the following



ping <master and media>

nslookup <master and media>

bpclntcmd -pn

bpclntcmd -self

bpclntcmd -hn <master and media>

bpclntcmd -ip <IP of master and media>



run this and paste it backup, normaly socket error 25 can be a DNS issue with your media server.

C:\Program Files\VERITAS\NetBackup\bin\admincmd>bptestbpcd -client dmz_client -debug



Exact Error Message
socket read failed

Details:
Overview:
When bplist is initiated from a NetBackup client, an attempt is made to connect to the NetBackup master server on the bprd port (13720). The master must then connect back to the client. If the master server's bprd process is unable to resolve the hostname of the client based on the IP address of the incoming connection, the operation fails.

#bplist -l /tmp
EXIT STATUS 23: socket read failed

Troubleshooting:
To verify that the NetBackup master is able to resolve the client IP address, use the following command on the NetBackup master server:

/usr/openv/netbackup/bin/bpclntcmd -ip <client_ip_address>

The following output indicates the NetBackup master server has a reverse lookup issue that needs to be resolved:

installation netbackup server 6.0 on CentOS 5.1

[root@netbackup ~]#yum install compat-libstdc++-296 xinetd libXp

[root@netbackup ~]#setenforce 0

To make NetBackup start up automatically when
the system is restarted, the netbackup script found in
/usr/openv/netbackup/bin/goodies has been placed in /etc/rc.d/init.d,
with links to it placed in the /etc/rc.d/rc2.d directory.


To make NetBackup start up automatically when
the system is restarted, the netbackup script found in
/usr/openv/netbackup/bin/goodies has been placed in /etc/rc.d/init.d,
with links to it placed in the /etc/rc.d/rc3.d directory.


To make NetBackup start up automatically when
the system is restarted, the netbackup script found in
/usr/openv/netbackup/bin/goodies has been placed in /etc/rc.d/init.d,
with links to it placed in the /etc/rc.d/rc5.d directory.


To make NetBackup shut down automatically when
the system is restarted, the netbackup script found in
/usr/openv/netbackup/bin/goodies has been placed in /etc/rc.d/init.d,
with links to it placed in the /etc/rc.d/rc0.d directory.


To make NetBackup shut down automatically when
the system is restarted, the netbackup script found in
/usr/openv/netbackup/bin/goodies has been placed in /etc/rc.d/init.d,
with links to it placed in the /etc/rc.d/rc6.d directory.

Enter license key: DEXZ-92WW-8WVP-ZO4O-4O4O-4777-7777-HPC6-NCN

DEXZ-92WW-8WVP-ZO4O-4O4O-4777-7777-HPC6-NCN:
NetBackup Enterprise Server Base product with all the features enabled
has been registered.

**********************************************************************
********************* ALERT - ACTION REQUIRED ************************
**********************************************************************

This installation could fit one of two scenarios.
Follow the instructions that fit your situation.


**********************************************************************

1. It appears NetBackup is being installed with the intention of
using a different network interface than the default (netbackup).
NetBackup daemons will be shut down. Additional entries must
be added to /usr/openv/netbackup/bp.conf and
/usr/openv/volmgr/vm.conf. The entry and the file affected
are as follows:

REQUIRED_INTERFACE=backupserver (bp.conf)
REQUIRED_INTERFACE=backupserver (vm.conf)
DEVICE_HOST=backupserver (vm.conf)

After these entries have been added, start the NetBackup and Media
Manager daemons by executing the following command:

/usr/openv/netbackup/bin/goodies/netbackup start

**********************************************************************

OR

**********************************************************************

2. This machine appears to be a member of a cluster. NetBackup
daemons will be shut down. Do not install any NetBackup add-on
or database agent products on this machine until after the
NetBackup server has been configured to run in a cluster. After
NetBackup server installation activities have occurred on all
members of the cluster, execute the following command on the
primary node:

/usr/openv/netbackup/bin/cluster/cluster_config

**********************************************************************



File /usr/openv/tmp/install_trace.7353 contains a trace of this install.
That file can be deleted after you are sure the install was successful.