Arch Linux

nickeP

Member

From: Sweden

Registered: 2024-07-09

Posts: 3

named crashes after the latest libuv update

Hi,

Since updating my system this morning, named and nslookup are crashing on my system.

Feb 11 09:40:11 arch-raspi named[444]: named: src/unix/udp.c:292: uv__udp_recvmsg: Assertion `handle->recv_cb != NULL' failed.
Feb 11 09:40:11 arch-raspi systemd-coredump[626]: [?] Process 444 (named) of user 40 dumped core.
Feb 11 09:40:11 arch-raspi systemd[1]: named.service: Main process exited, code=dumped, status=6/ABRT
Feb 11 09:40:11 arch-raspi systemd[1]: named.service: Failed with result 'core-dump'.
Feb 11 09:40:11 arch-raspi systemd[1]: named.service: Consumed 1.184s CPU time over 2min 8.175s wall clock time, 179M memory peak.

# pacman -Q |grep bind
bind 9.20.18-1

This morning the libuv package got updated which is an dependency to bind. I suspect that the bind package needs to be recompiled.

Regards
Nikolay

nickeP

Member

From: Sweden

Registered: 2024-07-09

Posts: 3

Re: named crashes after the latest libuv update

I downgraded the package libuv (1.52.0-1 => 1.51.0-1) and now named no longer crashes.

hkoch

Member

Registered: 2016-05-10

Posts: 5

Re: named crashes after the latest libuv update

I downgraded the package libuv (1.52.0-1 => 1.51.0-1) and now named no longer crashes.

This also worked for me. Thank you!

bigfreak

Member

Registered: 2019-01-04

Posts: 4

Re: named crashes after the latest libuv update

same here  downgrade the libuv works!

just4arch

Member

Registered: 2023-01-07

Posts: 121

Re: named crashes after the latest libuv update

This has been reported Upstream, so let's hope there will be an update soon or Arch backports it.

drankinatty

Member

From: Nacogdoches, Texas

Registered: 2009-04-24

Posts: 94

Website

Re: named crashes after the latest libuv update

Here is the upstream libuv bug: https://github.com/libuv/libuv/issues/5030

I pulled my hair out trying to find the cause. In this case, glad to know I was not alone... Hope the fix arrives soon.

---

David C. Rankin, J.D.,P.E.

pohl5434

Member

Registered: 2024-07-01

Posts: 3

Re: named crashes after the latest libuv update

Currently running bind single threaded on just one core. I had no luck downgrading libuv to 1.51

/usr/bin/named -f -u named -n 1

Seems to be an issue in libuv with thread synchronization on high load

drankinatty

Member

From: Nacogdoches, Texas

Registered: 2009-04-24

Posts: 94

Website

Re: named crashes after the latest libuv update

Hell of a week. The libuv folks are still working on a fix. We provided journal entries and coredumpctl info. They have also isolated a dig command that will trigger the named crash every time, so I suspect a libuv fix will be forthcoming. Arch released a updated bind 9.20.20-1 that mitigates the crashes with libuv 1.52.0 (at least I haven't had one yet). This on top of mdadm 4.5 that prevented RAID1 arrays from being assembled with the latest Arch 6.18.13 kernel. (I was lucky enough to be caught by that too) The just released mdadm 4.5-2 package fixes that issue as well. Let's hope this is the end of the core-server and boot crashes we see for a while. The recovery (emergency) console staring back at you is never a comforting site...

---

David C. Rankin, J.D.,P.E.