"Re:
> Contents of bind-users digest..."
>
>
> Today's Topics:
>
> 1. Accepting TCP connection failed: socket is not connected
> (sami.ra...@sofrecom.com)
> 2. Re: Accepting TCP connection failed: socket is not connected
> (Ond?ej Sur?)
>
managing the list at
bind-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific than "Re:
Contents of bind-users digest..."
Today's Topics:
1. Accepting TCP connection failed: socket is not connected
(sami.ra...@sofrecom.com
On Thu, 2024-07-11 at 21:25 +0200, Ondřej Surý wrote:
> It means what it says - the networking layer reports that the TCP socket is
> no longer connected at the time named is accepting the connection. It means
> that the client gave up between the 3-way handshake completion and accepting
> the
olver
> server BIND 9.16.48 running on Red Hat 7 as the operating system.
>
> Log :
> 07-Jul-2024 07:06:35.746 Accepting TCP connection failed: socket is not
> connected
> 07-Jul-2024 07:07:29.724 Accepting TCP connection failed: socket is not
> connected
>
>
Hello community,
Could someone please help me understand these errors in the log of a resolver
server BIND 9.16.48 running on Red Hat 7 as the operating system.
Log :
07-Jul-2024 07:06:35.746 Accepting TCP connection failed: socket is not
connected
07-Jul-2024 07:07:29.724 Accepting TCP
5 matches
Mail list logo