[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 24 Jun 2024 14:16:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279950 Bug ID: 279950 Summary: dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: bob@vesterman.com CC: jaap@NLnetLabs.nl CC: jaap@NLnetLabs.nl Flags: maintainer-feedback?(jaap@NLnetLabs.nl) I recently updated dns/nsd (to version 4.10 on 13.3-RELEASE-p3), and now it just doesn't respond to requests (neither DNS lookups nor "service nsd stop"). I've noticed that there are actually two nsd processes with different names, main and xfrd: # ps aux -ww | grep nsd nsd 2552 99.9 0.1 50156 38700 - R 10:00 0:29.78 nsd: main (nsd) nsd 2094 0.0 0.0 68952 9404 - Is 10:00 0:00.07 nsd: xfrd (nsd) Both of these start up whenever I do a "service start nsd". I don't remember ever having seen xfrd before, though I imagine I could've easily overlooked it in the past. As you can see, the "main" is running at or near 100% CPU; this seems to continue forever (hours, at the very least). I have rebooted, I have uninstalled/reinstalled, uninstalled/rebuilt/reinstalled, and even uninstalled/rebuilt absolutely everything/reinstalled. Nothing I've tried so far has helped. -- You are receiving this mail because: You are the assignee for the bug.