Keeping the correct time is essential on a server and client system. You can use any one of the following programs to verify that NTP client configuration is working correctly on Linux or Unix-like systems.
How to check NTP is working?
- ntpq – standard NTP query program
- ntpstat – show network time synchronisation status
- timedatectl – show or set info about ntp using systemd
Let us see all commands and examples in details
Verify NTP is working or not with ntpstat command
The ntpstat command will report the synchronisation state of the NTP daemon running on the local machine. If the local system is found to be synchronised to a reference time source, ntpstat will report the approximate time accuracy.
exit status of ntpstat command
You can use the exit status (return values) to verify its operations from a shell script or command line itself:
- If exit status 0 – Clock is synchronised.
- exit status 1 – Clock is not synchronised.
- exit status 2 – If clock state is indeterminant, for example if ntpd is not contactable.
Type the command as follows:
synchronised to NTP server (18.104.22.168) at stratum 3 time correct to within 42 ms polling server every 1024 s
Use the echo command to display exit status of ntp client:
$ echo $?
Checking the status of NTP with ntpq command
The ntpq utility program is used to monitor NTP daemon ntpd operations and determine performance. The program can be run either in interactive mode or controlled using command line arguments. Type the following command on your Linux or Unix-based system:
$ ntpq -pn
$ ntpq -p
remote refid st t when poll reach delay offset jitter ============================================================================== *dione.cbane.org 22.214.171.124 2 u 509 1024 377 51.661 -3.343 0.279 +ns1.your-site.c 126.96.36.199 3 u 899 1024 377 48.395 2.047 1.006 +ntp.yoinks.net 188.8.131.52 2 u 930 1024 377 0.693 1.035 0.241 LOCAL(0) .LOCL. 10 l 45 64 377 0.000 0.000 0.001
* the source you are synchronized to (syspeer). The above is an example of working ntp client. Where,
- -p : Print a list of the peers known to the server as well as a summary of their state.
- -n : Output all host addresses in dotted-quad numeric format rather than converting to the canonical host names.
Another reliable source is running the following command:
$ ntpq -c rv
Look for the leap code as follows:
So leap code 0 (leap_none) means normal synchronized state. And leap code 3 (leap_alarm) means NTP wasnever synchronized. Here is a sample outputs:
A note about timedatectl command
If you are using systemd based system, run the following command to check the service status
# timedatectl status
If NTP enabled is set to No. Try configuring by editing /etc/systemd/timesyncd.conf file as follows:
# vi /etc/systemd/timesyncd.conf
Append/edit [Time] as follows i.e. add time servers or change the provided ones, uncomment the relevant line and list their host name or IP separated by a space (default from my Debian 8.x server):
[Time] Servers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
Save and close the file. Finally, start and enable it, run:
# timedatectl set-ntp true
# timedatectl status
Local time: Mon 2019-09-30 18:25:38 IST Universal time: Mon 2019-09-30 12:55:38 UTC RTC time: Mon 2019-09-30 12:55:38 Time zone: Asia/Kolkata (IST, +0530) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no
The above is easy way to verify NTP is working on Linux.
You learned how to verify that your NTP configuration is working properly. Now you know how to check the status of your date and time, synchronized with upstream time servers. For more info see ntpd docs here.