Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error after upgrading to 9.7.1-p2 windows 2k3 VMWare ESX

42 views
Skip to first unread message

Chiesa Stefano

unread,
Aug 13, 2010, 3:25:42 AM8/13/10
to bind-...@lists.isc.org
Hello all.
Our Bind installaton is on a virtual VMWare ESX W2k3 server.
I've just upgraded our public primary dns server from 9.6.0-p1 to
9.7.1-p2.
After more or less 15 minutes of work the following messages appear in
the log:

13-Aug-2010 9:09:39.305 general: error: .\socket.c:2444: unexpected
error:
13-Aug-2010 9:09:39.305 general: error: SOCKET_RECV: Windows error code:
1236, returning ISC error 54
13-Aug-2010 9:09:39.430 general: error: .\socket.c:2444: unexpected
error:
13-Aug-2010 9:09:39.430 general: error: SOCKET_RECV: Windows error code:
1236, returning ISC error 54

I read around that it could be a BIND bug, or a problem in the Windows
registry.
Can some of you tell me something more certain and, if it is possible,
how to solve it?

Thanks in advance.
Have a nice day.

Stefano Chiesa.

----------------------------------------
Stefano Chiesa
Wolters Kluwer Italia
Strada 1, Palazzo F6
20090 Milanofiori Assago (Mi) - Italia
Phone +39 0282476279 (20279 Voip)
Fax +39 0282476633

Danny Mayer

unread,
Aug 16, 2010, 12:01:10 AM8/16/10
to Chiesa Stefano, bind-...@lists.isc.org
On 8/13/2010 3:25 AM, Chiesa Stefano wrote:
> Hello all.
> Our Bind installaton is on a virtual VMWare ESX W2k3 server.
> I've just upgraded our public primary dns server from 9.6.0-p1 to
> 9.7.1-p2.
> After more or less 15 minutes of work the following messages appear in
> the log:
>
> 13-Aug-2010 9:09:39.305 general: error: .\socket.c:2444: unexpected
> error:
> 13-Aug-2010 9:09:39.305 general: error: SOCKET_RECV: Windows error code:
> 1236, returning ISC error 54
> 13-Aug-2010 9:09:39.430 general: error: .\socket.c:2444: unexpected
> error:
> 13-Aug-2010 9:09:39.430 general: error: SOCKET_RECV: Windows error code:
> 1236, returning ISC error 54
>
> I read around that it could be a BIND bug, or a problem in the Windows
> registry.
> Can some of you tell me something more certain and, if it is possible,
> how to solve it?
>

It's a bug in the BIND code. It's a nuisance more than a problem since
it appears to not affect the running of the code. There is a fix in
process of being reviewed for this. BIND 9.7.x appears to have become
much more aggressive with issuing cancels which is why you are seeing
this error show up in the logs.

Danny

0 new messages