Date: Thu, 06 Sep 2018 20:00:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231193] ntpd peers stuck in INIT status when using local named Message-ID: <bug-231193-227-IkgvD3G8jq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231193-227@https.bugs.freebsd.org/bugzilla/> References: <bug-231193-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231193 Ian Lepore <ian@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |ian@FreeBSD.org Status|New |Open --- Comment #2 from Ian Lepore <ian@FreeBSD.org> --- (In reply to ml from comment #0) It's not clear to me that it's ntpd having trouble resolving those names. = The name resolution errors in the log are from ntpdate, not ntpd. When the pee= rs are stuck in INIT state, what is the output from "ntpq -np"? That will show for sure whether the addresses are resolved. That ntpq output looks to me = more like the names are resolved but UDP packets to or from port 123 are being blocked somehow. Oh, hmm... after looking again it looks like the names may not be resolved = when ntpd processes the config file (I just noticed the errors about restrict), = but then they do resolve by time the peer configuration happens, so you end up = with resolved peers who can't communicate because the restrict statements that w= ould have allowed communications with them never got processed. I think waiting for named to be ready is the only viable fix, and I agree w= ith you that the ability to have an optional timeout for that wait is also important. IMO, dougb was wrong to reject the changes in bug 144400, and I think I'll look into re-opening that and fixing it. But I can't make any promises that it'll get into 12.0-RELEASE, I'm really busy these days. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231193-227-IkgvD3G8jq>