Arch Linux

train_wreck

Member

Registered: 2011-10-22

Posts: 97

any idea what happened with this BIND crash?

May 15 23:06:57 SERVER named[6630]: mem.c:1298: REQUIRE(ptr != ((void *)0)) failed, back trace
May 15 23:06:57 SERVER named[6630]: #0 0x433afd in ??
May 15 23:06:57 SERVER named[6630]: #1 0x7fa24887215a in ??
May 15 23:06:57 SERVER named[6630]: #2 0x7fa2488871bf in ??
May 15 23:06:57 SERVER named[6630]: #3 0x7fa2491fc0b4 in ??
May 15 23:06:57 SERVER named[6630]: #4 0x7fa2491a6a0a in ??
May 15 23:06:57 SERVER named[6630]: #5 0x7fa24918c5d0 in ??
May 15 23:06:57 SERVER named[6630]: #6 0x7fa24918c734 in ??
May 15 23:06:57 SERVER named[6630]: #7 0x7fa249203090 in ??
May 15 23:06:57 SERVER named[6630]: #8 0x7fa24921270b in ??
May 15 23:06:57 SERVER named[6630]: #9 0x7fa2488944dc in ??
May 15 23:06:57 SERVER named[6630]: #10 0x7fa2484460a2 in ??
May 15 23:06:57 SERVER named[6630]: #11 0x7fa247c0fd1d in ??
May 15 23:06:57 SERVER named[6630]: exiting (due to assertion failure)
May 15 23:06:58 SERVER systemd[1]: named.service: main process exited, code=killed, status=6/ABRT
May 15 23:06:58 SERVER rndc[6638]: rndc: connect failed: 127.0.0.1#953: connection refused
May 15 23:06:58 SERVER systemd[1]: named.service: control process exited, code=exited status=1
May 15 23:06:58 SERVER systemd[1]: Unit named.service entered failed state.
May 15 23:06:58 SERVER systemd-coredump[6636]: Process 6630 (named) dumped core.

out of the blue, bind crashed on this internal caching/forwarding BIND nameserver. all attempts to restart it would immediately result in the same exact error output, and the only solution was to reboot the server. haven't seen it since.

just a spurious error?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,432

Re: any idea what happened with this BIND crash?

https://bugs.archlinux.org/task/40304