<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-timesyncd doesn't work with pure systemd-networkd"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79836#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-timesyncd doesn't work with pure systemd-networkd"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79836">bug 79836</a>
from <span class="vcard"><a class="email" href="mailto:kotrfa@gmail.com" title="kotrfa <kotrfa@gmail.com>"> <span class="fn">kotrfa</span></a>
</span></b>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>