[2.1] Cannot sync with an upstream NTP server with stratum=9 or larger
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
MAAS region controller has a local NTP server with "tos orphan 8".
http://
In my case, I have only one NTP server with stratum=11 in reachable networks, so I set it as an upstream NTP server for MAAS. However, ntpd in MAAS does not sync with the upstream server.
$ ntpq -pn
remote refid st t when poll reach delay offset jitter
=======
<IP address of an upstream> LOCAL(0) 11 u 25 64 377 0.721 -799.12 2.326
When manually editing /etc/ntp/maas.conf with "tos orphan 12" and restarting ntpd, it's synced as expected (with "*" in front of an upstream NTP server).
$ ntpq -pn
remote refid st t when poll reach delay offset jitter
=======
*<IP address of an upstream> LOCAL(0) 11 u 30 64 377 0.640 -5.127 0.825
Acting as stratum=8 NTP as MAAS is a bit too much in some cases.
Changed in maas: | |
milestone: | none → 2.2.0 |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.x |
Changed in maas: | |
milestone: | 2.2.x → 2.3.0 |
tags: | added: ntp |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Could you try using the `fudge` command?
For example, to /etc/ntp.conf add:
fudge <ip-of- upstream- server> stratum 4
and restart ntpd.
This should, I believe, make ntpd act as if the upstream server is stratum 4 instead of whatever it advertises itself at. See http:// doc.ntp. org/current- stable/ clockopt. html for more detail.