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