• Ntpq P .init. 16 U 128 0 0.000 0.000 0.000 For Sale
• Ntpq P .init. 16 U 128 0 0.000 0.000 0.000 Dollar

Ntpq P .init. 16 U 128 0 0.000 0.000 0.000 For Sale

16 u - 64 0 0.000 0.000 4000.00 210.173.160.87.INIT. 16 u - 64 0 0.000 0.000 4000.00 localhost.localdomain: stratum 16, offset 0.000000, synch distance 0.000000 今回の場合、 whenが書かれていない = サーバ指定に合わせた restrict を書く; ntptrace でstratum が16のまま = 待つ; で直りました。 # ntpq -pn.

The problem with time not syncing is due to restrict default ignore, causing all remote packets to be dropped by the daemon (including those replying to configured servers, unless you add additional restricts to allow the configured servers).I have no idea where 36.105.58.17 is coming from, it's a random address in China which seems entirely unrelated to your config. Are you actually in China? If so, it could be that your DNS queries are being attacked by an ISP or the government to give false results.I recommend the following config (but not for clients in China, as there is a known lack of NTP pool servers there). Pool 0.freebsd.pool.ntp.org iburst preemptpool 1.freebsd.pool.ntp.org iburst preemptpool 2.freebsd.pool.ntp.org iburst preemptpool 3.freebsd.pool.ntp.org iburst preemptrestrict default ignorerestrict source nomodify noquery notraprestrict 192.168.1.0 mask 255.255.255.0 nomodify notrapThe FreeBSD default /etc/ntp.conf uses an obsolete method for configuring pool servers, which can be problematic. The above is the current best config for it. Restrict source is a relatively new feature which matches all configured servers, including dynamic pool servers.

Or, in traditional video-game fashion, would you prefer to simply reload the last checkpoint and try again? Clone arc troopers.

Ntpq P .init. 16 U 128 0 0.000 0.000 0.000 Dollar

There's no need to specify driftfile, as that is managed by /etc/rc.d/ntpd (via ntpdflags).The NIST servers can be a bit overloaded at times, so the pool can often produce better results. They can also be a very poor choice for a client outside the USA due to the large and unstable latency.You might alternatively want to use your ISP's NTP servers, if they have them, e.g.