After I change the dietpi-config /advance/time sync mode / boot + daily.
After reboot I get these error messages on boot screen
attached the boot screen. It will go until 60 tries are made then does finally boot, and has correct time.
What do I do to fix this?
Dave
Hi,
many thanks for your message. As indicated by the error message, pls do:
systemctl daemon-reload
/boot/dietpi/func/run_ntpd 1
I just did what you asked.
then rebooted.
Same thing nothing changed.
did you still have the error message about the changed drop in file? Pls do following and post the output.
systemctl restart systemd-timesyncd.service
systemctl status systemd-timesyncd.service
that looks fine, your time was synced and service is running. Pls can you do another reboot. Once back only, export the journal and attach the log file pls.
journalctl > /tmp/log.txt
Is this what you want?
It does not look right.
As you can tell I am very new.
I sent you a PM asking if you need to teamviewer into my computer and then SSH into the PI
to get this I did the following:
Cd /tmp
nano log.txt
that looks strange. Probably something goes wrong on exporting the the journal. Usually journalctl should give you the complete boot log.
Here is another log file. Since I posted that last one, I have learned a little bit more on how to do what you asked.
this time I ran the command you listed:
journalctl > /tmp/log.txt
and then went to the dir /tmp
then I did:
nano /tmp/log.txt
this is what is looks like. Please help me get what you need.
Aim is to download entire file and attach it to this post. The output is quite long and will not fit on one screen
Got it. I took me some thinking but here. WOW. see how new I am.
log.txt (60 KB)
well your log seems pretty fine.
Most of the time your system is waiting on network. It takes around 20-25 secounds to get WiFi up and running
Sep 11 16:08:30 DietPi dhclient[657]: Listening on LPF/wlan0/dc:a6:32:72:f8:e7
Sep 11 16:08:30 DietPi dhclient[657]: Sending on LPF/wlan0/dc:a6:32:72:f8:e7
Sep 11 16:08:30 DietPi dhclient[657]: Sending on Socket/fallback
Sep 11 16:08:30 DietPi dhclient[657]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Sep 11 16:08:30 DietPi dhclient[657]: DHCPOFFER of 192.168.2.146 from 192.168.2.1
Sep 11 16:08:30 DietPi dhclient[657]: DHCPREQUEST for 192.168.2.146 on wlan0 to 255.255.255.255 port 67
Sep 11 16:08:30 DietPi dhclient[657]: DHCPACK of 192.168.2.146 from 192.168.2.1
Sep 11 16:08:31 DietPi dhclient[657]: bound to 192.168.2.146 -- renewal in 33883 seconds.
once WiFi connection established, time sync succeeded without issues.
Sep 11 16:08:39 DietPi DietPi-Boot[463]: [ INFO ] DietPi-Run_NTPD | Waiting for completion of systemd-timesyncd (29/60)
Sep 11 16:08:55 DietPi systemd-timesyncd[478]: Synchronized to time server for the first time 163.237.218.19:123 (2.north-america.pool.ntp.org).
Sep 11 16:08:55 DietPi DietPi-Boot[463]: [ INFO ] DietPi-Run_NTPD | Waiting for completion of systemd-timesyncd (30/60)
Sep 11 16:08:56 DietPi DietPi-Boot[463]: [ OK ] DietPi-Run_NTPD | systemd-timesyncd synced
Sep 11 16:08:56 DietPi systemd[1]: Stopping Network Time Synchronization...
Sep 11 16:08:56 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.
Sep 11 16:08:56 DietPi systemd[1]: Stopped Network Time Synchronization.
Sep 11 16:08:56 DietPi DietPi-Boot[463]: [ OK ] Network time sync | Completed
as you can see, time is jumping from Sep 11 16:08:39 to Sep 11 16:08:55.
I can’t see issues on time syncronization.
So I have tried this with wire also.
Same results.
Is there a away to change when it query.
Like add a command to autostart file?
Not sure what you mean. As I said, the log you posted was quite ok and time synchronization was working.
I would like to get rid of those 60 attempts.
It slows boot time 20 seconds…
I am using this as a digital dashboard.
And 20 seconds every boot is not going to work.
The boot is not exactly waiting for ntp.
If however you feel that this is slowing you down you can go to dietpi-config - Advanced Options - Time sync mode and select Mode 0 to deal yourself how the time will be synchronized.
I have done that, that is how I get 28 seconds of bootup time. But when after boot up time is FEB 14 2019 1400 hrs.
What other options do I have to get time updated? So I just found a few threads down /DietPi/dietpi/func/run_ntpd 1
I just did that command and my clock is updated.
Now how to I get this command to autorun after bootup is completed?
SOLVED
Here is what I did
Using the file manager on taskbar near start menu.
open that. Goto / dir then make your way to
/var/lib/dietpi-autostart/custom.sh
open custom.sh with leafpad.
add to the bottom line
startx /DietPi/dietpi/func/run_ntpd 1
save and then reboot. in less then 5 min time will correct itself
there are a couple of thinks your can do to increase boot time