From owner-freebsd-users-jp@freebsd.org Thu Jan 28 12:02:18 2016 Return-Path: Delivered-To: freebsd-users-jp@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 A7CBBA70A88 for ; Thu, 28 Jan 2016 12:02:18 +0000 (UTC) (envelope-from kohi@kkdlabs.jp) Received: from sh.kkdlabs.jp (s236214.ppp.asahi-net.or.jp [220.157.236.214]) (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 4EA7B1D06 for ; Thu, 28 Jan 2016 12:02:16 +0000 (UTC) (envelope-from kohi@kkdlabs.jp) Received: from [10.2.255.243] (lars.bears.ichikawa.chiba.jp [10.2.255.243]) by sh.kkdlabs.jp (8.15.2/8.14.4) with ESMTP id u0SBioDn073236; Thu, 28 Jan 2016 20:44:50 +0900 (JST) (envelope-from kohi@kkdlabs.jp) Message-ID: <56A9FF35.40603@kkdlabs.jp> Date: Thu, 28 Jan 2016 20:44:53 +0900 From: Koh-ichi Ito User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-users-jp@freebsd.org Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Subject: [FreeBSD-users-jp 95645] ntpdc timed out X-BeenThere: freebsd-users-jp@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion relevant to FreeBSD communities in Japan List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 12:02:18 -0000 いとうと申します。 FreeBSD 10.2-RELEASE-p1 で SA-16:09.ntp に対応するため freebsd-update を 実行し、こんなことになるとは思いもよらなかったので適用前の状況は確認しな かったんですが、/etc/rc.d/ntpd restart して、動作確認のために ntpdc を実 行したら kohi@sh$ ntpdc ntpdc> peer localhost: timed out, nothing received ***Request timed out ntpdc> ntpdc> sysinfo localhost: timed out, nothing received ***Request timed out ntpdc> quit というエラーが出て動作しなくなってしまいました。ntpq は正常に応答し、同 期もとれていることが確認できています。 kohi@sh$ ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *ntp-b3.nict.go. .NICT. 1 u 43 64 3 8.476 0.508 0.745 そのときのサーバ側の様子は root@sh:/tmp # cat /tmp/fullopen.conf restrict default server ntp.nict.jp root@sh:/tmp # /usr/sbin/ntpd -n -c /tmp/fullopen.conf 28 Jan 20:37:09 ntpd[73030]: ntpd 4.2.8p6-a (1): Starting 28 Jan 20:37:09 ntpd[73030]: Command line: /usr/sbin/ntpd -n -c /tmp/fullopen.conf 28 Jan 20:37:09 ntpd[73030]: proto: precision = 0.209 usec (-22) 28 Jan 20:37:09 ntpd[73030]: Listen and drop on 0 v6wildcard [::]:123 28 Jan 20:37:09 ntpd[73030]: Listen and drop on 1 v4wildcard 0.0.0.0:123 28 Jan 20:37:09 ntpd[73030]: Listen normally on 2 re0 10.2.255.241:123 28 Jan 20:37:09 ntpd[73030]: Listen normally on 3 lo0 [::1]:123 28 Jan 20:37:09 ntpd[73030]: Listen normally on 4 lo0 [fe80::1%2]:123 28 Jan 20:37:09 ntpd[73030]: Listen normally on 5 lo0 127.0.0.1:123 28 Jan 20:37:09 ntpd[73030]: Listening on routing socket on fd #26 for interface updates です。 ＃ 切り分けのために甘い設定で動かしましたが、常用の設定はもっと閉めてい ます、念のため。 ntpq がつながって同期がとれていることも確認できているので、あまり深く気 にせず軽い気持ちで訊いちゃいますけど、みなさんのところでは、こんな事象、 出ていませんか? -- kkdlabs.jp, featuring Koh-ichi Ito as just another DNS freak in town.