- Newest
- Most votes
- Most comments
From here this is difficult to troubleshoot because it might be related to a single instance (or not). If you would like to understand the reasons for the failure I'd suggest creating a support case with the details so that the team can investigate.
That said, a couple of thoughts:
- NTP doesn't need to succeed all of the time. That's not a good reason for it to fail; but it's unlikely that your instance will experience significant clock drift if NTP fails once every so often. So it does depend on the definition of "sometimes".
- How often is synchronisation happening? The NTP service will have a rate limit on it and high levels of traffic will cause requests to be dropped. As above, this is not necessarily a terrible outcome but again it's hard to say without knowing all of the details.
I am able to reproduce the error now continously in a windows instance. I tried manual sync multiple times in few mins interval. But the same error. Looks like AWS NTP Server is permanently barred from that instance.
Anything we need to do to investigate this issue? Do we have any tools to check it? I dont think telnet will work as it is UDP.
To troubleshoot this issue, reach out to the support team - we (here on re:Post) don't have the ability to "see" into your AWS account and assist at this level.
Relevant content
- asked 7 months ago
- Accepted Answerasked 3 years ago
- asked 3 years ago
- asked 3 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
Hi, I fully agree on "NTP doesn't need to succeed all of the time". As long as the failure rate remains reasonably low, it's perfectly fine: the drift will never get big.