[systemd-devel] systemd-timesyncd dies on one machine but runs okay on another

[Mantas Mikulėnas]

On Mon, Sep 3, 2018 at 3:41 PM Manuel Wagesreither <ManWag at fastmail.fm>
wrote:

> Hallo all!
>
> I'm working on an embedded project consisting of an host and numerous
> virtual machines and am facing problems related to time management.
> systemd-timesyncd dies on one machine (HOST), but runs okay on another
> (VM2) with identical config.
>
> The project setup is as follows:
>
> HOST: Runs a (heavily) modified Debian with systemd, retrieves time via
> NTP from VM3 using systemd-timesyncd.
> * VM1: Runs openwrt and serves time via NTP using chrony
> * VM2: Runs a (heavily) modified Debian with SELINUX and systemd,
> retrieves time via NTP from VM3 using systemd-timesyncd
> * VM3-?: Some other VMs which seem to run fine
>
> The symptoms are as follows:
>
> HOST: `systemd-timesyncd.service` is reported as inactive (dead). A time
> update (adjusting the time by 2 days) took place. Then, after 5min, the
> service died. (It always seems to die 5-15min after a time update.)
> ```
> root at HOST:/var/log# systemctl status systemd-timesyncd
> ● systemd-timesyncd.service - Network Time Synchronization
>    Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
> vendor preset: enabled)
>   Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
>            └─disable-with-time-daemon.conf
>    Active: inactive (dead) since Wed 2018-09-05 07:30:02 CEST; 1 day 17h
> left
>      Docs: man:systemd-timesyncd.service(8)
>   Process: 4724 ExecStart=/lib/systemd/systemd-timesyncd (code=exited,
> status=0/SUCCESS)
>  Main PID: 4724 (code=exited, status=0/SUCCESS)
>    Status: "Idle."
>
> Sep 03 11:51:58 konnektor systemd[1]: Starting Network Time
> Synchronization...
> Sep 03 11:51:58 konnektor systemd[1]: Started Network Time Synchronization.
> Sep 05 07:25:31 konnektor systemd-timesyncd[4724]: Synchronized to time
> server 192.168.253.1:123 (192.168.253.1).
> Sep 05 07:30:02 konnektor systemd[1]: Stopping Network Time
> Synchronization...
> Sep 05 07:30:02 konnektor systemd[1]: Stopped Network Time Synchronization.
> ```
>

Looks like a normal exit, though. What systemd version is this? For v217 or
later I'd expect to see _Status: "Shutting down"_...

Try starting it with [Service] Environment="SYSTEMD_LOG_LEVEL=debug" to see
more details.



> systemd-timesyncd configuration for both HOST and VM2
> ```
> root at HOST, VM2:/var/log# cat /lib/systemd/system/systemd-networkd.service
>

That's not timesyncd...

-- 
Mantas Mikulėnas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180903/71095d39/attachment.html>