networking
protocol_error
ai_generated
partial
NTP: Server 203.0.113.1 stratum 16, too high to synchronize
ID: networking/ntp-stratum-too-high
85%Fix Rate
84%Confidence
1Evidence
2024-05-12First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| NTP 4.2.8 | active | — | — | — |
| chrony 4.3 | active | — | — | — |
| OpenNTPD 6.2 | active | — | — | — |
| Windows Time Service 10.0 | active | — | — | — |
Root Cause
The NTP server reports a stratum value of 16, indicating it is unsynchronized or has lost its upstream reference clock, making it unusable as a time source.
generic中文
NTP服务器报告层级值为16，表示它未同步或失去了上游参考时钟，使其无法用作时间源。
Official Documentation
https://www.ntp.org/documentation/Workarounds
-
85% success Check the NTP server's upstream connection: on the server, run 'ntpq -p' to verify reachability and stratum of upstream servers, then fix network issues or reconfigure the server to use a reliable upstream
Check the NTP server's upstream connection: on the server, run 'ntpq -p' to verify reachability and stratum of upstream servers, then fix network issues or reconfigure the server to use a reliable upstream
-
90% success Switch the client to a different NTP server with a lower stratum, e.g., replace 'server 203.0.113.1' with 'server pool.ntp.org iburst' in /etc/ntp.conf
Switch the client to a different NTP server with a lower stratum, e.g., replace 'server 203.0.113.1' with 'server pool.ntp.org iburst' in /etc/ntp.conf
中文步骤
Check the NTP server's upstream connection: on the server, run 'ntpq -p' to verify reachability and stratum of upstream servers, then fix network issues or reconfigure the server to use a reliable upstream
Switch the client to a different NTP server with a lower stratum, e.g., replace 'server 203.0.113.1' with 'server pool.ntp.org iburst' in /etc/ntp.conf
Dead Ends
Common approaches that don't work:
-
95% fail
The client NTP service is not the problem; the server's stratum is still 16, so the client will continue to reject it.
-
80% fail
This may cause the client to use a bad time source, leading to clock drift and potential synchronization issues.