[Raspi Bug?]Date/Time is way off on new install. NTP shows INIT #295
Description
[edit]I found a thread on the Raspi forum that had the same problem and a workaround that solved my issue:
https://www.raspberrypi.org/forums/viewtopic.php?t=141454&f=28#p938961
As workaround, add the following command
/sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p udp --dport 123 -j TOS --set-tos 0x00
to the file
/etc/rc.local
I rebooted and it worked. OctoPrint updated just fine now.
Weird stuff, in any case. Is it just all coincidence or is something off with the Raspi 3?...
I'm leaving this open because maybe that workaround can be put into the disk image? As usual, I don't actually understand what it does, so I can't judge if it'll cause new problems..
Raspi 3, fresh install. Tried to update OctoPrint, failed.
I noticed the date is wrong - about a year back - and wouldn't update.
I set the timezone/location via raspi-config, but that didn't change.
I restarted the NTP service, no effect.
"sudo ntpd -gq" just hangs apparently
I get this all the time:
pi@AuxEquip9:~ $ sudo ntpq -p
remote refid st t when poll reach delay offset jitter
service02.vie.x .INIT. 16 u - 64 0 0.000 0.000 0.000
boxi.trexler.at .INIT. 16 u - 64 0 0.000 0.000 0.000
time2.mediainve .INIT. 16 u - 64 0 0.000 0.000 0.000
server.samoylyk .INIT. 16 u - 64 0 0.000 0.000 0.000
(The servers change, though. It's not always the same. Not sure why, I did set the location twice, just to try again.)
I don't think it's a firewall issue, as the old Raspi (1) didn't seem to have that issue - at least I never noticed anything.
Nor did I find any settings on the firewall that should prevent NTP from working, unless it's on the Raspi itself which I doubt.