NTPD: System time has not been synced/updated correctly. │
│ │
│ To prevent further issues with software installations, │
│ DietPi-Software will now exit. │
│ │
│ If problems persist, check the NTPD log: │
│ /var/log/ntpd.log │
│ │
│ To override this error, run the following command: │
│ echo 0 > /etc/dietpi/.ntpd_exit_status
Apparently the time can not be synced correctly. Even after reinstalling NTPD it does not change and I receive this message every time when I log in.
Firstly, make sure you are running DietPi v150, as we fixed a known problem where NTPD wouldnt start in some cases.
Failing that, switch to SystemD-Timesync: dietpi-config > advanced > time sync mode > 4 Daemon + Drift
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal and Bitcoin.
johnvick wrote:Is this needed on devices that have RTC?
John
Hi John,
Yes initially, to set the time. Also ensures the RTC does not drift out of time incorrectly over a period.
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
How do I set the time on my Raspberry Pi with dietpi - NTPD does not work, it currently thinks the date is 02/04/2018.
reboot, retry, reinstall - nothing !
I've tried all the options in dietpi-config, I've tried the ntp server my mac uses (apple euro) I've tried the server my years old router uses 143.210.16.201 - nothing works.
How do i just get the bloody box to understand today's date and time.
I've tried "date --set="23 June 1988 10:00:00" format and that got ignored.
Please help - I have spent every night this week messing with this thing, but enough is enough - reply and you could save the life of my Pi - cos this weekend it will be no more !
to set the time. The issue is, if the time is too far out, NTP will not set it unless you force it to. Once set, it writes it to file then uses that as the starting point next time so it is only on initial install you get a significant problem. On boot on V6 instances, I regularly see an NTP could not be set type error when using the daemon + drift setting.
