ntpd Stratum Zero when nptd is started – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, ntp, ntpd, , .
I have noticed that when I start ntpd on a server, checks against that server reveal that it has a stratum of zero. If I understand this correctly, I believe this means that ntpd is currently only using itself as the time source.
After a minute or so, it checks against the server, and the stratum is no longer zero.
Do I understand this correctly, and can I speed up time the time before it becomes non-zero?
This sounds like a bug (or a configuration edit gone horribly wrong) – As Matt Simmons pointed out ntpd usually defaults to Stratum 16 (“Unsynchronized”).
My (admittedly limited) understanding of NTP strata is that Stratum 0 is reserved for reference clocks (a cesium clock for example, or a GPS Time receiver) that you would attach to a computer to create a stratum 1 server (using the stratum 0 device as its reference).
Local clock should not be used.
you can speed up synchronization by using the iburst keyword for your server definitions.