[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: can not set time

Am 04.02.2017 um 15:49 schrieb Matthias Bodenbinder:

More info:

I switched to systemd and systemd-timesyncd. During boot the time is synced back and forth multiple times and in the end it stays wrong.

Look at this. See the timestamps for each line. Going back and forth.

Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 78.46.253.198:123 (2.debian.pool.ntp.org).
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing.
The switch to systemd and systemd-timesyncd did the trick. But it takes very long. Its obvious from the journal messages but I did not get it at first: timesyncd changes the time in small increments of only 0.01 seconds. 

I just had to wait and now the time is correct.

Matthias
Reply to: