NTP synchronised problem in our Centos 7.6 node

Someone, please help on this issue:-

Note : for security reason i didn't mention hostnames and ips.
==============================================================================

[root@ ~]# ntpstat
unsynchronised
   polling server every 1024 s
Ntpstat showing unsynchronised.

==============================================================================

[root@~]# systemctl status ntpd
�- ntpd.service - Network Time Service
   Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2019-04-04 15:00:51 UTC; 5 months 17 days ago
 Main PID: 8275 (ntpd)
    Tasks: 1
   Memory: 20.0K
==============================================================================

And all poller ntp servers are reaching through ntp port and no packet loss. 


[root@ ~]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
   node1               2 u   64 1024    7    1.362   -4.212   3.041
    node2             2 u   65 1024    7    1.752   -4.089   3.023
   node3              2 u   64 1024    7   25.469   -4.160   2.876
    node4            2 u   63 1024    7   25.666   -4.238   2.930
    node5            2 u   66 1024    7   45.907   -5.017   3.054
  node6              2 u   65 1024    7   45.905   -4.499   3.045

==============================================================================
NTptime is giving return code 5;
[root@~]# ntptime
ntp_gettime() returns code 5 (ERROR)
  time e1305f50.e00d7fc8  Sat, Sep 21 2019  8:35:28.875, (.875206994),
  maximum error 16000000 us, estimated error 16000000 us, TAI offset 0
ntp_adjtime() returns code 5 (ERROR)
  modes 0x0 (),
  offset 0.000 us, frequency 43.490 ppm, interval 1 s,
  maximum error 16000000 us, estimated error 16000000 us,
  status 0x2041 (PLL,UNSYNC,NANO),
  time constant 10, precision 0.001 us, tolerance 500 ppm,
[root@~]# date
Sat Sep 21 08:35:33 UTC 2019

==============================================================================

This is the alert we're getting every time but usually, it's getting a fix within 10mins 

OP5 alert is :- 
'Check NTP Status' on host 'hostname' has passed the WARNING threshold.

Service: Check NTP Status
Service Notes: 

Status : WARNING
Notification Comment: 

Additional info:  
Warning - NTPd Health is 50% with 6 peer(s).

Thresholds:  Health (20%

Kindly help on this to fix the issue.

Hmm.

When I run ntpstat .... after a refresh install, I get the following:

ubuntu:~# ntpstat
synchronised to NTP server (198.50.238.156) at stratum 3 
   time correct to within 30 ms
   polling server every 64 s

Perhaps just install ntpd again from scratch with a fresh /etc/ntp.conf file (saving your current one before, of course)?

FYI:

ubuntu:~#  ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.ubuntu.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 ntp.ubuntu.com  .POOL.          16 p    -   64    0    0.000    0.000   0.000
+159.203.82.102  104.236.116.147  3 u   15   64  377   24.997    0.908   3.820
+63-225-179-23.t 204.123.2.5      2 u    8   64  377   60.418    0.388   3.881
#ntp.wdc1.us.lea 130.133.1.10     2 u    7   64  377   28.500    2.689   3.502
*november.system 139.78.97.128    2 u   12   64  377   32.184    0.602   3.532
#208.67.72.50    128.227.205.3    2 u    8   64  377   55.752   -3.484   3.526
+195.21.137.209  195.66.241.10    2 u    6   64  377   30.329    1.189   3.308
#ntpool1.603.new 204.9.54.119     2 u    6   64  377   13.701    2.929   3.439
+time.richiemcin 209.51.161.238   2 u    9   64  357   23.790    0.529   2.967
+darwin.kenyonra 127.67.113.92    2 u   14   64  357   41.307   -0.001   3.179
+static-72-87-88 128.59.0.245     2 u    4   64  377   31.062   -1.641   3.249
+y.ns.gin.ntt.ne 249.224.99.213   2 u   66   64  377    6.620    1.957   4.289
#alphyn.canonica 17.253.34.253    2 u   30   64  377   25.755   -1.800   3.689
+i.will.not.be.e 213.251.128.249  2 u    3   64  377   28.559   -2.690   3.311
+208.67.72.43    152.2.133.54     2 u    3   64  377   55.397   -1.380   3.396
+horp-bsd01.horp 152.2.133.54     2 u   14   64  377   28.801   -0.031   3.538
+lithium.constan 198.30.92.2      2 u   14   64  377   25.507   -2.083   3.563
+ns1.backplanedn 173.162.192.156  2 u   13   64  377   29.019    1.230   3.559
+time.nullrouten 216.218.254.202  2 u    8   64  377   49.467    3.116   3.677
+chilipepper.can 17.253.34.125    2 u   26   64  377   93.719    0.661   3.774
#neoknet.com     129.250.35.251   3 u    7   64  377   36.605    4.435  11.929

ubuntu:~# ntptime
ntp_gettime() returns code 0 (OK)
  time e1317a86.a7033a48  Sat, Sep 21 2019 23:43:50.652, (.652393818),
  maximum error 289516 us, estimated error 16 us, TAI offset 0
ntp_adjtime() returns code 0 (OK)
  modes 0x0 (),
  offset 0.000 us, frequency -15.952 ppm, interval 1 s,
  maximum error 289516 us, estimated error 16 us,
  status 0x2001 (PLL,NANO),
  time constant 3, precision 0.001 us, tolerance 500 ppm,

OBTW, was able to reproduce, perhaps a similar error, by downloading the latest version of ntp manually and trying to install in a crude way:

ubuntu:/etc/init.d# ntptime
ntp_gettime() returns code 5 (ERROR)
  time e13182c8.b37ccc04  Sun, Sep 22 2019  0:19:04.701, (.701123517),
  maximum error 16000000 us, estimated error 16000000 us, TAI offset 37
ntp_adjtime() returns code 5 (ERROR)
  modes 0x0 (),
  offset 0.000 us, frequency 0.000 ppm, interval 1 s,
  maximum error 16000000 us, estimated error 16000000 us,
  status 0x2041 (PLL,UNSYNC,NANO),
  time constant 3, precision 1.000 us, tolerance 500 ppm,

This error happened when I tried to use the original directory, mixing the old install with the new install.

However, when restarted ntpd in a totally clean install directory, it worked fine.

Now running latest version:

ubuntu:/etc/init.d# ntpd --version
ntpd 4.2.8p13@1.3847 Sun Sep 22 05:03:19 UTC 2019 (1)

Reference: NTP Software Downloads

This version we're using in our side.. Could please someone give solution for this issue

ntp-4.2.6p5-28.el7.centos.x86_64
ntpdate-4.2.6p5-28.el7.centos.x86_64

--- Post updated at 09:40 AM ---

Really thanks for your reply.. We're running ntp around 50 nodes.. it's difficult to reinstall in all. Can you tell why it's happening.

This version we're using in our side.. Could please someone give solution for this issue

ntp-4.2.6p5-28.el7.centos.x86_64
ntpdate-4.2.6p5-28.el7.centos.x86_64

Your version of NTP was released in 2011, nearly a decade (8 years) ago:

[   ]	ntp-4.2.6p5-RC1.tar.gz	2011-10-18 19:33	4.0M	 
[   ]	ntp-4.2.6p5-RC1.tar.gz.md5	2011-10-18 19:33	57	 
[   ]	ntp-4.2.6p5-RC2.tar.gz	2011-11-30 22:19	4.0M	 
[   ]	ntp-4.2.6p5-RC2.tar.gz.md5	2011-11-30 22:19	57	 
[   ]	ntp-4.2.6p5-RC3.tar.gz	2011-12-08 21:22	4.0M	 
[   ]	ntp-4.2.6p5-RC3.tar.gz.md5	2011-12-08 21:22	57	 
[   ]	ntp-4.2.6p5.tar.gz	2011-12-24 18:52	4.0M	 
[   ]	ntp-4.2.6p5.tar.gz.md5	2011-12-24 18:52	53	 

For security and other reasons, you must upgrade to the latest version.

Your version of ntp is NOT SUPPORTED by anyone.

It is your responsibility to upgrade, not complain how many servers you have running with obsolete code (sorry to tell you directly, but it is true).

Reference: Index of /~ntp/ntp_spool/ntp4/ntp-4.2

You might want to check out this page of ntp vulnerabilities:

NTP : Products and vulnerabilities

Thank you!!. sure. Let me upgrade and let you know. Hope this is the latest version : -ntpd 4.2.8p13@1.3847

Yes.

Hi Folks,

Just a quick addition to the above, I have currently been installing a couple of RHEL 7.5 servers. They are both running ntp and have been installed from a RHEL 7.5 image and then fully updated from the current Red Hat online repos, so I decided just to tick this one off the build and when I checked the server I find.

[root@fbakirpomd4 bin]# ntpd --version
ntpd 4.2.6p5

exit 0
[root@fbakirpomd4 bin]# systemctl status ntpd
�- ntpd.service - Network Time Service
   Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-09-10 13:46:23 BST; 1 weeks 5 days ago
 Main PID: 32639 (ntpd)
   CGroup: /system.slice/ntpd.service
           └─32639 /usr/sbin/ntpd -u ntp:ntp -g

Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: Listen and drop on 1 v6wildcard :: UDP 123
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: Listen normally on 2 lo 127.0.0.1 UDP 123
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: Listen normally on 3 bond0 10.10.184.51 UDP 123
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: Listen normally on 4 bond0:0 10.10.184.52 UDP 123
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: Listening on routing socket on fd #21 for interface updates
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: 0.0.0.0 c016 06 restart
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
Sep 10 13:46:23 fbakirpomd4 ntpd[32639]: 0.0.0.0 c011 01 freq_not_set
[root@fbakirpomd4 bin]# ntpstat
unsynchronised
  time server re-starting
   polling server every 8 s
[root@fbakirpomd4 bin]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 10.107.129.61   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
 10.107.130.62   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
[root@fbakirpomd4 bin]# ntptime
ntp_gettime() returns code 5 (ERROR)
  time e132f4ba.dfb26000  Mon, Sep 23 2019  8:37:30.873, (.873816),
  maximum error 16000000 us, estimated error 16000000 us, TAI offset 0
ntp_adjtime() returns code 5 (ERROR)
  modes 0x0 (),
  offset 0.000 us, frequency 0.000 ppm, interval 1 s,
  maximum error 16000000 us, estimated error 16000000 us,
  status 0x41 (PLL,UNSYNC),
  time constant 7, precision 1.000 us, tolerance 500 ppm,
[root@fbakirpomd4 bin]#

These servers are built from an already supplied Kick Start file, which to be fair is pretty large - much larger than it needs to be to be fair with a huge amount of configuration stuff in the file.

The repo's are setup in the Kick Start as follows;

[root@fbakirpomd4 bin]# yum repolist
Loaded plugins: product-id, search-disabled-repos, subscription-manager, versionlock
repo id                                            repo name                                                                               status
rhel-7-server-eus-rpms/x86_64                      Red Hat Enterprise Linux 7 Server - Extended Update Support (RPMs)                      21,608
rhel-7-server-rpms/x86_64                          Red Hat Enterprise Linux 7 Server (RPMs)                                                21,088
repolist: 42,696
[root@fbakirpomd4 bin]#

So I'll have a hunt around to try and come up with a reason for the package not updating - a yum update was run against the server.

Regards

Gull04

FWIW, I had the same problem with apt on ubuntu, upgrading to an older and less secure version so I went to the NTP home site and downloaded and installed, in a different directory structure,

4.2.8p38

The reason was that there has been myriad vulnerabilities and flaws found and fixed in NTP since 2011 when 4.2.6p5 was released.

Hmm,

This might cause me a minor problem, due to the nature of the servers although these are development servers - the production servers keep things running. So it may well be that I'll have to change to Chrony.

I'll investigate my options and report back.

Regards

Gull04

That is actually a good idea for me as well:

chrony - Comparison of NTP implementations

I may switch to chrony .... because I have never really trusted ntp (because of the many ntp code vulnerabilities over the years).

Also, not sure how much confidence we can have in this, but cvedetails reports than 0 Chrony vulnerabilities has been reported after 2016:

Tuxfamily Chrony : CVE security vulnerabilities, versions and detailed reports

Your ntpq output in post#1 is missing a column!?

Are you sure your current ntpd is the only process listening on port 123?

pgrep '(ntp|chrony)d?$'
netstat -antp | grep -w 123

Hi Folks,

I've been round the houses on this, the decision has been to change from NTP to Chrony. - due mainly to security concerns.

So here's a quick breakdown.

[root@fbakirpomd4 bin]# systemctl stop ntpd
[root@fbakirpomd4 bin]# chkconfig ntpd off
Note: Forwarding request to 'systemctl disable ntpd.service'.
[root@fbakirpomd4 bin]# systemctl enable chronyd
[root@fbakirpomd4 bin]# systemctl start chronyd
[root@fbakirpomd4 bin]# ps -ef | grep cronyd
root     23225 26147  0 10:11 pts/1    00:00:00 grep --color=auto cronyd
[root@fbakirpomd4 bin]# ps -ef | grep chronyd
chrony   23208     1  0 10:11 ?        00:00:00 /usr/sbin/chronyd
root     23253 26147  0 10:11 pts/1    00:00:00 grep --color=auto chronyd
[root@fbakirpomd4 bin]# cat /etc/chrony.conf
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
# server 0.rhel.pool.ntp.org iburst
# server 1.rhel.pool.ntp.org iburst
# server 2.rhel.pool.ntp.org iburst
# server 3.rhel.pool.ntp.org iburst
##############################################################
#
# Added local hosts for xxxxxxxx xxxxx chrony servers
#
##############################################################
server 10.1.100.134 iburst
server 10.235.100.19 iburst
##############################################################

# Record the rate at which the system clock gains/losses time.
driftfile /var/lib/chrony/drift

# Allow the system clock to be stepped in the first three updates
# if its offset is larger than 1 second.
makestep 1.0 3

# Enable kernel synchronization of the real-time clock (RTC).
rtcsync

# Enable hardware timestamping on all interfaces that support it.
#hwtimestamp *

# Increase the minimum number of selectable sources required to adjust
# the system clock.
#minsources 2

# Allow NTP client access from local network.
#allow 192.168.0.0/16

# Serve time even if not synchronized to a time source.
#local stratum 10

# Specify file containing keys for NTP authentication.
#keyfile /etc/chrony.keys

# Specify directory for log files.
logdir /var/log/chrony

# Select which information is logged.
#log measurements statistics tracking
[root@fbakirpomd4 bin]# systemctl enable chronyd
[root@fbakirpomd4 bin]# systemctl start chronyd
[root@fbakirpomd4 bin]# ps -ef | grep cronyd
root     23225 26147  0 10:11 pts/1    00:00:00 grep --color=auto cronyd
[root@fbakirpomd4 bin]# ps -ef | grep chronyd
chrony   23208     1  0 10:11 ?        00:00:00 /usr/sbin/chronyd
root     23253 26147  0 10:11 pts/1    00:00:00 grep --color=auto chronyd
[root@fbakirpomd4 bin]# chronyc tracking
Reference ID    : 0AEB6413 (ntp2.xxxxxxxxxxxxx.co.uk)
Stratum         : 2
Ref time (UTC)  : Mon Sep 23 09:11:35 2019
System time     : 0.000000041 seconds slow of NTP time
Last offset     : +0.000060960 seconds
RMS offset      : 0.000060960 seconds
Frequency       : 6.443 ppm fast
Residual freq   : -0.865 ppm
Skew            : 0.017 ppm
Root delay      : 0.000187665 seconds
Root dispersion : 0.000315763 seconds
Update interval : 1.8 seconds
Leap status     : Normal
[root@fbakirpomd4 bin]# man chkconfig
[root@fbakirpomd4 bin]# chkconfig chronyd on
Note: Forwarding request to 'systemctl enable chronyd.service'.
[root@fbakirpomd4 bin]#

Checked the servers this morning and all seems well.

Regards

Gull04

1 Like

Thanks for the update.

I think I will follow you and do the same on some of my Ubuntu boxes.

Hi Neo,

Our servers are nearly all configured with NTP, but as part of the upgrade process on our RHEL estate we are also screwwing down the security so Chrony it is.

We recently had an Audit carried out and the above version of NTP didn't come out of it well. The Cyber Security Team has endorsed a list of trusted sites for sourcing software packages and as a result upgrading NTP was going to be a more tortuos process than installing and configuring Chrony.

The configuration of Chrony is really straight forward, the config file is included.

Regards

Gull04

1 Like

Here is what I did (as quick test) on a ubuntu server (because did not want to update system with apt in this case, on this particular server):

wget https://download.tuxfamily.org/chrony/chrony-3.5.tar.gz
tar xvzf chrony-3.5.tar.gztar xvzf chrony-3.5.tar.gz
cat INSTALL
./configure --disable-readline other-options
make all
vi /etc/chrony.conf
ps aux | grep chron* | grep -v grep

root     28922  0.0  0.0  97024  2620 ?        S    23:29   0:00 /usr/local/sbin/chronyd

cd /var/log
grep chrony *log

syslog:Sep 25 23:29:44 www chronyd[28922]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG)
syslog:Sep 25 23:29:44 www chronyd[28922]: Initial frequency 16.866 ppm
syslog:Sep 25 23:29:49 www chronyd[28922]: Selected source 104.168.88.15
cat /etc/chrony.conf
pool pool.ntp.org iburst
makestep 1.0 3
rtcsync
port 0

References (2):

chrony - Download
chrony - Installation

TODO: Change this so chrony does not run as root (see next post)...

On a second ubuntu server, using apt:

apt install chrony
ps aux | grep chron | grep -v grep
_chrony  19064  0.0  0.1 108304  3092 ?        S    04:55   0:00 /usr/sbin/chronyd
cat /etc/chrony/chrony.conf

root@localhost:/etc/chrony# cat chrony.conf
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.

# This will use (up to):
# - 4 sources from ntp.ubuntu.com which some are ipv6 enabled
# - 2 sources from 2.ubuntu.pool.ntp.org which is ipv6 enabled as well
# - 1 source from [01].ubuntu.pool.ntp.org each (ipv4 only atm)
# This means by default, up to 6 dual-stack and up to 2 additional IPv4-only
# sources will be used.
# At the same time it retains some protection against one of the entries being
# down (compare to just using one of the lines). See (LP: #1754358) for the
# discussion.
#
# About using servers from the NTP Pool Project in general see (LP: #104525).
# Approved by Ubuntu Technical Board on 2011-02-08.
# See http://www.pool.ntp.org/join.html for more information.
pool ntp.ubuntu.com        iburst maxsources 4
pool 0.ubuntu.pool.ntp.org iburst maxsources 1
pool 1.ubuntu.pool.ntp.org iburst maxsources 1
pool 2.ubuntu.pool.ntp.org iburst maxsources 2

# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys

# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift

# Uncomment the following line to turn logging on.
#log tracking measurements statistics

# Log files location.
logdir /var/log/chrony

# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0

# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync

# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3

#If you don't need to serve time to NTP clients or peers, you can add port 0 to the chrony.conf file 
# to completely disable the NTP server functionality and prevent NTP requests from reaching chronyd
port 0

Conclusion: On ubuntu, better to install with apt if possible. It's easier, more secure and more comprehensive than a quick manual install (like in the post above);

cd /var/log
grep chrony *log

auth.log:Sep 26 04:55:13 localhost groupadd[18713]: group added to /etc/group: name=_chrony, GID=115
auth.log:Sep 26 04:55:13 localhost groupadd[18713]: group added to /etc/gshadow: name=_chrony
auth.log:Sep 26 04:55:13 localhost groupadd[18713]: new group: name=_chrony, GID=115
auth.log:Sep 26 04:55:13 localhost useradd[18717]: new user: name=_chrony, UID=111, GID=115, home=/var/lib/chrony, shell=/usr/sbin/nologin
auth.log:Sep 26 04:55:13 localhost usermod[18723]: change user '_chrony' password
auth.log:Sep 26 04:55:13 localhost chage[18728]: changed password expiry for _chrony
auth.log:Sep 26 04:55:13 localhost chfn[18731]: changed user '_chrony' information
dpkg.log:2019-09-26 04:55:13 install chrony:amd64 <none> 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status half-installed chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 configure chrony:amd64 3.2-4ubuntu4.2 <none>
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status unpacked chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:13 status half-configured chrony:amd64 3.2-4ubuntu4.2
dpkg.log:2019-09-26 04:55:15 status installed chrony:amd64 3.2-4ubuntu4.2
kern.log:Sep 26 04:55:14 localhost kernel: [9630131.911799] audit: type=1400 audit(1569473714.650:59): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbinchronyd" pid=18964 comm="apparmor_parser"
syslog:Sep 26 04:55:14 localhost kernel: [9630131.911799] audit: type=1400 audit(1569473714.650:59): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/chronyd" pid=18964 comm="apparmor_parser"
syslog:Sep 26 04:55:15 localhost systemd[1]: Starting chrony, an NTP client/server...
syslog:Sep 26 04:55:15 localhost chronyd[19064]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 -DEBUG)
syslog:Sep 26 04:55:15 localhost chronyd[19064]: Initial frequency -0.501 ppm
syslog:Sep 26 04:55:15 localhost systemd[1]: Started chrony, an NTP client/server.
syslog:Sep 26 04:55:23 localhost chronyd[19064]: Selected source 198.50.238.163

.. and just for fun, installed chrony on macOS as follows:

brew cask install chronycontrol

Reference:

chronyd on MacOS X

1 Like

Hi Neo,

Thanks for the macOS info, I'll maybe get round to installing on my MacBook in the not too distand future.

Regards

Gull04