FW: Critical: .\socket.c:640: REQUIRE(sock->hEvent != ((void *)0)) failed, general: critical: exiting (due to assertion failure)

[Tim Rutherford]

FYI this has not happened again since we upgraded to 9.5.1b1  

> -----Original Message-----
> From: Danny Mayer [mailto:mayer at gis.net] 
> Sent: Tuesday, August 05, 2008 12:01 AM
> To: timrutherford at c4.net
> Cc: comp-protocols-dns-bind at isc.org
> Subject: Re: FW: Critical: .\socket.c:640: 
> REQUIRE(sock->hEvent != ((void *)0)) failed, general: 
> critical: exiting (due to assertion failure)
> 
> Tim Rutherford wrote:
> > We are seeing this in our event logs as well when the 
> service crashes -
> > Windows 2003 running 9.5.0-P1 
> > 
> > First 
> > 
> > 	..\mem.c:1716: INSIST(mpctx->freecount > 0) failed 
> > 
> > Second 
> > 
> > 	exiting (due to assertion failure)
> > 
> > Third 
> > 
> > 	Faulting application named.exe, version 0.0.0.0, faulting module
> > named.exe, version 0.0.0.0, fault address 0x0001113f. 
> > 
> > 
> > We are using split views if that is relevant. 
> > 
> > Thanks,
> > Tim
> > 
> 
> Apparently you ran out of memory too.
> 
> Danny
> > -----Original Message-----
> > From: bind-users-bounce at isc.org 
> [mailto:bind-users-bounce at isc.org] On Behalf
> > Of Ian Tait
> > Sent: Thursday, July 24, 2008 5:58 AM
> > To: comp-protocols-dns-bind at isc.org
> > Subject: RE: Critical: .\socket.c:640: REQUIRE(sock->hEvent 
> != ((void *)0))
> > failed, general: critical: exiting (due to assertion failure)
> > 
> > Hi,
> > 
> > I'll try that again, as outlook got a bit quick on the mark,
> > 
> > On a windows 2000 machine, with the latest beta, I get 
> > 
> > .\socket.c:640: REQUIRE(sock->hEvent != ((void *)0)) failed 
> > 
> > and then 'exiting (due to assertion failure)
> > 
> > Just FYI.
> > 
> > Thanks,
> > 
> > Ian
> > 
> >> -----Original Message-----
> >> From: Ian Tait 
> >> Sent: 24 July 2008 10:56
> >> To: comp-protocols-dns-bind at isc.org
> >> Subject: RE: Critical: .\socket.c:640: REQUIRE(sock->hEvent 
> >> != ((void *)0)) failed, general: critical: exiting (due to 
> >> assertion failure)
> >>
> >> Hi,
> >>
> >> On a windows 2000 machine with the latest 9.5  
> >>
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: bind-users-bounce at isc.org
> >>> [mailto:bind-users-bounce at isc.org] On Behalf Of Danny Mayer
> >>> Sent: 23 June 2008 05:16
> >>> To: Fabien V.
> >>> Cc: comp-protocols-dns-bind at isc.org
> >>> Subject: Re: Critical: .\socket.c:640: REQUIRE(sock->hEvent 
> >> != ((void 
> >>> *)0)) failed, general: critical: exiting (due to 
> assertion failure)
> >>>
> >>> Fabien V. wrote:
> >>>> Hi,
> >>>>
> >>>> I have Bind 9.5 for Windows XP.
> >>>>
> >>>> Sometimes, I have the following error occurred :
> >>>>
> >>>> general: critical: .\socket.c:640: REQUIRE(sock->hEvent != ((void
> >>>> *)0)) failed
> >>>> general: critical: exiting (due to assertion failure).
> >>>>
> >>>> Can I help from anyone ?
> >>>>
> >>>> Thank you very much and see you soon.
> >>>>
> >>>> Fabien V.
> >>> This is the second report that I have seen on this. Do 
> you have any 
> >>> dumps or have anything else in the event log? If so can you 
> >> send this 
> >>> directly to me (and not via the newsgroup)?
> >>> Which version of Windows XP service pack are you running? 
> >> Do you have 
> >>> logs of what was happening when this was triggered?
> >>> Was this after a AXFR transfer?
> >>>
> >>> I have been working on fixing this.
> >>>
> >>> Danny
> >>>
> >>>
> > 
> > 
> > 
>