no reply received in time, skipping initial time setting

[ilyaevseev]

Openntpd is started as service under CentOS 7.x after network-online.target is reached.

It seems that DNS resolving is actually not working at this moment, so "ExecStartPre=/bin/ping -qw1c5 time.google.com" returns "Name or service not known".

Openntpd not tries to re-resolve servername and re-send queries. Instead this, it simply waits 15 seconds and reports "no reply received in time, skipping initial time setting". Is it a bug or a feature?

My current workaround:

# /etc/systemd/system/openntpd.service.d/WaitResolverAlive.conf
[Service]
ExecStartPre=/bin/sh -c 'for N in 1 2 3 4 5; do /bin/ping -q -w1 -c3 time.google.com && break; sleep 1; done'

[tofurky]

the following fixed things for me on ubuntu 18.10:

# systemctl edit openntpd.service

[Unit]
After=network-online.target nss-lookup.target
Wants=network-online.target

[tofurky]

started running into issues with this in ubuntu 19.10 (could be coincidental). anyways, enabling ifupdown-wait-online.service, along with adding the after/wants network-online.target to the openntpd service override, seems to fix things. this of course only matters if you're using ifupdown instead of something like systemd-networkd or networkmanager.