tladated on beaglebone doesn't get the correct time
Reported by
jrbarnette@chromium.org,
Mar 28 2016
|
|||||
Issue description
I've noticed that beaglebone servo hosts in the test lab tend to
have an incorrect time. I checked up the status of tlsdated, and
it seemed healthy (or at least, "not unhealthy"):
localhost ~ # status tlsdated
tlsdated start/running, process 393
localhost ~ # grep tlsdate /var/log/messages*
/var/log/messages.2:2016-03-27T00:05:27.139512-07:00 NOTICE simple-rotate[429]: rotating /var/log/tlsdate.log
Despite that, time on the selected beaglebone servo host was
more than 10 minutes slow.
For reference, tlsdated on beaglebone has been enabled since
bug 320868 ; I don't know what's going on.
,
Mar 30 2016
It's reliably reproducible. Log in to any beaglebone, and the time will be off, sometimes by many hours.
,
Apr 11 2016
,
Apr 26 2016
,
Apr 27 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 27 2017
A spot-check of various beaglebones says this is no longer reproducible. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by autumn@chromium.org
, Mar 28 2016