I am running netdata across 3 nodes (1x rpi, 1x small ubuntu server and 1x Synology DS920+).
I am having an issue where the Synology NAS is always showing a warning against the system_clock_sync_state metric. I have checked that the NAS is using ntp (see screenshot)
What else can I check? Is it an erroneous warning?
All netdata nodes running in docker containers using “v1.43.0-148-nightly3”.
Synology DSM is Version: 7.2-64570 Update 3
This is still happening - any ideas anyone?
I just installed netdata on my synology and have this same alert. Anyone have any idea?
This worked for me:
Install Entware (package manager you can use when you connect trough SSH with your NAS), is used this guide:
When Entware is installed, you can install the chrony package with
sudo opkg install chrony
EDIT:
This steps also needed:
sudo mkdir /var/log/chrony
sudo mkdir /var/lib/chrony
sudo opkg install nano
sudo nano /etc/chrony.conf
Delete everything in the conf file and place this:
Welcome to the chrony configuration file. See chrony.conf(5) for more
information about usable directives.
Include configuration files found in /etc/chrony/conf.d.
confdir /etc/chrony/conf.d
Use Debian vendor zone.
pool 0.ubuntu.pool.ntp.org iburst
pool 1.ubuntu.pool.ntp.org iburst
pool 2.ubuntu.pool.ntp.org iburst
pool 3.ubuntu.pool.ntp.org iburstUse time sources from DHCP.
sourcedir /run/chrony-dhcp
Use NTP sources found in /etc/chrony/sources.d.
sourcedir /etc/chrony/sources.d
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
Save NTS keys and cookies.
ntsdumpdir /var/lib/chrony
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
Get TAI-UTC offset and leap seconds from the system tz database.
This directive must be commented out when using time sources serving
leap-smeared time.
leapsectz right/UTC
sudo systemctyl restart chronyd
Is it an erroneous warning?
That is the system clock synchronization state according to the kernel. Netdata doesn’t do any calculation; it is just a system call that reports whatever the system clock state is according to the kernel. See this comment for technical details.