From owner-freebsd-stable@freebsd.org Tue Jul 14 13:48:43 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95E9599BB89 for ; Tue, 14 Jul 2015 13:48:43 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 750ED31A for ; Tue, 14 Jul 2015 13:48:43 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id E5DD76BB for ; Tue, 14 Jul 2015 09:43:30 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Circular dependency between local_unbound and ntpd? Message-Id: Date: Tue, 14 Jul 2015 09:43:30 -0400 To: freebsd-stable Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 13:48:43 -0000 I believe I ran afoul of a circular dependency between local_unbound and = ntpd on my 10.2-PRERELEASE system. I use a stock /etc/ntp.conf and use = ntpd_sync_on_start=3D"YES". Last night, a BIOS settings reset cause my CMOS clock to go WAY out of = synch for the first time. No problem, I thought: NTP will correct it at = boot. Wrong! When my system booted, the time was not corrected. Also, DNS resolution = was not working. I figured out it was because local_unbound relies on = an accurately set clock, but the clock could not be set accurately = because my stock ntp.conf requires working DNS resolution to reach the = NTP servers. That sounds like a potential circular dependency to me. My workaround at the time was to look up 0.freebsd.pool.ntp.org on = another system; stop ntpd; then do a ntpdate using the IP addresses to = set the clock. Once the clock was set accurately, things were all hunky = dory. Does anyone have any suggestion for an automatic way around this? I = guess one way would be to put the IP address of an NTP server into my = ntp.conf file, so at least one would be reachable without needing a = working DNS? My main concern is for those systems like my Raspberry Pi and Beaglebone = Black that don't have a battery-backed clock. I currently don't use = local_unbound on those, but it seems like I'd encounter this problem = routinely if I did. Cheers, Paul.=