cancel
Showing results for 
Search instead for 
Did you mean: 

Connection to Media Server Fails

MilesVScott
Level 6
Certified

I have been troubleshooting a connection issue to a Media Server for a day or two... The environment is:

NBU 7.1.0.3 Master Server on Win 2k3 Ent x64

NBU 7.1.0.4 Media Server on Win 2k3 Ent x64

Firewalls are disabled on both, and basic network connectivity exists(ping, nslookup, bptestbpcd(with no options), and I have checked the host files on both and the entries are corect.

 

I noticed that backups to the media server are rerouting through a different MS. I tried to go get to host properties on the MS and after a few seconds get:

"Ping failed on host [HN](IPx.x.x.x)"

I was able to get pretty far through troubleshooting and found no visable issues. Finally I came across a command that does not work:

 

bptestbpcd -client [server] -connect_options 0 1 1 -verbose

From the Media Server to the master, everything looks fine:

 

0 1 1
x.x.x.50:4783 -> x.x.x.51:1556
x.x.x.50:4784 -> x.x.x.51:1556
PEER_NAME = [Media Server]
HOST_NAME = [Master Server]
CLIENT_NAME = [Master Server]
VERSION = 0x07100000
PLATFORM = win_x64
PATCH_VERSION = 7.1.0.3 
SERVER_PATCH_VERSION = 7.1.0.3 
MASTER_SERVER = [Master Server]
EMM_SERVER = [Master Server]
NB_MACHINE_TYPE = MASTER_SERVER
 
However, when I run it from the master to the media it hangs. After ending the cmd it outputs this:
0 1 1
0.0.0.0:4921 -> x.x.x.50:13724
0.0.0.0:1037 -> x.x.x.50:1556
<16>bptestbpcd main: Function bpcr_get_peername_rqst() failed: 0
<16>bptestbpcd main: Function bpcr_new_standard_socket_rqst((null)) failed: 23
socket close failed
 
I am trying to dig through vnetd posts but am unable to find anything. If anyone has any suggestions that would be great.

 

1 ACCEPTED SOLUTION

Accepted Solutions

MilesVScott
Level 6
Certified

After troubleshooting with support the issue was the Timeout settings on the Master. Apparently these settings:

Client connect timeout - 300

Client read timeout - 300

Media server connect timeout - 30

Needed to be:

 

Client connect timeout - 1800

Client read timeout - 3600

Media server connect timeout - 150

 

Not quite sure why I need 30 mins and an hour... but I can't argue with what works. I will go back and tune those down a bit later but for now everything is working.

 

Thanks for the suggestions!

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Do you have bpcd log on the media server?

If so, please copy to bpcd.txt and post as File attachment.

MilesVScott
Level 6
Certified

Here is the most recent bpcd. Sorry about the size. They have been quite large because of the redirection of jobs.

 

Thanks,

Mark_Solutions
Level 6
Partner Accredited Certified

Way too big!

Could you try and change its file name and then connect to it from the Master again so that we get a short period of connection to analyse

The 0.0.0.0 is interesting - does the Media server have its loop back address in its hosts file? (127.0.0.0 against itself?)

Do you have short and FQDN names specified

Have you disabled domain, public and private firewalls?

MilesVScott
Level 6
Certified

Actually the log's were not even verbose 5. I will work on narrowing the logs down with more detail! :)

MilesVScott
Level 6
Certified

After troubleshooting with support the issue was the Timeout settings on the Master. Apparently these settings:

Client connect timeout - 300

Client read timeout - 300

Media server connect timeout - 30

Needed to be:

 

Client connect timeout - 1800

Client read timeout - 3600

Media server connect timeout - 150

 

Not quite sure why I need 30 mins and an hour... but I can't argue with what works. I will go back and tune those down a bit later but for now everything is working.

 

Thanks for the suggestions!