From owner-freebsd-questions@FreeBSD.ORG Thu Feb 18 04:16:28 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73D291065670 for ; Thu, 18 Feb 2010 04:16:28 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from server505.appriver.com (server505a.appriver.com [98.129.35.4]) by mx1.freebsd.org (Postfix) with ESMTP id 058238FC12 for ; Thu, 18 Feb 2010 04:16:27 +0000 (UTC) X-Policy: GLOBAL - maxiscale.com X-Primary: psteele@maxiscale.com X-Note: This Email was scanned by AppRiver SecureTide X-ALLOW: psteele@maxiscale.com ALLOWED X-Virus-Scan: V- X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES->UNITED STATES X-Note-Sending-IP: 98.129.23.14 X-Note-Reverse-DNS: ht01.exg5.exghost.com X-Note-WHTLIST: psteele@maxiscale.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G173 G174 G175 G176 G180 G181 G192 G279 X-Note: Encrypt Rule Hits: X-Note: Mail Class: ALLOWEDSENDER X-Note: Headers Injected Received: from [98.129.23.14] (HELO ht01.exg5.exghost.com) by server505.appriver.com (CommuniGate Pro SMTP 5.3.2) with ESMTPS id 28367131 for freebsd-questions@freebsd.org; Wed, 17 Feb 2010 22:16:28 -0600 Received: from mbx03.exg5.exghost.com ([169.254.1.200]) by ht01.exg5.exghost.com ([98.129.23.14]) with mapi; Wed, 17 Feb 2010 22:16:26 -0600 From: Peter Steele To: "freebsd-questions@freebsd.org" Date: Wed, 17 Feb 2010 22:16:25 -0600 Thread-Topic: What would make ntpd hang in BSD 8? Thread-Index: Acqv+sa+dhoA1NsrQ8uXDgZN71YeNAADsqUwABHgSGA= Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB385D5663@MBX03.exg5.exghost.com> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB385470DB@MBX03.exg5.exghost.com> <74B75245-623A-496A-BDEC-F1B1C7099619@mac.com> <23F2E2B0457F4046AD8350DAFB86C41130D43517@MBX03.exg5.exghost.com> In-Reply-To: <23F2E2B0457F4046AD8350DAFB86C41130D43517@MBX03.exg5.exghost.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: What would make ntpd hang in BSD 8? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2010 04:16:28 -0000 Resending this message. For some reason my post never showed up... -----Original Message----- From: Peter Steele=20 Sent: Wednesday, February 17, 2010 11:51 AM To: freebsd-questions@freebsd.org Subject: RE: What would make ntpd hang in BSD 8? > ntpq -pc rv localhost > cat /etc/ntp.conf My ntp.conf looks like this: # General Configuration server 0.us.pool.ntp.org server 1.us.pool.ntp.org server 2.us.pool.ntp.org server 3.us.pool.ntp.org # Drift file driftfile /var/db/ntpd.drift The output from ntpq for the BSD 7 system is this: remote refid st t when poll reach delay offset jit= ter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D +169.229.70.183 169.229.128.214 3 u 40 512 37 7.921 9.170 8.= 836 *208.75.88.4 192.12.19.20 2 u 43 512 37 12.049 8.224 8.= 168 +217.160.254.116 209.51.161.238 2 u 38 512 37 55.111 -7.128 10.= 347 +198.247.173.220 128.206.12.130 3 u 39 512 37 47.401 -1.149 3.= 659 status=3Dc624 sync_alarm, sync_ntp, 2 events, event_peer/strat_chg, version= =3D"ntpd 4.2.0-a Sun Feb 24 09:12:07 UTC 2008 (1)", processor=3D"amd64", sy= stem=3D"FreeBSD/7.0-RELEASE-p9", leap=3D11, stratum=3D16, precision=3D-20, = rootdelay=3D0.000, rootdispersion=3D8.340, peer=3D25349, refid=3DINIT, reft= ime=3D00000000.00000000 Wed, Feb 6 2036 22:28:16.000, poll=3D4, clock=3Dc= f26c2d5.ea2b4541 Wed, Feb 17 2010 11:32:37.914, state=3D1, offset=3D0.000,= frequency=3D-13.269, jitter=3D0.001, stability=3D0.000 and the output from the BSD 8 system is this: remote refid st t when poll reach delay offset jit= ter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 169.229.70.183 .INIT. 16 u - 64 0 0.000 0.000 0.= 002 208.75.88.4 .INIT. 16 u - 64 0 0.000 0.000 0.= 002 217.160.254.116 .INIT. 16 u - 64 0 0.000 0.000 0.= 002 198.137.202.16 .INIT. 16 u - 64 0 0.000 0.000 0.= 002 assID=3D0 status=3Dc011 sync_alarm, sync_unspec, 1 event, event_restart, ve= rsion=3D"ntpd 4.2.4p5-a (1)", processor=3D"amd64", system=3D"FreeBSD/8.0-CU= RRENT", leap=3D11, stratum=3D16, precision=3D-19, rootdelay=3D0.000, rootdi= spersion=3D0.000, peer=3D0, refid=3DINIT, reftime=3D00000000.00000000 Wed, Feb 6 2036 22:28:16.000, poll=3D6, clock=3Dcf26c4d1.d21b33f1 Wed, Feb 17 2010 11:41:05.820, state=3D1, offset= =3D0.000, frequency=3D-14.299, jitter=3D0.002, noise=3D0.002, stability=3D0= .000, tai=3D0 The most obvious difference is the .INIT. entries, but there also appear to= be several "0.0" type of entries that look suspicious. What do these imply= ?