<div dir="ltr"><div>Indeed, i run gnome and gnomes NetworkManager.</div><div><br></div><div>I just tested the binary approach with LOG_LEVEL=debug (log attached below and it worked, also systemctl start systemd-timesyncd.service works.</div>
<div><br></div><div><div>Added new server <a href="http://time1.google.com">time1.google.com</a>.</div><div>Added new server <a href="http://time2.google.com">time2.google.com</a>.</div><div>Added new server <a href="http://time3.google.com">time3.google.com</a>.</div>
<div>Added new server <a href="http://time4.google.com">time4.google.com</a>.</div><div>systemd-timesyncd running as pid 985</div><div>Selected server <a href="http://time1.google.com">time1.google.com</a>.</div><div>Resolving time1.google.com...</div>
<div>Resolved address <a href="http://216.239.32.15:123">216.239.32.15:123</a> for <a href="http://time1.google.com">time1.google.com</a>.</div><div>Resolved address [2001:4860:4802:32::f]:123 for <a href="http://time1.google.com">time1.google.com</a>.</div>
<div>Selected address <a href="http://216.239.32.15:123">216.239.32.15:123</a> of server <a href="http://time1.google.com">time1.google.com</a>.</div><div>Using NTP server <a href="http://216.239.32.15:123">216.239.32.15:123</a> (<a href="http://time1.google.com">time1.google.com</a>).</div>
<div>Sent NTP request to <a href="http://216.239.32.15:123">216.239.32.15:123</a> (<a href="http://time1.google.com">time1.google.com</a>).</div><div>NTP response:</div><div> leap : 0</div><div> version : 4</div>
<div> mode : 4</div><div> stratum : 2</div><div> precision : 0.000001 sec (-20)</div><div> reference : n/a</div><div> origin : 1407956263.690</div><div> receive : 1407956263.355</div><div>
transmit : 1407956263.355</div><div> dest : 1407956263.731</div><div> offset : -0.355 sec</div><div> delay : +0.040 sec</div><div> packet count : 1</div><div> jitter : 0.000</div><div>
poll interval: 32</div><div> adjust (slew): -0.355 sec</div><div> status : 8193 sync</div><div> time now : 1407956263.730</div><div> constant : 1</div><div> offset : -0.355 sec</div><div> freq offset : +0 (0 ppm)</div>
<div>interval/delta/delay/jitter/drift 32s/-0.355s/0.040s/0.000s/+0ppm</div></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-08-13 20:47 GMT+02:00 Lennart Poettering <span dir="ltr"><<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, 13.08.14 20:35, Daniel Buch (<a href="mailto:boogiewasthere@gmail.com">boogiewasthere@gmail.com</a>) wrote:<br>
<br>
> With current git i noticed systemd-timesyncd failed and complain like this,<br>
> log attached below.<br>
><br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Starting Network Time<br>
> Synchronization...<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: systemd-timesyncd.service: main<br>
> process exited, code=exited, status=1/FAILURE<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Failed to start Network Time<br>
> Synchronization.<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Unit systemd-timesyncd.service<br>
> entered failed state.<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: systemd-timesyncd.service has no<br>
> holdoff time, scheduling restart.<br>
> aug 13 20:12:08 dbuch-laptop systemd-timesyncd[377]: Failed to allocate<br>
> manager: No data available<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: systemd-timesyncd.service: main<br>
> process exited, code=exited, status=1/FAILURE<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Failed to start Network Time<br>
> Synchronization.<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Unit systemd-timesyncd.service<br>
> entered failed state.<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: systemd-timesyncd.service has no<br>
> holdoff time, scheduling restart.<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Stopping Network Time<br>
> Synchronization...<br>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Starting Network Time<br>
> Synchronization...<br>
> aug 13 20:12:08 dbuch-laptop systemd-timesyncd[385]: Failed to allocate<br>
> manager: No data available<br>
><br>
> Is this known or am i missing some configuration where i need opt-in?<br>
<br>
</div></div>Hmm, ENODATA? That smells like something returned by sd-network, but I<br>
can't see how that could happen... I figure you run things without<br>
networkd? (which is totally ok and supported, just asking...)<br>
<br>
If you run the binary from the command line, does it fail too? If so,<br>
can you run it in gdb, and maybe step through it, to see where it fails?<br>
<br>
Also, setting SYSTEMD_LOG_LEVEL=debug as env var for it might be<br>
interesting too...<br>
<span class="HOEnZb"><font color="#888888"><br>
Lennart<br>
<br>
--<br>
Lennart Poettering, Red Hat<br>
</font></span></blockquote></div><br></div>