Re: [chrony-users] Re: sync takes half an hour to complete |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Re: sync takes half an hour to complete
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 24 Feb 2020 09:21:12 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1582532487; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UeB6wYvivn5IGYYntriRxYEJtTaLJFN9TxB++9Iwh1A=; b=AiNLwmqzc7ctMIgfnuYGcPCvq8hZRZnZr69AlsRBOfjzFC12wnQp3v+wo2CFs6KBrbXx7v JuAoob9gKXiy6GXQtWMKu5vp4qw7wqggqvsIonSxreBKTUm9bb1MfyK2wPEsIOEjmyP/vi vtOV6lYAa1031yPjmPgVZKOtUWd719E=
On Fri, Feb 21, 2020 at 02:46:27PM +0200, Andrii Voloshyn wrote:
> Anyone, any ideas?
(I didn't receive your original email due to a spam filter)
> On Fri, Feb 14, 2020 at 3:24 PM Andrii Voloshyn <a.voloshyn@xxxxxxxxxxxxxx>
> wrote:
>
> > Feb 10 22:58:23 : chronyd[479]: Selected source 81.94.123.16
> > Feb 10 22:58:26 : try: 1, refid: 0.0.0.0, correction: 0.000000003, skew:
> > 0.000
> > Feb 10 22:58:26 : try: 2, refid: 0.0.0.0, correction: 0.000000003, skew:
> > 0.000
> >
> > I thought that correction should be 0.0 while refid is 0.0.0.0?
One explanation would be that a source was briefly selected and the
clock was updated, but later the selection failed due to falsetickers
and what you see is the remaining correction from that updated. Are
there any other chrony messages in the system log?
> > pool <pool server 1>.pool.ntp.org iburst
> > pool <pool server 2>.pool.ntp.org iburst
> > pool <pool server 3>.pool.ntp.org iburst
> > pool <pool server 4>.pool.ntp.org iburst
> > pool <pool server 5>.pool.ntp.org iburst
> > makestep 1.0 3
That's a very large number of sources from the pool.
> > I am wondering if it could be caused by some bug, that might have been
> > fixed in the later versions of chrony?
I don't recall anything specific, but it is possible.
> > Is there anything I can do to eliminate this issue in the future?
Try a newer version and/or collect more data in case it happens again.
> > One other question I would like to ask is this: Is the source only
> > selected after all sources get online/offline?
No, just one online reachable source is enough (with default minsources).
--
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.