https://www.google.com.au/search?q=Connect()+failed+for+backend+no+free+ports
On Wed, 19 Sep 2018 at 12:32, Shishir Kumar Yadav
wrote:
> I am able to get logs and I see these errors -
>
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[569]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[569]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[569]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[569]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[569]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[569]: :::
> 10.21.214.31:39846 [18/Sep/2018:23:39:22.405] haproxy-frontend
> ir-http-server-backend/server1 0/0/-1/-1/0 503 212 - - SC-- 16/15/13/13/3
> 0/0 "GET
> /splunk-data/puretest/db/f2/63/1~DFFEABF3-6CE0-4107-88E9-DAC84082BE3A/guidSplunk-DFFEABF3-6CE0-4107-88E9-DAC84082BE3A/1536613068-1536610572-12314536523543509297.tsidx
> HTTP/1.1"
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: Connect() failed for
> backend ir-http-server-backend: no free ports.
> 2018-09-18 23:39:22+00:00 127.0.0.1 haproxy[572]: :::
> 10.21.214.31:39840 [18/Sep/2018:23:39:22.405] haproxy-frontend
> ir-http-server-backend/server1 0/0/-1/-1/0 503 212 - - SC-- 36/36/33/33/3
> 0/0 "GET
> /splunk-data/puretest/db/f2/63/1~DFFEABF3-6CE0-4107-88E9-DAC84082BE3A/guidSplunk-DFFEABF3-6CE0-4107-88E9-DAC84082BE3A/splunk-autogen-params.dat
> HTTP/1.1"
>
>
> My sysctl port range is -
>
> net.ipv4.ip_local_port_range = 32768 61000
>
>
> On Tue, Sep 18, 2018 at 10:20 AM, Shishir Kumar Yadav <
> shis...@purestorage.com> wrote:
>
>> Thanks Lucas.
>>
>> I am trying to enable the logging. Will provide the logs when it is
>> available.
>>
>> The default value 2000 is much higher to cause problem as I am seeing
>> problem at 250 connections.
>>
>> -Shishir
>>
>> On Tue, Sep 18, 2018 at 2:40 AM, Lukas Tribus wrote:
>>
>>> Hello,
>>>
>>>
>>> On Tue, 18 Sep 2018 at 02:36, Shishir Kumar Yadav
>>> wrote:
>>> >
>>> > Hi All,
>>> >
>>> > I am using haproxy 1.8.3
>>>
>>> Which has 169 unfixed bugs:
>>> http://www.haproxy.org/bugs/bugs-1.8.3.html
>>>
>>> I'd strongly suggest you use latest stable, although that doesn't mean
>>> it has something to do with your specific issue.
>>>
>>>
>>>
>>> > I am testing a setup where a bunch of clients are generating number of
>>> GET
>>> > requests and when number of connection reaches somewhere around 250,
>>> > the clients intermittently get 503 Service Unavailable error.
>>>
>>> Looking at the haproxy logs is the logical next step. They will most
>>> likely contain the reason for this 503 error.
>>>
>>>
>>> Also note that when you *not* set maxconn, the default value of 2000
>>> applies (per process and per frontend, not per server).
>>>
>>>
>>>
>>> Lukas
>>>
>>
>>
>
