Em qui., 18 de jun. de 2020 às 06:49, Anand Buddhdev
escreveu:
> On 16/06/2020 20:17, Tony Finch wrote:
>
> Hi Tony,
>
> >> 16-Jun-2020 15:21:58.815 general: Accepting TCP connection failed:
> socket is not connected
> >>
> >> What does this log message mean?
> >
> > I think this error comes from
On 16/06/2020 20:17, Tony Finch wrote:
Hi Tony,
16-Jun-2020 15:21:58.815 general: Accepting TCP connection failed: socket is
not connected
What does this log message mean?
I think this error comes from getpeername() and it can occur if the
connection is closed between accept() and getpeerna
When I got that message I had to unblock tcp port 53 on my firewall.
Jim
-Original Message-
From: bind-users On Behalf Of Anand Buddhdev
Sent: Tuesday, June 16, 2020 11:28 AM
To: bind-users
Subject: [Non-DoD Source] BIND 9.16 incoming TCP connection errors
All active links
Anand Buddhdev wrote:
>
> 16-Jun-2020 15:21:58.815 general: Accepting TCP connection failed: socket is
> not connected
>
> What does this log message mean?
I think this error comes from getpeername() and it can occur if the
connection is closed between accept() and getpeername(), which I wouldn'
Hi folks,
I'm running an authoritative server on BIND 9.16. It gets about 3500
q/s, of which around 200 q/s are over TCP. At least, this is what DSC
reports (DSC is a libpcap application sniffing traffic independent of BIND).
In my named.conf, I have set:
reserved-sockets 1000;
tcp-clients 9
5 matches
Mail list logo
