# system\_clock\_sync\_state warning on Synology NAS
**URL:** https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844
**Category:** Help
**Created:** [November 4, 2023, 9:34am UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844 "2023-11-04T09:34:43Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@pk1966](https://community.netdata.cloud/u/pk1966)
#### Post date: [November 4, 2023, 9:34am UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844/1 "2023-11-04T09:34:44Z")
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
---
### Author:  [@pk1966](https://community.netdata.cloud/u/pk1966)
#### Post date: [November 10, 2023, 5:25pm UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844/2 "2023-11-10T17:25:39Z")
This is still happening - any ideas anyone?
---
### Author:  [@digitaljdr](https://community.netdata.cloud/u/digitaljdr)
#### Post date: [July 30, 2024, 2:11am UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844/3 "2024-07-30T02:11:54Z")
I just installed netdata on my synology and have this same alert. Anyone have any idea?
---
### Author:  [@buckbaggen](https://community.netdata.cloud/u/buckbaggen)
#### Post date: [August 15, 2024, 12:14pm UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844/4 "2024-08-15T12:14:47Z")
This worked for me:
Install Entware (package manager you can use when you connect trough SSH with your NAS), is used this guide:
> **[Using Entware on Synology NAS - Technorabilia](https://www.technorabilia.com/using-entware-on-synology-nas/)**
>
> How to install Entware packages on your Synology NAS. Reasons for using Entware. Example package installation using use Nano editor package.
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](http://0.ubuntu.pool.ntp.org) iburst
> pool [1.ubuntu.pool.ntp.org](http://1.ubuntu.pool.ntp.org) iburst
> pool [2.ubuntu.pool.ntp.org](http://2.ubuntu.pool.ntp.org) iburst
> pool [3.ubuntu.pool.ntp.org](http://3.ubuntu.pool.ntp.org) iburst
>
> # Use 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
---
### Author:  [@ilyam8](https://community.netdata.cloud/u/ilyam8)
#### Post date: [August 15, 2024, 5:15pm UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844/5 "2024-08-15T17:15:03Z")
> 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](https://github.com/netdata/netdata/issues/12604#issuecomment-1427851921) for technical details.
---
### Author:  [@keithajmani](https://community.netdata.cloud/u/keithajmani)
#### Post date: [January 13, 2025, 9:55pm UTC](https://community.netdata.cloud/t/system-clock-sync-state-warning-on-synology-nas/4844/6 "2025-01-13T21:55:49Z")
Wanted to update this with a simpler solution that builds on the reply from @buckbaggen above.
- chrony seems installed by default now on Synology DSM 7.x +
- I only needed to create **/etc/chrony.conf.user** with the following two lines only, included from the earlier solution:
```auto
makestep 1 3
rtcsyncde here
```
Then I did a quick restart of the service, as above:
```auto
systemctl restart chronyd
```
This was on a DS920+ and DS416play. The errors have went away in netdata within seconds after restarting chrony. Will see if it sticks.
```auto
netdata-parent2 netdata[13943]: ALERT 'system_clock_sync_state' of instance 'system.clock_sync_state' on node 'NODENAME', transitioned from WARNING to CLEAR
```