Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44406 - [systemd] timesyncd seems broken in 219-4
Attached to Project:
Arch Linux
Opened by Gaetan Bisson (vesath) - Tuesday, 31 March 2015, 02:50 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 31 March 2015, 17:30 GMT
Opened by Gaetan Bisson (vesath) - Tuesday, 31 March 2015, 02:50 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 31 March 2015, 17:30 GMT
|
DetailsSystemd's timesyncd seems broken in version 219-4 currently in [testing].
All my machines run systemd-timesyncd with Arch's default /etc/systemd/timesyncd.conf . Normally they report: systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2015-03-19 15:06:22 TAHT; 1 weeks 4 days ago Docs: man:systemd-timesyncd.service(8) Main PID: 218 (systemd-timesyn) Status: "Using Time Server 27.54.95.11:123 (2.arch.pool.ntp.org)." CGroup: /system.slice/systemd-timesyncd.service └─218 /usr/lib/systemd/systemd-timesyncd Mar 30 12:46:42 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.355s/0.01...1ppm Mar 30 13:20:50 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/+0.010s/0.355s/0.01...3ppm Mar 30 13:54:59 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/-0.011s/0.353s/0.01...0ppm Mar 30 14:29:07 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/+0.008s/0.344s/0.01...1ppm Mar 30 15:03:16 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/-0.004s/0.354s/0.01...0ppm Mar 30 15:06:17 unagi systemd-timesyncd[218]: Network configuration changed, trying to establish connection. Mar 30 15:06:17 unagi systemd-timesyncd[218]: Using NTP server 27.54.95.11:123 (2.arch.pool.ntp.org). Mar 30 15:06:17 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/+0.002s/0.349s/0.01...0ppm Mar 30 15:40:26 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/+0.006s/0.365s/0.01...2ppm Mar 30 16:14:34 unagi systemd-timesyncd[218]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.345s/0.01...2ppm Hint: Some lines were ellipsized, use -l to show in full. Now I have upgraded one of them to systemd-219-4 and it now says: systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2015-03-30 16:38:42 TAHT; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 14967 (systemd-timesyn) Status: "Using Time Server 202.22.158.30:123 (0.arch.pool.ntp.org)." CGroup: /system.slice/systemd-timesyncd.service └─14967 /usr/lib/systemd/systemd-timesyncd Mar 30 16:38:42 aji systemd[1]: Starting Network Time Synchronization... Mar 30 16:38:42 aji systemd[1]: Started Network Time Synchronization. And nothing else. Restarting the service has no effect. Could anyone confirm this issue and/or let me know how I could provide further debbugging info? |
This task depends upon
Comment by Dave Reisner (falconindy) -
Tuesday, 31 March 2015, 11:33 GMT
The drift spam was moved to debug in 219.
Comment by Gaetan Bisson (vesath) -
Tuesday, 31 March 2015, 16:03 GMT
Ah, thanks. Is there some way I could get details on the sync once the service is already started?
Comment by Dave Reisner (falconindy) -
Tuesday, 31 March 2015, 16:05 GMT
timedatectl will show "NTP synchronized: Yes" if everything is working. Beyond that, you'd need to restart timesyncd with extra debugging (add a dropin with [Service]\nEnvironment=SYSTEMD_LOG_LEVEL=debug) if you want to be more chatty.
Comment by Gaetan Bisson (vesath) -
Tuesday, 31 March 2015, 17:30 GMT
Thanks a lot!