Using systemd-timesyncd with network manager (e.g netctl) worked fine, but after using ONLY systemd-networkd, timesyncd doesnt sync time. After some time, it just shows status: "Idle." without any work. * systemd-networkd.service - Network Service Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled) Active: active (running) since Sun 2014-06-08 16:48:36 CEST; 15h ago Docs: man:systemd-networkd.service(8) Main PID: 149 (systemd-network) Status: "Processing requests..." CGroup: /system.slice/systemd-networkd.service `-149 /usr/lib/systemd/systemd-networkd Jun 08 16:48:36 smecpi systemd[1]: Starting Network Service... Jun 08 16:48:36 smecpi systemd-networkd[149]: eth0: link configured Jun 08 16:48:36 smecpi systemd[1]: Started Network Service. Jun 08 16:48:37 smecpi systemd-networkd[149]: eth0: gained carrier * systemd-timedated.service - Time & Date Service Loaded: loaded (/usr/lib/systemd/system/systemd-timedated.service; static) Active: active (running) since Mon 2014-06-09 08:14:05 CEST; 11min ago Docs: man:systemd-timedated.service(8) man:localtime(5) http://www.freedesktop.org/wiki/Software/systemd/timedated Main PID: 4520 (systemd-timedat) CGroup: /system.slice/systemd-timedated.service `-4520 /usr/lib/systemd/systemd-timedated Jun 09 08:14:05 smecpi systemd[1]: Started Time & Date Service. * systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled) Active: active (running) since Sun 2014-06-08 16:48:35 CEST; 15h ago Docs: man:systemd-timesyncd.service(8) Main PID: 125 (systemd-timesyn) CGroup: /system.slice/systemd-timesyncd.service `-125 /usr/lib/systemd/systemd-timesyncd Jan 01 01:00:06 smecpi systemd-timesyncd[125]: System clock time unset or jumped backwards, restoring from recorded timestamp: Sun 2014-06-08 16:48:35 CEST Jun 08 16:48:35 smecpi systemd[1]: Started Network Time Synchronization.
By the way, no errors or log are present. The file /etc/systemd/timesyncd.conf is in it's defaults.
It seems to me that timesyncd just waits for "network configuration change". I guess that (somehow) timesyncd is runned after networkd and then waits for change. All you have to do is systemctl restart systemd-networkd Here is example and steps to reproduce (after boot up, both networkd and timesyncd are enabled): ~ $ systemctl status systemd-timesyncd systemd-networkd * systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled) Active: active (running) since Wed 2014-06-11 17:55:50 CEST; 24min ago Docs: man:systemd-timesyncd.service(8) Main PID: 126 (systemd-timesyn) CGroup: /system.slice/systemd-timesyncd.service `-126 /usr/lib/systemd/systemd-timesyncd Jun 01 01:00:06 locsmxp systemd-timesyncd[126]: System clock time unset or jumped backwards, restoring from recorded timestamp:...0 CEST Jun 11 17:55:50 locsmxp systemd[1]: Started Network Time Synchronization. * systemd-networkd.service - Network Service Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled) Active: active (running) since Wed 2014-06-11 17:55:51 CEST; 24min ago Docs: man:systemd-networkd.service(8) Main PID: 150 (systemd-network) Status: "Processing requests..." CGroup: /system.slice/systemd-networkd.service `-150 /usr/lib/systemd/systemd-networkd Jun 11 17:55:51 locsmxp systemd[1]: Started Network Service. Jun 11 17:55:51 locsmxp systemd-networkd[150]: eth0: link configured Jun 11 17:55:52 locsmxp systemd-networkd[150]: eth0: gained carrier Hint: Some lines were ellipsized, use -l to show in full. now restart networkd: ~ $ systemctl restart systemd-networkd and the result: ~ $ systemctl status systemd-timesyncd systemd-networkd * systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled) Active: active (running) since Wed 2014-06-11 17:55:50 CEST; 25min ago Docs: man:systemd-timesyncd.service(8) Main PID: 126 (systemd-timesyn) Status: "Using Time Server 216.239.32.15:123 (time2.google.com)." CGroup: /system.slice/systemd-timesyncd.service `-126 /usr/lib/systemd/systemd-timesyncd Jun 01 01:00:06 locsmxp systemd-timesyncd[126]: System clock time unset or jumped backwards, restoring from recorded timestamp:...0 CEST Jun 11 17:55:50 locsmxp systemd[1]: Started Network Time Synchronization. Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Network configuration changed, trying to establish connection. Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Network configuration changed, trying to establish connection. Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Using NTP server 216.239.32.15:123 (time2.google.com). Jun 11 18:20:49 locsmxp systemd-timesyncd[126]: interval/delta/delay/jitter/drift 64s/+0.000s/0.000s/0.000s/+0ppm * systemd-networkd.service - Network Service Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled) Active: active (running) since Wed 2014-06-11 18:20:48 CEST; 5s ago Docs: man:systemd-networkd.service(8) Main PID: 1129 (systemd-network) Status: "Processing requests..." CGroup: /system.slice/systemd-networkd.service `-1129 /usr/lib/systemd/systemd-networkd Jun 11 18:20:48 locsmxp systemd-networkd[1129]: eth0: gained carrier Jun 11 18:20:48 locsmxp systemd[1]: Started Network Service. Jun 11 18:20:48 locsmxp systemd-networkd[1129]: eth0: link configured Hint: Some lines were ellipsized, use -l to show in full.
Is this still reproducible with current git?
I can reproduce it with 215-4.1 . Seems solved.
I can't reproduce it with 215-4.1 . Seems solved.
(In reply to comment #4) > I can reproduce it with 215-4.1 . Seems solved. Sorry - typo. I CAN'T reproduce it on same machine (as in post below).
Thanks for the clarification.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.