| Re: [chrony-users] New with 1.30: stuck after resume from suspend |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Thu, Jul 03, 2014 at 12:35:35PM +0200, Holger Hoffstätte wrote:
> After updating to 1.30-final on my laptop (kernel 3.14.10, Gentoo userland) everything still seems to work fine. However after waking up from suspend-to-RAM over night, it seems chrony is "stuck": it's still running and accessible to requests (e.g. to list sources), but no longer performs any update polls. The "LastRx" counter shows a "10y" interval, and waiting ~maxpoll doesn't seem to help. 10 years does seem a bit long. ;)
10 years is the value printed when no samples are stored.
This is probably related to the new detection of forward time jumps,
which was mainly intended to handle system suspends. When chronyd
sees that the clock advanced by more than 10 second than what is
expected, it will throw away all data and start again from scratch
will polling interval at minpoll.
When this happens, in the log you should see a "forward time jump was
detected" message, immediately followed by "no reachable sources" and
then in about 2 minimum polling intervals (assuming the suspend was
longer than the polling interval used before suspend) a new source
should be selected.
> Giving such a stuck chrony a nudge via "chronyc burst" gets things going again.
Interesting. I suspect the scheduled timeout got lost somehow.
How is your chronyd configured? Do you set the online/offline status
from chronyc?
> The previous 1.29.1 release never had this problem and properly recovered itself after wakeup, initially downscaling the poll interval and subsequently ramping up again.
That's what should be still happening with 1.30, except it will
wait for 3 replies before updating the clock instead of one. Throwing
avaid the old data is useful to avoid a possibly large frequency error
when the new measurement is added to the (now invalid) old data.
--
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.