Arch Linux

rossboulet

Member

Registered: 2017-12-13

Posts: 49

[SOLVED] named from bind package core dumping

After an upgrade last night, named began to fail and core dump within a few seconds after starting. I'm running kernel 5.6.4-arch1 and had to go back to bind-9.16.0-1.1-pentium4 and bind-tools-9.16.0-1.1-pentium4 to get it to run.

What other information do I need to supply? If it makes a difference, it is running in a VM with qemu under an Arch host.

Last edited by rossboulet (2020-04-29 04:06:17)

abaumann

Administrator

From: Zurich

Registered: 2019-11-14

Posts: 1,042

Website

Re: [SOLVED] named from bind package core dumping

Hi, part of the logfile would be helpful. I checked for trivial things, but I'm afraid
it crashes with a certain configuration or with certain zones files..

deep42thought

Administrator

From: Jena, Germany

Registered: 2017-06-17

Posts: 617

Re: [SOLVED] named from bind package core dumping

fwiw: bind 9.16.2-1.0 on i486 runs fine with my non-trivial config.

rossboulet

Member

Registered: 2017-12-13

Posts: 49

Re: [SOLVED] named from bind package core dumping

I tried running named in the foreground and watched. Within a minute, it would fail with "netmgr.c:1000: REQUIRE(worker->recvbuf_inuse) failed, back trace". The failure was sometimes in a few seconds and sometimes more, but always within a minute.
I ran across this post when I searched for the error: https://www.mail-archive.com/freebsd-cu … 80444.html which mentions libuv as the culprit. Sure enough, libuv had been upgraded from 1.35 to 1.36 in the same pass as bind. Another update to libuv (1.37) was added today. I've upgraded to it and bind has been running for 22 minutes with no errors. If it stays solid for 24 hours, I'll come back and marked this solved.

Last edited by rossboulet (2020-04-27 19:54:33)