search

ntp-project / ntp

The full and complete NTP Reference Implementation from the Network Time Protocol Project at Network Time Foundation.
https://www.ntp.org/
148 stars 53 forks source link

The time of ntp client was added 2^32 seconds by ntp server when we deployed cluster, unexpectedly. #2

Open h3c-open opened 4 years ago

h3c-open commented 4 years ago

We know that max seconds of transmiting message updating time among different clients by the ntp are 2^32 seconds, but time difference are only 2 years between server and clinet actually. So I do not know how is it ? Can someone give me some suggestions, thank you in advance！

hstenn commented 6 months ago

more information would be helpful. What version of ntpd are you running? ntpd has its build date compiled in, so it knows "now" time cannot be earlier than this date.

Behavior like you describe has only been observed when a human decides to try crazy dates.

sjvudp commented 4 days ago

We know that max seconds of transmiting message updating time among different clients by the ntp are 2^32 seconds, but time difference are only 2 years between server and clinet actually. So I do not know how is it ? Can someone give me some suggestions, thank you in advance！

With the information given it's hard to decide what happened actually, not to talk about whether it's a bug or not.