@hall1458 Wow. Dude, I’m sorry that nobody has stepped in to help you out. I’m not much of a *nix guy, but I’ve been dealing with this at work for various reasons. I’ll do what I can.
The NTP service should synchronize your Pi’s clock with one of many time servers out on the internet. If you get a terminal onto your Pi and type
ps ax | grep ntpd you should see this line in return:
602 ? Ss 0:04 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111. Some parts will be different. This is good. If all you see is
grep --color=auto ntp then the NTP service isn’t running. Post back here and we’ll get that fixed.
Assuming that NTP is running on your pi, you will want to check the configuration of your NTP server. Type
nano /etc/ntp.conf. If you see a blank screen/file, then you have a problem. Assuming you do see a file, you want to look for the following lines:
# pool: server 0.debian.pool.ntp.org iburst server 1.debian.pool.ntp.org iburst server 2.debian.pool.ntp.org iburst server 3.debian.pool.ntp.org iburst
These are the servers that your Pi will be checking for a valid time. You can manually check them as well. Exit the
/etc/ntp.conf file and type
ntpq -pn and wait. You should see something like this:
remote refid st t when poll reach delay offset jitter ============================================================================== +126.96.36.199 .PPS. 1 u 856 1024 377 18.624 -1.660 5.766 +188.8.131.52 184.108.40.206 2 u 468 1024 377 27.636 0.276 6.356 *220.127.116.11 .GPS. 1 u 839 1024 377 37.422 0.189 4.440 +18.104.22.168 22.214.171.124 2 u 713 1024 377 48.940 -1.173 2.743
At least one of those lines should have an asterisk at the beginning. Give it a go and report back.