Ever since a started using FFP on the pi I've never been able to get the time to update without manually updating and restarting DNS even without making any changes. Not a huge problem since the time is good for the season once I get it set, just annoying. I have the same problem with Pi2 running V1.10 and Pi3 running V2.4.
Can you ssh into that pi and ping the NTP server? (ping Time.google.com). If you can't ping the hostname, then ping the IP address, 216.239.35.12. If neither work, then you know you are not able to get out of the private network and onto the internet. That would be the next troubleshooting step.
I tried the ssh, not sure what it shows
From ssh run this command:
ntpq
then type in:
peers.
Look for a * in the far left side next to the remote this means it's synced to that server. here's mine:
This is from a 2.4 install. by default the OS has 4 pool entries in the ntp config file, so it should work as long as your firewall/isp isn't blocking ntp.
marx1 wrote:From ssh run this command:ntpq
then type in:
peers.
Look for a * in the far left side next to the remote this means it's synced to that server. here's mine:
This is from a 2.4 install. by default the OS has 4 pool entries in the ntp config file, so it should work as long as your firewall/isp isn't blocking ntp.
gassy wrote:
So that's odd, it's countering what your previous post about the ntpq -p (basically the same command) outputted. ntpq askes the NTP service on the PI things, and peers asks for who it's synced to.,
I'm thinking there is a issue with the ntp service somewhere; but let's do some basic network testing to rule everything else out.
Try pinging 0.debian.pool.ntp.org and 1.debian.pool.ntp.org it should resolve an IP, but it may not respond to pings (due to people blocking it) but if it does this - then DNS and basic firewalling is working. If it doesn't this means DNS or routing is broken. Verify your DNS (I saw it was pointed to your router, you can try 8.8.8.8 and 8.8.4.4). and make sure you can ping 8.8.8.8.
If the above is good, then NTP is getting blocked on your firewall or your ISP. I don't know why this would be IMO. If you want to fight with the firewall you can; or an easier solution would be to get a RTC for the FPP. I do this + a gps module for a multisync'd show I do that has no internet access - and requires time sync.
Wi-Fi is disabled because the country is not set.
Use raspi-config to set the country before use.
fpp@FPP:~ $ ping 0.debian.pool.ntp.org
ping: 0.debian.pool.ntp.org: Temporary failure in name resolution
fpp@FPP:~ $
I just noticed the wi-fi message. Otherwise I'm not sure what any of this means.
so it's your DNS server settings. on your first post you have a picture. On the very bottom of it, it shows DNS settings. Change the first entry to be 8.8.8.8 and the second one to be 8.8.4.4, these are google's dns servers. reboot and your time should be good.
I just read the country code is set when you configure your wireless over on the falcon board. So if your not using wireless, ignore it.

