bind9: assertion error about 13 seconds after security upgrade
I applied yesterday's bind9 security upgrade on my long stable DNS
server and about 13 seconds later (right after all zones are loaded)
I see the following in my logs:
Mar 19 00:10:40 jitterbug named[3492]: ../../../lib/dns/name.c:2487: REQUIRE((((dest) != ((void *)0)) && (((const isc__magic_t *)(dest))->magic == ((('D') << 24 | ('N') << 16 | ('S') << 8 | ('n')))))) failed, back trace
Mar 19 00:10:40 jitterbug named[3492]: #0 0x484457 in ??
Mar 19 00:10:40 jitterbug named[3492]: #1 0xb79407c5 in ??
Mar 19 00:10:40 jitterbug named[3492]: #2 0xb7ddbd02 in ??
Mar 19 00:10:40 jitterbug named[3492]: #3 0xb7e5dd1c in ??
Mar 19 00:10:40 jitterbug named[3492]: #4 0xb7e601df in ??
Mar 19 00:10:40 jitterbug named[3492]: #5 0xb7e60a3b in ??
Mar 19 00:10:40 jitterbug named[3492]: #6 0xb7965f04 in ??
Mar 19 00:10:40 jitterbug named[3492]: #7 0xb790e27a in ??
Mar 19 00:10:40 jitterbug named[3492]: #8 0xb75d0366 in ??
Mar 19 00:10:40 jitterbug named[3492]: exiting (due to assertion failure)
Mar 19 00:10:40 jitterbug systemd[1]: bind9.service: Main process exited, code=killed, status=6/ABRT
Mar 19 00:10:40 jitterbug rndc[3544]: rndc: connect failed: 127.0.0.1#953: connection refused
Mar 19 00:10:40 jitterbug systemd[1]: bind9.service: Control process exited, code=exited status=1
Mar 19 00:10:40 jitterbug systemd[1]: bind9.service: Unit entered failed state.
Mar 19 00:10:40 jitterbug systemd[1]: bind9.service: Failed with result 'signal'.
After attempting to stop/start or restart several times, I decided to
downgrade and bind9 became stable once again.
I applied the bind9 security upgrade on several other systems. I
have not noticed a problem on any of them (some LTS, some Buster,
some Bullseye). So it must be something in my complex environment that
triggers a bug that doesn't affect most environments.
--
CJ Fearnley | LinuxForce Inc.
cjf@LinuxForce.net | Hosting and Linux Consulting
https://www.LinuxForce.net | https://blog.LinuxForce.net
Reply to: