| Re: [chrony-users] Checking chrony daemon status via NTP3 protocol |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Checking chrony daemon status via NTP3 protocol
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 27 May 2020 08:53:46 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1590562431; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KJNuTfJvYLUEXPRyeIoTrQnTW1qQdIwB8VPmtqa5ROk=; b=XVQaJCxZyvNHUGWaH2NsaYOOmWJuNS0+p913DvKtpw7ZaJ16Q0aGtxrcPq85uKswDDRgLQ Au2HH0e9qSVBsfjsH57XkIYvrbqj2WapeifnvgKX6CZ9wgQqxXSMhZMuDXtSfbZwIud1oh dnnmxKbWbbCWBg/bAgMSDDyZWFWU6MA=
On Tue, May 26, 2020 at 05:49:15PM +0000, SALA MASSIMO wrote:
> Hi
>
> I apologize in advace if my question is trivial.
>
> The daemon is stopped (ver 3.5).
> I start it and send a NTP3 CLIENT query, to localhost port 123/udp:
> NTP_VERSION << 3 | NTP_MODE_CLIENT
>
> The first answer has the status 0xdc : the bit NTP_LEAP_NOTSYNC is set.
> Good: the daemon is starting and looking for the Ntp servers.
>
> I query again the daemon, and in the following replies from the server:
> * the status is OK : 0x1c
> * the server time (reference timestamp, at offset 16 of the Udp packet payload) is incorrect.
This sounds like a bug. In a quick test with the current development
code and chrony-3.5 I didn't see this behavior.
How is your server configured?
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.