Check ntp-chronyd


This plugin checks the clock offset of chronyd in milliseconds compared to ntp servers. It also prints

  • Reference ID

  • Stratum

  • Ref time (UTC)

  • System time

  • Last offset

  • RMS offset

  • Frequency

  • Residual freq

  • Skew

  • Root delay

  • Root dispersion

  • Update interval

  • Leap status

The stratum of the NTP time source determines its quality. The stratum is equal to the number of hops to a reference clock (which is stratum 0). A NTP server connected directly to the reference clock is Stratum 1, a client connected to this NTP server is Stratum 2, etc.

Fact Sheet

Check Plugin Download

Check Interval Recommendation

Once a minute

Can be called without parameters


Compiled for



usage: ntp-chronyd [-h] [-V] [-c CRIT] [--test TEST] [-w WARN]

This plugin checks the clock offset of chronyd in milliseconds compared to ntp

  -h, --help            show this help message and exit
  -V, --version         show program's version number and exit
  -c CRIT, --critical CRIT
                        Set the critical threshold for the ntp time offset, in
                        ms. Default: 86400000ms
  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
  -w WARN, --warning WARN
                        Set the warning threshold for the ntp time offset, in
                        ms. Default: 800ms

Usage Examples

./ntp-chronyd --warning 500 --critical 10000


NTP offset is 0.698234ms, Stratum is 3, Leap status is Normal

Reference ID    : C3BA0165 (
Stratum         : 3
Ref time (UTC)  : Sun Aug 07 10:02:47 2022
System time     : 0.000254363 seconds slow of NTP time
Last offset     : +0.000698234 seconds
RMS offset      : 0.028022379 seconds
Frequency       : 23.159 ppm fast
Residual freq   : -0.032 ppm
Skew            : 6.203 ppm
Root delay      : 0.068764083 seconds
Root dispersion : 0.016749078 seconds
Update interval : 518.9 seconds
Leap status     : Normal


  • WARN or CRIT if ntp offset is below or above a given threshold.

  • WARN if stratum is >= 9.

  • WARN if no NTP server is used.

  • WARN if no NTP server is found.

Perfdata / Metrics






The ‚frequency‘ is the rate by which the system’s clock would be wrong if chronyd was not correcting it. It is expressed in ppm (parts per million). For example, a value of 1 ppm would mean that when the system’s clock thinks it has advanced 1 second, it has actually advanced by 1.000001 seconds relative to true time.



This is the estimated local offset on the last clock update.



This shows the ‚residual frequency‘ for the currently selected reference source. This reflects any difference between what the measurements from the reference source indicate the frequency should be and the frequency currently being used. The reason this is not always zero is that a smoothing procedure is applied to the frequency. Each time a measurement from the reference source is obtained and a new residual frequency computed, the estimated accuracy of this residual is compared with the estimated accuracy (see skew next) of the existing frequency value. A weighted average is computed for the new frequency, with weights depending on these accuracies. If the measurements from the reference source follow a consistent trend, the residual will be driven to zero over time.



This is a long-term average of the offset value.



This is the total of the network path delays to the stratum-1 computer from which the computer is ultimately synchronized. In certain extreme situations, this value can be negative. (This can arise in a symmetric peer arrangement where the computers’ frequencies are not tracking each other and the network delay is very short relative to the turn-around time at each computer.)



This is the total dispersion accumulated through all the computers back to the stratum-1 computer from which the computer is ultimately synchronized. Dispersion is due to system clock resolution, statistical measurement variations etc.



This is the estimated error bound on the frequency.



The stratum indicates how many hops away from a computer with an attached reference clock we are. Such a computer is a stratum-1 computer, so the computer in the example is two hops away (that is to say, a.b.c is a stratum-2 and is synchronized from a stratum-1).

Source of description:


OS Error „2 No such file or directory“ calling command „chronyc tracking“

You don’t have chronyd.

No NTP server used.

This message occurs when chronyd is running, and chronyd does (currently) not use any ntp server.

Credits, License