Solved: "EXIT STATUS 25: cannot connect on socket" while i...

Harry_NBAD · ‎01-15-2014

I am facing this issue as I am initiating this restore and receiving the following error:

"EXIT STATUS 25: cannot connect on socket"

I looked upon the bplogs for the restore script but couldn't find anything.

Please suggest, it's urgent.

Thanks in Advance!!!

Regards,

Harmanpreet Singh

Marianne · ‎01-16-2014

In my bprestore script there was a typo error.

Yes! Any typo error will cause a failure!
As you have experienced -S wrong-name produced status 25.
-C wrong-name will cause status 227 (no entity found).
-D wrong-name will cause some sort of connection error. Probably 'Client hostname not found' (status 48).

-S -C and -D are REALLY optional switches.

Without -S bprestore will use 1st entry in bp.conf to know where to send restore request to.

Without -C bprestore will request restore for local hostname (CLIENT_NAME in bp.conf)

Without -D bprestore will automatically perform local restore.

See bprestore command usage: http://www.symantec.com/docs/HOWTO43687

ANYTHING in square brackets is optional.

bprestore [-A | -B] [-K] [-l | -H | -y] [-r] [-T] [-L progress_log [-en]] [-R rename_file] [-C client] [-D client] [-S master_server] [-disk_media_server media_server][-t policy_type] [-ppolicy] [-k "keyword_phrase"] [-cm] [-drs] [-md] [-dd] [-td temp_dir] [-s date] [-e date] [-Ffile_options] [-spsredir_server hostname] [-spscurver] [-spsignorelock] [-spspreserveiis] [-spsrestoresecurity] [-spsverkeep [0 | 1 | 2]] [-vhd_fn VHD_filename] [-vhd_type 0 | 1] [-vhd_dsizeVHD_disk_size] [-vhd_dof 0 | 1] -BR portal_name | teamsite_name] [-copycopy_number] [-granular_restore] [-priority number] [-w [hh:mm:ss]] -flistfile | filenames [-ev_migrated_data]

Handy NetBackup Links

View solution in original post

RamNagalla · ‎01-15-2014

hello,

where exactly you are reciving this error? if yes, from where you are actually trying to do the restore?

before starting the restore?

or after starting the restore , the job is failing with 25? if yes please provide the detail status of the job

Harry_NBAD · ‎01-15-2014

Hello,

I am executing the restore from the command line and when I am executing the command it is giving me the same error.

"EXIT STATUS 25: cannot connect on socket."

I am firing this command from master server.

Regarding the command being fired, it is normal bprestore command which is being executed with all the parameters required.

/usr/openv/netbackup/bin/bprestore -r -L <log-file> -R <rename-file> -C masterserver -D master-server -S master-server -p policy-name -s $starttime -e $endtime -f source-file

Master and media server is just one machine.

Regards,

RamNagalla · ‎01-15-2014

so when you trigger the command its giving the output

EXIT STATUS 25: cannot connect on socket

so does netbackup services are running fine.. including with bprd?

Harry_NBAD · ‎01-15-2014

Yes they are running fine.

NB Processes

------------

root 8573 1 0 Jan 6 ? 4:44 /usr/openv/netbackup/bin/nbevtmgr

root 8580 1 0 Jan 6 ? 2:41 /usr/openv/netbackup/bin/nbaudit

root 8686 1 0 Jan 6 ? 3:46 /usr/openv/netbackup/bin/bprd

root 8707 8704 0 Jan 6 ? 0:19 /usr/openv/netbackup/bin/nbproxy dblib nbjm

root 8712 8710 0 Jan 6 ? 72:55 /usr/openv/netbackup/bin/bpjobd

root 8650 8716 0 Jan 6 ? 0:05 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root 8807 1 0 Jan 6 ? 1:54 /usr/openv/netbackup/bin/nbars

root 8722 1 0 Jan 6 ? 3:21 /usr/openv/netbackup/bin/nbstserv

root 8663 1 0 Jan 6 ? 30:14 /usr/openv/netbackup/bin/nbrb

root 8559 1 0 Jan 6 ? 581:44 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/global/databases.conf -hn 8

root 8693 1 0 Jan 6 ? 0:45 /usr/openv/netbackup/bin/bpcompatd

root 12439 12438 0 Jan 6 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -HPManager-1.ior.mgr -proxyID HPManager#1_1389040255

root 8716 1 0 Jan 6 ? 11:12 /usr/openv/netbackup/bin/nbpem

root 8741 1 0 Jan 6 ? 6:07 /usr/openv/netbackup/bin/nbim

root 8710 1 0 Jan 6 ? 11:52 /usr/openv/netbackup/bin/bpdbm

root 8704 1 0 Jan 6 ? 21:03 /usr/openv/netbackup/bin/nbjm

root 8463 1 0 Jan 6 ? 2:00 /usr/openv/netbackup/bin/vnetd -standalone

root 8657 1 0 Jan 6 ? 36:27 /usr/openv/netbackup/bin/nbemm

root 8466 1 0 Jan 6 ? 1:34 /usr/openv/netbackup/bin/bpcd -standalone

root 8750 8716 0 Jan 6 ? 0:18 /usr/openv/netbackup/bin/nbproxy dblib nbpem

root 8827 1 0 Jan 6 ? 1:00 /usr/openv/netbackup/bin/bmrd

root 8835 1 0 Jan 6 ? 0:12 /usr/openv/netbackup/bin/nbcssc -a NetBackup

root 9504 8716 0 Jan 6 ? 0:38 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email

root 8752 1 0 Jan 6 ? 4:57 /usr/openv/netbackup/bin/nbrmms

root 8799 1 0 Jan 6 ? 83:24 /usr/openv/netbackup/bin/nbsl

root 8844 1 0 Jan 6 ? 0:41 /usr/openv/netbackup/bin/nbsvcmon

MM Processes

------------

root 8673 1 0 Jan 6 ? 0:56 /usr/openv/volmgr/bin/ltid

root 8680 1 0 Jan 6 ? 1:27 vmd -v

root 8825 1 0 Jan 6 ? 0:27 tldcd -v

root 8817 8673 0 Jan 6 ? 0:13 tldd -v

root 8821 8673 0 Jan 6 ? 1:43 avrd -v

root 5985 8817 0 19:15:03 ? 0:00 tldd -v

eux290{root}# netstat -a |grep bp

tcp 0 0 *.bpdbm *.* LISTEN

tcp 0 0 *.bpjobd *.* LISTEN

tcp 0 0 *.bprd *.* LISTEN

tcp 0 0 *.bpcd *.* LISTEN

====

The daemon is running fine and able to listen.

Harry_NBAD · ‎01-15-2014

Yes The bprd daemon is running fine.

netstat -a |grep bp

tcp 0 0 *.bpdbm *.* LISTEN

tcp 0 0 *.bpjobd *.* LISTEN

tcp 0 0 *.bprd *.* LISTEN

tcp 0 0 *.bpcd *.* LISTEN

revarooo · ‎01-15-2014

Let's see the Detailed Status information,

Harry_NBAD · ‎01-15-2014

Kindly let me know if any other information is required.

RamNagalla · ‎01-15-2014

show us the output of bpps -a and also the exact output of the bprestore command(copy & paste or screenshot)

Harry_NBAD · ‎01-15-2014

/usr/openv/netbackup/bin/bpps -a

NB Processes

------------

root 8573 1 0 Jan 6 ? 4:44 /usr/openv/netbackup/bin/nbevtmgr

root 8580 1 0 Jan 6 ? 2:41 /usr/openv/netbackup/bin/nbaudit

root 8686 1 0 Jan 6 ? 3:46 /usr/openv/netbackup/bin/bprd

root 8707 8704 0 Jan 6 ? 0:19 /usr/openv/netbackup/bin/nbproxy dblib nbjm

root 8712 8710 0 Jan 6 ? 72:55 /usr/openv/netbackup/bin/bpjobd

root 8650 8716 0 Jan 6 ? 0:05 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root 8807 1 0 Jan 6 ? 1:54 /usr/openv/netbackup/bin/nbars

root 8722 1 0 Jan 6 ? 3:21 /usr/openv/netbackup/bin/nbstserv

root 8663 1 0 Jan 6 ? 30:14 /usr/openv/netbackup/bin/nbrb

root 8559 1 0 Jan 6 ? 581:44 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/global/databases.conf -hn 8

root 8693 1 0 Jan 6 ? 0:45 /usr/openv/netbackup/bin/bpcompatd

root 12439 12438 0 Jan 6 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -HPManager-1.ior.mgr -proxyID HPManager#1_1389040255

root 8716 1 0 Jan 6 ? 11:12 /usr/openv/netbackup/bin/nbpem

root 8741 1 0 Jan 6 ? 6:07 /usr/openv/netbackup/bin/nbim

root 8710 1 0 Jan 6 ? 11:52 /usr/openv/netbackup/bin/bpdbm

root 8704 1 0 Jan 6 ? 21:03 /usr/openv/netbackup/bin/nbjm

root 8463 1 0 Jan 6 ? 2:00 /usr/openv/netbackup/bin/vnetd -standalone

root 8657 1 0 Jan 6 ? 36:27 /usr/openv/netbackup/bin/nbemm

root 8466 1 0 Jan 6 ? 1:34 /usr/openv/netbackup/bin/bpcd -standalone

root 8750 8716 0 Jan 6 ? 0:18 /usr/openv/netbackup/bin/nbproxy dblib nbpem

root 8827 1 0 Jan 6 ? 1:00 /usr/openv/netbackup/bin/bmrd

root 8835 1 0 Jan 6 ? 0:12 /usr/openv/netbackup/bin/nbcssc -a NetBackup

root 9504 8716 0 Jan 6 ? 0:38 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email

root 8752 1 0 Jan 6 ? 4:57 /usr/openv/netbackup/bin/nbrmms

root 8799 1 0 Jan 6 ? 83:24 /usr/openv/netbackup/bin/nbsl

root 8844 1 0 Jan 6 ? 0:41 /usr/openv/netbackup/bin/nbsvcmon

MM Processes

------------

root 8673 1 0 Jan 6 ? 0:56 /usr/openv/volmgr/bin/ltid

root 8680 1 0 Jan 6 ? 1:27 vmd -v

root 8825 1 0 Jan 6 ? 0:27 tldcd -v

root 8817 8673 0 Jan 6 ? 0:13 tldd -v

root 8821 8673 0 Jan 6 ? 1:43 avrd -v

root 5985 8817 0 19:15:03 ? 0:00 tldd -v

=========

./restore.sh

EXIT STATUS 25: cannot connect on socket

Harry_NBAD · ‎01-15-2014

./restore.sh

EXIT STATUS 25: cannot connect on socket

=======

root 8573 1 0 Jan 6 ? 4:44 /usr/openv/netbackup/bin/nbevtmgr

root 8580 1 0 Jan 6 ? 2:41 /usr/openv/netbackup/bin/nbaudit

root 8686 1 0 Jan 6 ? 3:46 /usr/openv/netbackup/bin/bprd

root 8707 8704 0 Jan 6 ? 0:19 /usr/openv/netbackup/bin/nbproxy dblib nbjm

root 8712 8710 0 Jan 6 ? 72:55 /usr/openv/netbackup/bin/bpjobd

root 8650 8716 0 Jan 6 ? 0:05 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

root 8807 1 0 Jan 6 ? 1:54 /usr/openv/netbackup/bin/nbars

root 8722 1 0 Jan 6 ? 3:21 /usr/openv/netbackup/bin/nbstserv

Harry_NBAD · ‎01-15-2014

extended output:

root 8663 1 0 Jan 6 ? 30:14 /usr/openv/netbackup/bin/nbrb

root 8559 1 0 Jan 6 ? 581:44 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/global/databases.conf -hn 8

root 8693 1 0 Jan 6 ? 0:45 /usr/openv/netbackup/bin/bpcompatd

root 12439 12438 0 Jan 6 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib -mgrIORFile -HPManager-1.ior.mgr -proxyID HPManager#1_1389040255

root 8716 1 0 Jan 6 ? 11:12 /usr/openv/netbackup/bin/nbpem

root 8741 1 0 Jan 6 ? 6:07 /usr/openv/netbackup/bin/nbim

root 8710 1 0 Jan 6 ? 11:52 /usr/openv/netbackup/bin/bpdbm

root 8704 1 0 Jan 6 ? 21:03 /usr/openv/netbackup/bin/nbjm

root 8463 1 0 Jan 6 ? 2:00 /usr/openv/netbackup/bin/vnetd -standalone

root 8657 1 0 Jan 6 ? 36:27 /usr/openv/netbackup/bin/nbemm

root 8466 1 0 Jan 6 ? 1:34 /usr/openv/netbackup/bin/bpcd -standalone

root 8750 8716 0 Jan 6 ? 0:18 /usr/openv/netbackup/bin/nbproxy dblib nbpem

root 8827 1 0 Jan 6 ? 1:00 /usr/openv/netbackup/bin/bmrd

Harry_NBAD · ‎01-15-2014

root 8835 1 0 Jan 6 ? 0:12 /usr/openv/netbackup/bin/nbcssc -a NetBackup

root 9504 8716 0 Jan 6 ? 0:38 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email

root 8752 1 0 Jan 6 ? 4:57 /usr/openv/netbackup/bin/nbrmms

root 8799 1 0 Jan 6 ? 83:24 /usr/openv/netbackup/bin/nbsl

root 8844 1 0 Jan 6 ? 0:41 /usr/openv/netbackup/bin/nbsvcmon

root 8673 1 0 Jan 6 ? 0:56 /usr/openv/volmgr/bin/ltid

root 8680 1 0 Jan 6 ? 1:27 vmd -v

root 8825 1 0 Jan 6 ? 0:27 tldcd -v

root 8817 8673 0 Jan 6 ? 0:13 tldd -v

root 8821 8673 0 Jan 6 ? 1:43 avrd -v

root 5985 8817 0 19:15:03 ? 0:00 tldd -v

revarooo · ‎01-15-2014

How about the DETAILED STATUS output of the restore job from the Activity Monitor!!!

Harry_NBAD · ‎01-15-2014

I pushed the restore operation from the CLI. and the output is just shown as:

./restore.sh

EXIT STATUS 25: cannot connect on socket

ontherocks · ‎01-15-2014

What's the status of backup of this specific netbackup client ?

Please provide output of below command :-

bptestbpcd -debug -verbose -client <client_name>

Harry_NBAD · ‎01-15-2014

[21387] <2> bptestbpcd: VERBOSE = 5
[21387] <2> ConnectToBPCD: db_getCLIENT(eux290) failed: 227
[21387] <2> local_bpcr_connect: bpcr.c.278: connect_opts = 0x01000100 connect_opts2 = 0x01000100
[21387] <2> local_bpcr_connect: bpcr.c.285: connect_opts = 0x01000100
[21387] <2> local_bpcr_connect: bpcr.c.324: daemon_port_type = 0
[21387] <2> vnet_in_resilient_network: [vnet_addrinfo.c:8752] ignoring local host 0 0x0
[21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1
[21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
[21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1
[21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
[21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1
[21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
[21387] <2> vnet_pbxConnect: pbxConnectEx Succeeded
[21387] <2> do_pbx_service: [vnet_connect.c:2116] via PBX bpcd CONNECT FROM 164.129.225.67.51495 TO 164.129.225.67.1556 fd = 4

[21387] <2> async_connect: [vnet_connect.c:1433] connect immediate CONNECT FROM 164.129.225.67.51495 TO 164.129.225.67.1556 fd = 4
[21387] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO eux290 164.129.225.67 bpcd VIA pbx
[21387] <2> init_resilient_cache: [vnet_nbrntd.c:869] Initialize resilient cache. 0 0x0
[21387] <2> logconnections: BPCD CONNECT FROM 164.129.225.67.51495 TO 164.129.225.67.1556 fd = 4
[21387] <2> vnet_in_resilient_network: [vnet_addrinfo.c:8752] ignoring local host 0 0x0
[21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1

Harry_NBAD · ‎01-15-2014

[21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
[21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1
[21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
[21387] <2> vnet_pbxConnect: pbxConnectEx Succeeded
[21387] <8> do_pbx_service: [vnet_connect.c:2108] via PBX VNETD CONNECT FROM 164.129.225.67.51496 TO 164.129.225.67.1556 fd = 5
[21387] <2> async_connect: [vnet_connect.c:1433] connect immediate CONNECT FROM 164.129.225.67.51496 TO 164.129.225.67.1556 fd = 5
[21387] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO 164.129.225.67 164.129.225.67 vnetd VIA pbx
[21387] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:442] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
[21387] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string /tmp/vnet-21390389815503207813000000001-021390
[21387] <2> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:471] hash_str1 a9170aa577cf4b929de7337f6404b584

[21387] <2> bpcr_get_peername_rqst: Server peername length = 17
[21387] <2> bpcr_get_hostname_rqst: Server hostname length = 17
[21387] <2> bpcr_get_clientname_rqst: Server clientname length = 6
[21387] <2> bpcr_get_version_rqst: bpcd version: 07500004
[21387] <2> bpcr_get_platform_rqst: Server platform length = 9
[21387] <2> bpcr_get_version_rqst: bpcd version: 07500004
[21387] <2> bpcr_patch_version_rqst: theRest == > <
[21387] <2> bpcr_get_version_rqst: bpcd version: 07500004
[21387] <2> bpcr_patch_version_rqst: theRest == > <
[21387] <2> bpcr_get_version_rqst: bpcd version: 07500004

Harry_NBAD · ‎01-15-2014

VERSION = 0x07500004
PLATFORM = hpia11.31
PATCH_VERSION = 7.5.0.4
SERVER_PATCH_VERSION = 7.5.0.4
NB_MACHINE_TYPE = MASTER_SERVER
20:51:43.999 [21387] <2> vnet_in_resilient_network: [vnet_addrinfo.c:8752] ignoring local host 0 0x0
20:51:43.999 [21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1
20:51:43.999 [21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
20:51:43.999 [21387] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1
20:51:43.999 [21387] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4776] Local [strong] check, using interface ANY
20:51:44.000 [21387] <2> vnet_pbxConnect: pbxConnectEx Succeeded
20:51:44.005 [21387] <8> do_pbx_service: [vnet_connect.c:2108] via PBX VNETD CONNECT FROM 164.129.225.67.51501 TO 164.129.225.67.1556 fd = 6
20:51:44.005 [21387] <2> async_connect: [vnet_connect.c:1433] connect immediate CONNECT FROM 164.129.225.67.51501 TO 164.129.225.67.1556 fd = 6
20:51:44.005 [21387] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO 164.129.225.67 164.129.225.67 vnetd VIA pbx
20:51:44.005 [21387] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:442] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
20:51:44.068 [21387] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string /tmp/vnet-21399389815504067812000000001-021399
20:51:44.138 [21387] <2> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:471] hash_str1 b756a9bef7be9181820cc954bbd9780c
164.129.225.67:51501 -> 164.129.225.67:1556
<2>bptestbpcd: EXIT status = 0
20:51:44.143 [21387] <2> bptestbpcd: EXIT status = 0

revarooo · ‎01-15-2014

Well that;s unlikely to fail when your running it from the client itself to itself:

CONNECT FROM 164.129.225.67.51495 TO 164.129.225.67.1556 fd = 4

Run it from the media server to the client

VOX

"EXIT STATUS 25: cannot connect on socket" while initiating a restore.