On 13.04.20 21:07, sth...@nethelp.no wrote:
>> general: error: TCP connection failed: quota reached
>
> I had some of these too, until I explicitly set this named option:
>
> tcp-listen-queue 20;
>
> Looks like the default is 10. The way I interpret this parameter is
> that this sets the *oper
> I believe this problem should be fixed in 9.16.1:
>
> 5361. [bug] named might not accept new connections after
> hitting tcp-clients quota. [GL #1643]
>
> However, we had two authoritative name servers running 9.16.1 which
> stopped accepting new TCP connections
Hello all,
I believe this problem should be fixed in 9.16.1:
5361. [bug] named might not accept new connections after
hitting tcp-clients quota. [GL #1643]
However, we had two authoritative name servers running 9.16.1 which
stopped accepting new TCP connection
On 3/5/20 4:34 AM, Ondřej Surý wrote:
>> On 5 Mar 2020, at 10:11, Arsen STASIC wrote:
>>
>> Hi,
>>
>> Bind 9.16 was installed on 3/2 15:45 and tcp connections ramped up to
>> maximum:
>> rndc status | grep -i tcp
>> tcp clients: 102/150
>> TCP high-water: 150
>>
>> Switching back to bind 9.
Hi Arsen,
we think you are hitting a problem that was reported to us earlier. Since it
has been now circulated on the bind-users, we made the merge request public:
https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/3163
and patch:
https://gitlab.isc.org/isc-projects/bind9/-/merge_reque
Hi,
Bind 9.16 was installed on 3/2 15:45 and tcp connections ramped up to maximum:
rndc status | grep -i tcp
tcp clients: 102/150
TCP high-water: 150
Switching back to bind 9.14 on 3/4 15:45 shows "normal" tcp client behavior:
rndc status | grep -i tcp
tcp clients: 29/150
TCP h
6 matches
Mail list logo
