Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Not able to communicate the master serve from media server

Created: 13 Dec 2012 • Updated: 13 Feb 2014 | 22 comments
This issue has been solved. See solution.

Hi Forum members

 

I am bulding a netbackup test environment and experiencing an issue "Media server not able to communicate the master server.."

The current environment is as follows.

NBU version -- 7.1

Master server -- Solaris 10 X86

Media server  --Win 2008 X64

Here is some output which I tried from master to media and media to master...

Master Server:-

bash-3.00# bpclntcmd -hn WIN-NBUMEDASER1
host WIN-NBUMEDASER1: WIN-NBUMEDASER1 at 192.168.100.41
aliases: WIN-NBUMEDASER1 192.168.100.41
bash-3.00# bpgetconfig -M WIN-NBUMEDASER1 >/tmp/bp.conf.WIN-NBUMEDASER1

bash-3.00# bpclntcmd -ip 192.168.100.41
host 192.168.100.41: WIN-NBUMEDASER1 at 192.168.100.41
aliases:     WIN-NBUMEDASER1     192.168.100.41

 

Media Server:-

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn Solaris10-NBUMaster
client hostname could not be found
alter client: Solaris10-NBUMaster : not found. (48) (Getting this error )

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 192.168.100.80
host 192.168.100.80: 192.168.100.80 at 192.168.100.80
aliases:     192.168.100.80

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -server Solaris10-NBUMaster
client hostname could not be found
alt master: Solaris10-NBUMaster not found. (48)

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -is_master_server win-nbumedaser1
win-nbumedaser1 is not a master server

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -is_master_server Solaris10-NBU
Master
Solaris10-NBUMaster is a master server

 

Media server Process:

C:\Program Files\Veritas\NetBackup\bin>bpps
* WIN-NBUMEDASER1                                       12/12/12 12:28:31.890
COMMAND           PID      LOAD             TIME   MEM                  START
vnetd            1504    0.000%            0.062  6.3M  12/12/12 12:02:37.969
bpinetd          2776    0.000%            0.062  8.6M  12/12/12 12:02:38.031
bpcd             1284    0.000%            0.031  7.3M  12/12/12 12:02:38.219
vmd              1400    0.000%            0.187   13M  12/12/12 12:02:41.375
ltid              972    0.000%            0.093   14M  12/12/12 12:02:41.656
nbrmms           2184    0.000%            0.640   25M  12/12/12 12:02:41.750
bpcompatd        1848    0.000%            0.031   11M  12/12/12 12:02:45.328
nbsl              524    0.000%            0.531   27M  12/12/12 12:02:45.390
nbsvcmon         1056    0.000%            0.171   17M  12/12/12 12:03:20.625
bpps             2992    0.000%            0.078  5.9M  12/12/12 12:28:30.812

Any help would be greatly appreciated.

Regards

APJKL
 

Comments 22 CommentsJump to latest comment

Marianne's picture

You have 2 choices:

  1. Add your Solaris server to the Windows DNS
  2. Add hosts entry on the media server for the master (seems you already have hosts entry on the master for the media server)

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
APJAK's picture

Hi Marianne,

 

This is a test environment and I don't have DNS setup.

I have added the master and media server details in the /etc/hosts file in both master and media servers.

Marianne's picture

Double check C:\Windows\System32\drivers\etc\hosts entry on media server. Possible incorrect entry?

Status 48 says 'hostname could not be found'.

Can you ping Solaris10-NBUMaster from the media server?

(Hopefully you have disabled UAC on the Windows media server?)

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

APJAK's picture

HI Marianne,

 

Thanks I have resolved the hosts entry issue, now I am able to ping the host from master and media servers and do the bpclntcmd from master and media servers, but still when I click the media server I am getting the error "cannot connect to socket"

I have read one of the topic in the forum posted by Roger.G "NetBackup 7.x Communication between Master & Media Server". I have followed your suggestions and attaching the logs

 

bash-3.00# bptestbpcd -host WIN-NBUMEDASER1 -verbose
<16>bptestbpcd main: Function ConnectToBPCD(WIN-NBUMEDASER1) failed: 25
cannot connect on socket
##Attaching the master server bpcd logs

Forward and reverse hostname lookup in both directions:

Master server:

bash-3.00# bpclntcmd -hn WIN-NBUMEDASER1
host WIN-NBUMEDASER1: WIN-NBUMEDASER1 at 192.168.100.41
aliases:     WIN-NBUMEDASER1     192.168.100.41

Media server:-

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn Solaris10-NBUMaster
host Solaris10-NBUMaster: Solaris10-NBUMaster at 192.168.100.80
aliases:     Solaris10-NBUMaster     192.168.100.80

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 192.168.100.80
host 192.168.100.80: Solaris10-NBUMaster at 192.168.100.80
aliases:     Solaris10-NBUMaster     192.168.100.80

 

 

 

AttachmentSize
mastererverbpcdlog.zip 21.15 KB
mediaserverbpcdlog.txt 3.14 KB
APJAK's picture

bash-3.00# bptestbpcd -host WIN-NBUMEDASER1 -verbose -debug
15:08:58.014 [14805] <2> bptestbpcd: VERBOSE = 0
15:12:42.700 [14805] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:12:54.729 [14805] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:13:06.760 [14805] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:13:59.189 [14805] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 301 0x0000012d
15:13:59.189 [14805] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 301 0x0000012d
15:13:59.189 [14805] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 301 0x0000012d
15:13:59.190 [14805] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
15:13:59.190 [14805] <2> vnet_connect_to_bpcd: ../../libvlibs/vnet_connect.c.237: 0: connect_to_service() failed: 18 0x00000012
15:13:59.190 [14805] <2> local_bpcr_connect: Can't connect to client WIN-NBUMEDASER1
15:13:59.190 [14805] <2> ConnectToBPCD: bpcd_connect_and_verify(WIN-NBUMEDASER1, WIN-NBUMEDASER1) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(WIN-NBUMEDASER1) failed: 25
15:13:59.190 [14805] <16> bptestbpcd main: Function ConnectToBPCD(WIN-NBUMEDASER1) failed: 25
<2>bptestbpcd: cannot connect on socket
15:13:59.190 [14805] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
15:13:59.190 [14805] <2> bptestbpcd: EXIT status = 25
cannot connect on socket
 

Marianne's picture

Have you disabled Windows Firewall on the Media server? 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

APJAK's picture

Yes, I have disabled the windows firewall in the media server, still getting the same error..

bash-3.00# bptestbpcd -host WIN-NBUMEDASER1 -verbose
<16>bptestbpcd main: Function ConnectToBPCD(WIN-NBUMEDASER1) failed: 25
cannot connect on socket
 

captain jack sparrow's picture

Can you reset network connection from Switch end. also do verify netstat output.. what status does it shows to connection established in between

Presuming Ports are allowed throughout all the security layers you have in your domain (e.g. SCSP/SEP/McAfee etc.)

 

 Cheers !!!

CJS

 

APJAK's picture

Hi Jack,

This is a test environment, the windows media server is a VM, I have reset the network adapter..

This is the netstat ouput

C:\Program Files\Veritas\NetBackup\bin>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:445            WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:1556           WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:13701          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:13724          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:13782          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:47001          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:49152          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:49153          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:49154          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:49155          WIN-NBUMEDASER1:0      LISTENING
  TCP    0.0.0.0:49156          WIN-NBUMEDASER1:0      LISTENING
  TCP    127.0.0.1:1556         WIN-NBUMEDASER1:50769  ESTABLISHED
  TCP    127.0.0.1:1557         WIN-NBUMEDASER1:0      LISTENING
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:0      LISTENING
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:50722  ESTABLISHED
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:50726  ESTABLISHED
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:50740  ESTABLISHED
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:50751  ESTABLISHED
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:50760  ESTABLISHED
  TCP    127.0.0.1:49166        WIN-NBUMEDASER1:50768  ESTABLISHED
  TCP    127.0.0.1:50722        WIN-NBUMEDASER1:49166  ESTABLISHED
  TCP    127.0.0.1:50723        WIN-NBUMEDASER1:0      LISTENING
  TCP    127.0.0.1:50726        WIN-NBUMEDASER1:49166  ESTABLISHED
  TCP    127.0.0.1:50737        WIN-NBUMEDASER1:0      LISTENING
  TCP    127.0.0.1:50740        WIN-NBUMEDASER1:49166  ESTABLISHED
  TCP    127.0.0.1:50751        WIN-NBUMEDASER1:49166  ESTABLISHED
  TCP    127.0.0.1:50754        WIN-NBUMEDASER1:0      LISTENING
  TCP    127.0.0.1:50760        WIN-NBUMEDASER1:49166  ESTABLISHED
  TCP    127.0.0.1:50768        WIN-NBUMEDASER1:49166  ESTABLISHED
  TCP    127.0.0.1:50769        WIN-NBUMEDASER1:1556   ESTABLISHED
  TCP    192.168.100.41:139     WIN-NBUMEDASER1:0      LISTENING
  TCP    192.168.100.41:50797   Solaris10-NBUMaster:1556  ESTABLISHED
  TCP    192.168.100.41:50798   Solaris10-NBUMaster:ssh  ESTABLISHED
  TCP    192.168.100.41:50799   Solaris10-NBUMaster:1556  ESTABLISHED
  TCP    192.168.100.41:50800   Solaris10-NBUMaster:1556  ESTABLISHED
  TCP    [::]:135               WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:445               WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:1556              WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:47001             WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:49152             WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:49153             WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:49154             WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:49155             WIN-NBUMEDASER1:0      LISTENING
  TCP    [::]:49156             WIN-NBUMEDASER1:0      LISTENING
  TCP    [::1]:49163            WIN-NBUMEDASER1:49164  ESTABLISHED
  TCP    [::1]:49164            WIN-NBUMEDASER1:49163  ESTABLISHED
  TCP    [::1]:50734            WIN-NBUMEDASER1:50735  ESTABLISHED
  TCP    [::1]:50735            WIN-NBUMEDASER1:50734  ESTABLISHED
  TCP    [::1]:50747            WIN-NBUMEDASER1:50748  ESTABLISHED
  TCP    [::1]:50748            WIN-NBUMEDASER1:50747  ESTABLISHED
  TCP    [::1]:50756            WIN-NBUMEDASER1:50757  ESTABLISHED
  TCP    [::1]:50757            WIN-NBUMEDASER1:50756  ESTABLISHED
  TCP    [::1]:50764            WIN-NBUMEDASER1:50765  ESTABLISHED
  TCP    [::1]:50765            WIN-NBUMEDASER1:50764  ESTABLISHED
  UDP    0.0.0.0:5355           *:*
  UDP    192.168.100.41:137     *:*
  UDP    192.168.100.41:138     *:*
  UDP    [::]:5355              *:*

Marianne's picture

Your media server bpcd log does not show any connection attempt from the master.

This is what made me believe that Windows firewall may be running on the media server.

Now that you have reset network adapter, we see ESTABLISHED connection with Master:

Solaris10-NBUMaster:1556  ESTABLISHED

Have you tried bptestbpcd connection again from Master?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

captain jack sparrow's picture

Is issues arising post deployment or is intermittent. Was wondering if it was post deployment you did not got any warning of connection being interrupted (NBU does pre-check when deploying media server to ensure it reaches EMM /master)

What security application do you have at both master/media?

Do you see nbemmcmd -getemmserver and listhosts) listing this media server? (Run from master/media under admin cmd

 Cheers !!!

CJS

 

APJAK's picture

Hi Marianne

Yes I have tested the bptestbpcd connection from Master, but still it's failing

bash-3.00# bptestbpcd -host win-nbumedaser1 -verbose
<16>bptestbpcd main: Function ConnectToBPCD(win-nbumedaser1) failed: 25
cannot connect on socket
 

Hi Jack

Nbemmcmd outputs:-

Master Server:-

bash-3.00# nbemmcmd -listhosts
NBEMMCMD, Version:7.1
The following hosts were found:
server             Solaris10-NBUMaster
master             Solaris10-NBUMaster
media              win-nbumediaserver
media              win-nbumedaser1
Command completed successfully.
 

bash-3.00# nbemmcmd -getemmserver
NBEMMCMD, Version:7.1
These hosts were found in this domain: Solaris10-NBUMaster, win-nbumedaser1, win-nbumediaserver

Checking with the host "Solaris10-NBUMaster"...
Checking with the host "win-nbumedaser1"...
Checking with the host "win-nbumediaserver"...

Server Type    Host Version        Host Name                     EMM Server
MASTER         7.1                 Solaris10-NBUMaster           Solaris10-NBUMaster
<unknown>      UNKNOWN RELEASE (-2)win-nbumedaser1               <unknown>
*Failed to get the configuration for the host "win-nbumedaser1". cannot connect on socket(25)
<unknown>      UNKNOWN RELEASE (-2)win-nbumediaserver            <unknown>
*Failed to get the configuration for the host "win-nbumediaserver". client hostname could not be found(48)

One or more hosts had mismatched EMM Servers.
There were problems getting information on one or more hosts.
The consistency check either failed or was incomplete.
Command did not complete successfully.

 

 

Media Server:-

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listhosts
NBEMMCMD, Version:7.1
The following hosts were found:
server             Solaris10-NBUMaster
master             Solaris10-NBUMaster
media              win-nbumediaserver
media              win-nbumedaser1
Command completed successfully.

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -getemmserver
NBEMMCMD, Version:7.1
These hosts were found in this domain: Solaris10-NBUMaster, win-nbumedaser1, win
-nbumediaserver

Checking with the host "Solaris10-NBUMaster"...
Checking with the host "win-nbumedaser1"...
Checking with the host "win-nbumediaserver"...

Server Type    Host Version        Host Name                     EMM Server

MASTER         7.1                 Solaris10-NBUMaster           Solaris10-NBUMaster
MEDIA          7.1                 win-nbumedaser1               Solaris10-NBUMaster
<unknown>      UNKNOWN RELEASE (-2)win-nbumediaserver            <unknown>

*Failed to get the configuration for the host "win-nbumediaserver". client hostn
ame could not be found(48)

One or more hosts had mismatched EMM Servers.
There were problems getting information on one or more hosts.
The consistency check either failed or was incomplete.
Command did not complete successfully.

 

 

 

Marianne's picture

NBU is case sensitive. Seems the SERVER entry in master's bp.conf is lower case.
Case MUST match in OS and NBU config.
Please also check NBU registry entries on Windows media server.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

captain jack sparrow's picture

Out of box question

Was media server renamed ?

Please post bpcd logs

Are multiple NIC configured at either of host?

 Cheers !!!

CJS

 

APJAK's picture

Hi,

The entries in the bp.conf file and the media server name are in same case..

bp.conf file output from the master server

bash-3.00# cat /opt/openv/netbackup/bp.conf
SERVER = Solaris10-NBUMaster
CLIENT_NAME = Solaris10-NBUMaster
CONNECT_OPTIONS = localhost 1 0 2
USE_VXSS = PROHIBITED
VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY
EMMSERVER = Solaris10-NBUMaster
HOST_CACHE_TTL = 3600
VXDBMS_NB_DATA = /usr/openv/db/data
#SERVER = WIN-NBUMEDIASERVER
SERVER = WIN-NBUMEDASER1
MEDIA_SERVER = WIN-NBUMEDASER1
 

Hostname from the Client:-

C:\Program Files\Veritas\NetBackup\bin\admincmd>hostname
WIN-NBUMEDASER1

However in the media server registry I can see the media server name in lower case, I have modified the media server name to upper case in the registrey.

After changing the registrey entries I have  ran the bptestbpcd -host <media-server) and nbemmcmd -getemmserver in the master server but still getting the same errorr.

bash-3.00# nbemmcmd -getemmserver
NBEMMCMD, Version:7.1
These hosts were found in this domain: Solaris10-NBUMaster, win-nbumedaser1

Checking with the host "Solaris10-NBUMaster"...
Checking with the host "win-nbumedaser1"... ^C^D

Server Type    Host Version        Host Name                     EMM Server                                                                                                                          
MASTER         7.1                 Solaris10-NBUMaster           Solaris10-NBUMa                                                                                                                      ster
<unknown>      UNKNOWN RELEASE (-2)win-nbumedaser1               <unknown>                                                                                                                           
*Failed to get the configuration for the host "win-nbumedaser1". cannot connect                                                                                                                       on socket(25)

One or more hosts had mismatched EMM Servers.
There were problems getting information on one or more hosts.
The consistency check either failed or was incomplete.
Command did not complete successfully.

bash-3.00# bptestbpcd -host WIN-NBUMEDASER1
<16>bptestbpcd main: Function ConnectToBPCD(WIN-NBUMEDASER1) failed: 25
cannot connect on socket

 

Is there any thing I am missing?
 

Marianne's picture

We see 2 media server entries on the master: 

media              win-nbumediaserver
media              win-nbumedaser1

Seems master can now communicate with  win-nbumedaser1, but not with win-nbumediaserver.

Server Type    Host Version        Host Name                     EMM Server

MASTER         7.1                 Solaris10-NBUMaster           Solaris10-NBUMaster
MEDIA          7.1                 win-nbumedaser1               Solaris10-NBUMaster
<unknown>      UNKNOWN RELEASE (-2)win-nbumediaserver            <unknown>

*Failed to get the configuration for the host "win-nbumediaserver". client hostname could not be found(48)

Where does win-nbumediaserver fit in the picture?

It is really best to stick to lowercase and not this mix of uppercase and lowercase.

I guess lookup and connection to win-nbumedaser1 is working because you have added aliases in hosts files?

**** EDIT ****

This post was based on your previous output.

PLEASE start from scratch and stick to ONE CASE - not this mix.

I prefer to always use lowercase.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

APJAK's picture

Hi Marianne,

I hae started from scratch, built the new test env with a solaris master and windows media server.

I have disabled the windows firewall, and stick to the hostnames in lower case.

I am still getting the same issue again..please suggest me how resolve the issue..

bp.confi output from master server:-

bash-3.00# cat /opt/openv/netbackup/bp.conf
SERVER = nbumaster
CLIENT_NAME = nbumaster
CONNECT_OPTIONS = localhost 1 0 2
USE_VXSS = PROHIBITED
VXSS_SERVICE_TYPE = INTEGRITYANDCONFIDENTIALITY
EMMSERVER = nbumaster
HOST_CACHE_TTL = 3600
VXDBMS_NB_DATA = /usr/openv/db/data
SERVER = win-nbumedia
MEDIA_SERVER = win-nbumedia
 

bash-3.00# hostname
nbumaster
 

C:\Program Files\Veritas\NetBackup\bin>hostname
win-nbumedia

I have added the media server manually to emm database

bash-3.00# nbemmcmd -addhost -machinename win-nbumedia  -masterserver nbumaster -emmname nbumaster -machinetype media -operatingsystem windows -netbackupversion 7.1.0.0
NBEMMCMD, Version:7.1
Command completed successfully.

Then try to get the emmserver details, still getting the error messages...

bash-3.00# nbemmcmd -getemmserver
NBEMMCMD, Version:7.1
These hosts were found in this domain: nbumaster, win-nbumedia

Checking with the host "nbumaster"...
Checking with the host "win-nbumedia"...

Server Type    Host Version        Host Name                     EMM Server
MASTER         7.1                 nbumaster                     nbumaster
<unknown>      UNKNOWN RELEASE (-2)win-nbumedia                  <unknown>
*Failed to get the configuration for the host "win-nbumedia". cannot connect on socket(25)

One or more hosts had mismatched EMM Servers.
There were problems getting information on one or more hosts.
The consistency check either failed or was incomplete.
Command did not complete successfully.

Ran the bptestbpcd command using the verbose and debug options

bash-3.00# bptestbpcd -host win-nbumedia -verbose -debug
15:05:21.574 [6908] <2> bptestbpcd: VERBOSE = 0
15:09:06.381 [6908] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:09:18.411 [6908] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:09:30.692 [6908] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:10:24.721 [6908] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 303 0x0000012f
15:10:24.721 [6908] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 303 0x0000012f
15:10:24.721 [6908] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 303 0x0000012f
15:10:24.721 [6908] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
15:10:24.721 [6908] <2> vnet_connect_to_bpcd: ../../libvlibs/vnet_connect.c.237: 0: connect_to_service() failed: 18 0x00000012
15:10:24.721 [6908] <2> local_bpcr_connect: Can't connect to client win-nbumedia
15:10:24.721 [6908] <2> ConnectToBPCD: bpcd_connect_and_verify(win-nbumedia, win-nbumedia) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(win-nbumedia) failed: 25
15:10:24.722 [6908] <16> bptestbpcd main: Function ConnectToBPCD(win-nbumedia) failed: 25
<2>bptestbpcd: cannot connect on socket
15:10:24.722 [6908] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
15:10:24.722 [6908] <2> bptestbpcd: EXIT status = 25
cannot connect on socket
bash-3.00# bptestbpcd -host win-nbumedia -verbose -debug
14:55:51.854 [6444] <2> bptestbpcd: VERBOSE = 0
14:59:36.541 [6444] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
14:59:48.582 [6444] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:00:00.612 [6444] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt SO_ERROR returned: 145 0x00000091
15:00:53.041 [6444] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 302 0x0000012e
15:00:53.041 [6444] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 302 0x0000012e
15:00:53.041 [6444] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.978: 0: ran out of time before connect: 302 0x0000012e
15:00:53.041 [6444] <2> connect_to_service: ../../libvlibs/vnet_connect.c.382: 0: vnet_async_connect() failed: 18 0x00000012
15:00:53.041 [6444] <2> vnet_connect_to_bpcd: ../../libvlibs/vnet_connect.c.237: 0: connect_to_service() failed: 18 0x00000012
15:00:53.041 [6444] <2> local_bpcr_connect: Can't connect to client win-nbumedia
15:00:53.041 [6444] <2> ConnectToBPCD: bpcd_connect_and_verify(win-nbumedia, win-nbumedia) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(win-nbumedia) failed: 25
15:00:53.042 [6444] <16> bptestbpcd main: Function ConnectToBPCD(win-nbumedia) failed: 25
<2>bptestbpcd: cannot connect on socket
15:00:53.042 [6444] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
15:00:53.042 [6444] <2> bptestbpcd: EXIT status = 25
cannot connect on socket
 

Howerver I am able to connect to the master server using the NBU adminconsole and Java console from the media server, but not able to open the media server properties..

Thanks in Advance

APJAK

AttachmentSize
mediaserver_bpcdlog.txt 1.36 KB
epsilon22222's picture

* Host file entries correct for both master and media servers?

* Have services been restarted on master/media after you've made any changes?

* Does bpclntcmd resolve names correctly?

* Does the bp.conf entries exist for master/media servers and are correct?

Marianne's picture

Media server bpcd log contains no record of connection attempt. 

Either firewall blocking connection attempt or something wrong with Media server network interface.

Can you telnet to any ports om media server? Try pbx and vnetd.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Will Restore's picture

<unknown>      UNKNOWN RELEASE

 

valid license key installed ? 

 

Will Restore -- where there is a Will there is a way

Will Restore's picture

bptestbpcd: EXIT status = 25

 

Cause

Even though The Firewall is turned off from control panel > Windows Firewall, 

Windows Firewall Service must be stopped before the connection is sucessful.

 

Solution

Turn off Windows Firewall and completely disable Windows Firewall Service.

 


Article URL http://www.symantec.com/docs/TECH165011

Will Restore -- where there is a Will there is a way

Marianne's picture

OP stopped responding on 17 December.

I have a feeling problems were due to config problems on VMs.
We see that the following had to be done at some point:

This is a test environment, the windows media server is a VM, I have reset the network adapter..

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links