On 07/12/18 1:57 pm, David C. Rankin wrote:
All, Has anyone else encountered a bind 9.13.4-1/named daemon dying
with "assertion failure" in the past week. I have encountered the
problem twice.
Happens to me everyday (morning) from about a week or may be more.
Dec 07 07:40:47 amish named[768]: resolver.c:10484: REQUIRE(fetchp !=
((void *)0) && *fetchp == ((void *)0)) failed, back trace
Dec 07 07:40:47 amish named[768]: #0 0x55ea39e304d2 in ??
Dec 07 07:40:47 amish named[768]: #1 0x7f889343ccaa in ??
Dec 07 07:40:47 amish named[768]: #2 0x7f88935ef95b in ??
Dec 07 07:40:47 amish named[768]: #3 0x7f88935f506e in ??
Dec 07 07:40:47 amish named[768]: #4 0x7f88935f8aba in ??
Dec 07 07:40:47 amish named[768]: #5 0x7f889345c349 in ??
Dec 07 07:40:47 amish named[768]: #6 0x7f889294ba9d in ??
Dec 07 07:40:47 amish named[768]: #7 0x7f889287bb23 in ??
Dec 07 07:40:47 amish named[768]: exiting (due to assertion failure)
A simple restart makes it happy again -- but for how long?
It does not happen after I restart it, till I shutdown laptop at night.
And then next morning happens again, within an hour, after turning on
the laptop.
As per log above some kind of assertion fails. I havent bothered to find
exact reason though.
I have made only 2 changes to default named.conf that ships with Arch.
Allowed recursion and using Cloudflare as forwarder.
- allow-recursion { 127.0.0.1; };
+ allow-recursion { any; };
+ forward first;
+ forwarders { 1.0.0.1 ; 1.1.1.1 ; }; //Cloudflare
Regards,
Amish.
