When a Wall Display/CPU/DAKboard OS device has been powered off or disconnected from the internet for a length of time, the internal clock may gain, or lose time. When reconnected to the internet, the DAKboard device will automatically update the time. However, sometimes this update process is delayed and an "incorrect date/time" or "Your clock is behind" message will appear.
If your device is connected to the internet, leave it powered on for about 5-10 minutes to give it enough time to sync, then restart it by unplugging the power and plugging it back in.
If the time still does not update, you may be unable to access the time servers from your location due to a networking issue. If you are comfortable with accessing the command-line interface for the device and troubleshooting the network issue, please reach out to us for the basic steps to access the command line and then review the following testing instructions:
Testing NTP:
Identify the status of the service, and note the 'System clock synchronized' and the 'NTP Service' sections for feedback:
timedatectl status
Local time: Tue 2021-06-08 12:46:21 EDT
Universal time: Tue 2021-06-08 16:46:21 UTC
RTC time: n/a
Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
If the NTP service shows off try to restart the service or the device. Restarts of the service are performed by running the following:
sudo timedatectl restart
NTP will have a number of fallback servers, they are all located in the following configuration file and are used for obtaining time sync data. You can find them by following the below example, most systems will be
- 0.debian.pool.ntp.org
- 1.debian.pool.ntp.org
- 2.debian.pool.ntp.org
- 3.debian.pool.ntp.org
(Advanced: NTP servers may be manually changed by uncommenting the 'FallbackNTP' line by using an editor like Nano and making changes to the domains listed):
pi@dakboard:~ $ cat /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.
[Time]
#NTP=
#FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048Pull any number of the servers and perform IP from ping to find the IP as shown. This will tell you if you can reach the NTP server with a ping, and the IP for additional testing in the next step:
ping debian.pool.ntp.org
PING 1.debian.pool.ntp.org (38.229.53.9) 56(84) bytes of data.
64 bytes from 38.229.53.9 (38.229.53.9): icmp_seq=1 ttl=53 time=74.10 ms
Perform a UDP Netcat to check the UDP 23 port which is used for the NTP of the IP you gained from the ping in the previous step, below is a successful response example for IP 38.229.53.9:
nc -z -v -u 38.229.53.9 23
Connection to 38.229.53.9 23 port [udp/*] succeeded!More advanced details on the timedatectl service are available to be reviewed at the following:
https://wiki.archlinux.org/title/systemd-timesyncd
Having Trouble?