Jump to content

TCP connect errors connecting from proxy to broker

p4broker TCP connect errors

  • Please log in to reply
1 reply to this topic

#1 nuadhu2



  • Members
  • Pip
  • 2 posts

Posted 01 August 2018 - 01:44 PM

We're running p4 2012.2  p4 proxy connecting to 2015.2 p4 broker (yeah, need to upgrade).  I occasionally see a spike in errors from p4 clients connecting to the proxy:

Proxy unable to communicate with remote server:
"TCP connect to ... Cannot assign requested address"

The proxy and broker are CentOS 6.8 Linux VMs.   I've applied the following tweaks based on recommendations I gleaned from googling related to high number of TIME_WAIT reported by netstat -a.

net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_tw_recycle = 1

This seemed to help somewhat but did not completely resolve the problem.  I suspect the TCP connect errors are  due to spike in number of p4 clients hitting the proxy/broker around the same time.  I'm not sure what else to try to address this problem.

Any suggestion on how to tune other parameters to mitigate these transient TCP connect errors is greatly appreciated.

#2 Dave Foglesong

Dave Foglesong


  • Members
  • PipPip
  • 12 posts

Posted 01 August 2018 - 08:00 PM

You might be exhausting the dynamic port range. I've had this happen on Perforce servers before, but don't recall if that was the exact error message I got when it happened.

There's a decent overview of how to check and change this setting here:


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users