From owner-freebsd-questions@freebsd.org Sun Aug 26 23:09:57 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A3001085ED8 for ; Sun, 26 Aug 2018 23:09:57 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6F09754FE for ; Sun, 26 Aug 2018 23:09:56 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 62DAC34A; Sun, 26 Aug 2018 19:09:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 26 Aug 2018 19:09:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=XhtxxpfDN/h2nNibXENo636JOIIg3 tOcBkCNvFV8Eqs=; b=SPuNPs8fasir60nR57AnXY9fISkP+bg4ooO9V87RjMAbk oXcwh07c+PLv0XlNG+PVj/aatkQjwyxuebBqfYDOvZsgDfjCOhL7WTO4NMOphnGg 6n1FcR+/IIzpFUQsZyZa3kDyTpjikmsFRxnDEDBLDzo1SFEYn/I0EtArz/1GEntc X3wyIpA8b7StR4XZ4BIP4cP8Q/FhP4l2dNM878tfdXJ7+mIGCtonWFbJjqz0dPdB u/9VoKYXBhyTRfS9seuYMEqCtNe1x22SiGL0B+5ReUP3DHOe03K5SwOX9pXiwEVH i5ANgL3252yXXfh6MvWMJUz2r2Z1Fp8Rr8J7o+vXg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Xhtxxp fDN/h2nNibXENo636JOIIg3tOcBkCNvFV8Eqs=; b=n6J1AOOQt4D8Hyp6uwrFry 20c49nApdOPFsAIaCdLZJBJyUuqiPmXuojQ8Y6R8Ut3/mij7WZvbhlK8yGlxK/Nq LnpzNRa6QBjBSsvzMTtleeX3dX4QJgW1ymoe31KwPpgdzWQUfft3jlDuVZTIeZsX 3LDqUqONoRE3nF7KkeZMU+3lorN/qLEQlAfugcGUy/WPMa48ia/5llYE+lppBM1I 5S0VEpG+UMZ6cKKo/YBp3Jeq6+84tc7eosugla+PTNDKy3kn2cvYjXNnW2Fe1gc6 ZBdSW3JYBDuJuuXdISFRdTNbzERoTK/1H/6MmK6nSbzWt5Tq6yvRDqWt1SGTlqiQ == X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.2] (unknown [94.233.224.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 63FF11028C; Sun, 26 Aug 2018 19:09:47 -0400 (EDT) Subject: Re: named and ntpd start order in rc.d To: Andrea Venturoli , freebsd-questions@freebsd.org References: From: Yuri Pankov Message-ID: Date: Mon, 27 Aug 2018 02:09:44 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2018 23:09:57 -0000 Andrea Venturoli wrote: > Hello. > > I'm in the same situation described in this bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129146 > > ntpd starts when named is not yet running, fails to resolve its peers > and never works again until I restart it manually. This seems to be a real bug here. Sometimes I'm seeing the ntpd whining about resolve failures on start when I'm doing network maintenance, but I have never checked if it operates correctly once the nameservers are back. Did you look into *why* it never works again, and how exactly it doesn't work -- it still seems to be running and spamming console while it's unable to resolve? > That bug (of the 7.0 era) was closed as fixed, since /etc/rc.d/ntpd > requires ntpdate, which in turn required named. > However, the latest statement is not true anymore, today (probably due > to the fact that named is no longer in base). > > I guess I'm not the only one who has this problem and I wonder how > others are solving this issue. > Also, should I add a comment to that bug or open a new one?