| Re: [chrony-dev] chronyd not recovering after time stepped. |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] chronyd not recovering after time stepped.
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Thu, 27 Aug 2015 23:35:02 +1200
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a0-2; h=Feedback-ID:X-Smtpcorp-Track:To:Message-Id:Date: From:Subject; bh=IYgOepQzpYCxLKuGpn9t3mjDUet3u5kXiyPKu2FT0KM=; b=r4MTIAJFLJdQ dKgk3cVgZWwOlrJdg2o/SfrzfUGTTuxl7kBAgGi9Uj0NZU7oS6E9YdA+cRSducQxbxPHyZCn4TYQ9 prJwNzV98GVsxDh7IoHJ3T0SHoMIXUdbxf7u3w5/0GU4bmIXZDzQVYEhJj3DNcZgnY1q4rSOk9So3 1SWJwCnWQpH4efaqM11sQ8xc1IOhs610+n4IJk3gnfB1syKxi3cQKaOlIXj/pZxCV+ISy3Fn4qR5w nplXQExLgULsRb8mhytLz026dmMrQSfPntzaEbRN3wdWXto8r5iPf66F4m1iBIQB5pyYmMKKwL/Yj FjWmcLbVogJGkM1F3dBBXw==;
- Feedback-id: 149811m:149811acx33YQ:149811sUapGmMZHF:SMTPCORP
> On 27/08/2015, at 11:24 pm, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
>
> Overshoot is possible depending on the adjtime() correction rate and
> the polling interval.
Yes - I don't think the overshoot is a problem.
>
>> On close inspection, I can that the offset is dropping, but very, very slowly from 70ms to 50ms in an hour, i.e at about 5ppm. Maybe it will recover in a few hours?
>
> That is odd. How long is the polling interval? It shouldn't take more
> than 6-10 new measurements after the step for the frequency to get close
> again to the right value and correct any remaining offset.
The polling interval is 8 seconds. And indeed, when I restart chronyd it only takes a few cycles to correct the offset.
I'm not seeing any significant change in frequency, maybe 1ppm (from 17.5 ppm) for just a few samples after the step and then back to 17.5.
>
>> Restarting chronyd clears the offset rapidly.
>>
>> Is this normal behaviour?
>>
>> I'm really not sure whats going on here and, if it is a problem, where I should be looking to debug it.
>
> The measurements, statistics and tracking logs could be useful.
I've been looking at the tracking logs. As far as I can tell, the others seem to be normal. Its just the 'System time' offset that is off.
--
Bryan Christianson
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.