Date: Mon, 10 Jul 2017 10:23:09 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Interpreting NTP status Message-ID: <0c954f96-eeb1-f811-8806-9e5fad7420f4@FreeBSD.org> In-Reply-To: <BN6PR2001MB173053AB0FB5FA9322784E7680A80@BN6PR2001MB1730.namprd20.prod.outlook.com> References: <BN6PR2001MB173053AB0FB5FA9322784E7680A80@BN6PR2001MB1730.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq Content-Type: multipart/mixed; boundary="xALBEdqViTQhPXwsK4MnF2uWNVJ4ugKh8"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <0c954f96-eeb1-f811-8806-9e5fad7420f4@FreeBSD.org> Subject: Re: Interpreting NTP status References: <BN6PR2001MB173053AB0FB5FA9322784E7680A80@BN6PR2001MB1730.namprd20.prod.outlook.com> In-Reply-To: <BN6PR2001MB173053AB0FB5FA9322784E7680A80@BN6PR2001MB1730.namprd20.prod.outlook.com> --xALBEdqViTQhPXwsK4MnF2uWNVJ4ugKh8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2017/07/09 15:39, Carmel NY wrote: > NTP status: > remote refid st t when poll reach delay offset = jitter > =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 > +198.55.111.50 133.157.29.35 3 u 760 1024 377 87.913 5.793 = 18.418 > *192.155.90.13 142.66.101.13 2 u 264 1024 377 45.449 -2.235 = 2.925 > 2607:fa18::2407 .STEP. 16 u - 1024 0 0.000 0.000 = 0.000 >=20 > I am hoping someone can tell me exactly what this means. I cannot find > any documentation on how to interpret this. This is the output from 'ntpq -p' It's described under the 'peers' command in ntpq(8) for using ntpq interactively. It shows what NTP servers you are synch'd to, how frequently you are polling those servers, how well you are managing to communicate with them, how long it takes an NTP query to do a round-trip to the servers and how close your local clock is to your time sources. The 'offset' column is measured in milliseconds, so you are fairly well synched. However, you only have two working servers -- you are unable to reach the 3rd server possibly because you don't have IPv6 yet. This means you can't use the 'majority consensus' algorithm -- so if one of your timesources drifted off, you have no way of knowing which is right and which is wrong. Cheers, Matthew --xALBEdqViTQhPXwsK4MnF2uWNVJ4ugKh8-- --0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZY0eDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnhSYP/jreWVAxx3z272D4jnN3VM84 tyXSLQ5+PdQagxg8Fu98rm9fO1dD7kPJfP38f+0jNABYoI6iJTraHsLcvyogjB2L 7cClR09Hb+d70VNz+cknh66/t1VjnLLWChkm514ayseDftMDPpRjZkoFsK7rFgSa TZyfQmDffifO3YI63unRmXnR+6ILuG5TLUjgwHo0o/1F2jMUmPKHcANoy9m2gd90 o3gFmu8ociezUFiYQZgTepD2paOM3E/yP0IXQCnUzMQMKwLKKeBNFNpzXjoBuQPi PR7JDBSFLhtAnstkDK3vhH3r+ckACiBu4sVCtHdPxuZyEoTnkprNlYLdHf1B1HoD T+7y7uxkhXF1kgyZtB44zG6be//47uWCR7ezdN1g+GqtEyhde8xqwIoYqUrIl/8M gLV0zDN6H/o0hS+u8byLNOYnWGogeGU2o2/lZ7bXl+uaZoA4IeG5MR+kNXNpE4nR obyRwfhYo6pC5W8UWAQfNeKkYX/z1lcRy+qv+j3fijoquh/7QFmGRtdAChVTd1cQ b0ubJ3cJAqdWvnPpKXqyoLJ9VJZLUVVFx0XZx/zTIrBnpBebMplLMdZmkJY0BvX0 Ik2+nR3aof1rcJstEdI2/OPB3kgN1s6eima3HYTHm0oCwQAilx+JgAqQRVAHZPGE S94LwL0YuOukNscazR2t =4CV2 -----END PGP SIGNATURE----- --0f9FtSHTRNKo8Loq9HNKKawc8M0at3ieq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c954f96-eeb1-f811-8806-9e5fad7420f4>