Memory Leak in Bind 9?

Mark Watts m.watts at eris.qinetiq.com
Fri Dec 8 15:39:11 UTC 2006


> After using Bind for years with the same relative configuration we
> started to see named stop responding.
>
> Looking at the logs I see this:
>
> Dec 08 01:28:53.584 general: error: timer.c:603: unexpected error:
> Dec 08 01:28:53.585 general: error: couldn't allocate event
>
> this is bind 9.2.2 on FreeBSD 4.4. I do see some other posts for the
> same issue on this list without and answer for FreeBSD 5.5.
>
> As I said this just suddenly started occurring. We have a cronjob to
> restart named twice a day to keep it living.
>
> Anyone have any ideas?
>
> Thanks,
>
> --Wes

Upgrade to BIND 9.3.2-P2 and try again.

Mark.

-- 
Mark Watts BSc RHCE MBCS
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services Group
GPG Public Key ID: 455420ED




More information about the bind-users mailing list