Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial time setting not working if servers is used #72

Open
codemaker219 opened this issue Aug 30, 2022 · 0 comments
Open

Initial time setting not working if servers is used #72

codemaker219 opened this issue Aug 30, 2022 · 0 comments

Comments

@codemaker219
Copy link

codemaker219 commented Aug 30, 2022

If you use the servers directive, the initial time setting is not working.

For example if you use the following config:

servers 0.de.pool.ntp.org trusted

Ntp will print:

bash-5.1# ntpd -d -f ntpd.conf 
/var/db/ntpd.drift is empty
ntp engine ready
peer 185.120.22.12 now valid
peer 87.106.180.117 now valid
peer 217.197.91.176 now valid
peer 164.68.116.11 now valid
no reply received in time, skipping initial time setting

Important to note is that the traffic is not blocked and even more imported is that if you switch from servers to server, everything is working. Like:

bash-5.1# ntpd -d -f ntpd.conf 
/var/db/ntpd.drift is empty
ntp engine ready
peer 185.120.22.14 now valid
set local clock to Tue Aug 30 11:58:58 UTC 2022 (offset 20780872.936448s)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant