Just be wary everyone. We do not know what is or isn’t included in the Oct2018 image as there is no build guide despite significant changes.
This is the first Stretch image and it is no longer RO.
The older images used ntpd and had a custom ntp-backup utility installed to deal with the fact the OS was RO so the time was saved to disk each hour. There was also another “fix” added along the way to force a NTP time correction via a cronjob after bootup too. Since Stretch uses systemd-timesync by default and we have no idea how much of the older build guide was used in the new image it’s not easy to know what exactly is required. Is ntp even installed? Should it even be installed if systemd-timesync is used?
This has also come up in passing on another thread a few hours ago too.
[edit] Actually that cronjob to force an update apparently ran every hour!
So that begs the question why isn’t the clock updated? Is it a network issue or is it a mismatched correction procedure? (rhetorical Q, just highlighting it may not be a simple network issue). Perhaps the ntp_update and/or ntp_backup utilities are failing because the rpi-rw command doesn’t exist? Just an example!
@Wesley_Phillip if you can ssh in is there any info at /var/log/ntp_update.log? (I’m not even sure it’s still used, sorry)