2014-04-20, 16:59
Reposting this from OE forums, in hope to get some more help:
Today I ran into a time synchronization issue on RPi B running OE 3.2.4. On start up, I'm getting the generic "1 Jan 1970" date. The Pi has internet and everything else works just like before. This is not the first time I am getting this issue, but this time it's the longest instance.
Further inspection revealed there are problems between the Pi and the NTP servers. This is the output of running "ntpdate -d 0.asia.pool.ntp.org":
As you can see, the servers get dropped, ultimately resulting in the Pi not being able to pull data from them. Like I said, absolutely nothing changed in my setup. The things I've tried:
- setting the Pi with a static IP
- using google DNS
- enable the 'wait for network on boot' option in OE settings
- opening inbound/outbound rules for UDP port 123
- updating ntpdate through autostart.sh
- rebooting my modem and router
Ultimately, I reverted everything back the the way it was. It's extremely frustrating, and I just can't pinpoint the cause. Please help with how should I proceed.
Today I ran into a time synchronization issue on RPi B running OE 3.2.4. On start up, I'm getting the generic "1 Jan 1970" date. The Pi has internet and everything else works just like before. This is not the first time I am getting this issue, but this time it's the longest instance.
Further inspection revealed there are problems between the Pi and the NTP servers. This is the output of running "ntpdate -d 0.asia.pool.ntp.org":
Code:
# ntpdate -d 0.asia.pool.ntp.org
1 Jan 02:06:54 ntpdate[1111]: ntpdate [email protected] Tue Nov 26 09:29:13 UTC 20 13 (1)
Looking for host 0.asia.pool.ntp.org and service ntp
host found : 203.185.69.60
transmit(203.185.69.60)
transmit(212.26.18.43)
transmit(129.250.35.251)
transmit(109.205.114.188)
transmit(203.185.69.60)
transmit(212.26.18.43)
transmit(129.250.35.251)
transmit(109.205.114.188)
transmit(203.185.69.60)
transmit(212.26.18.43)
transmit(129.250.35.251)
transmit(109.205.114.188)
transmit(203.185.69.60)
transmit(212.26.18.43)
transmit(129.250.35.251)
transmit(109.205.114.188)
transmit(203.185.69.60)
transmit(212.26.18.43)
transmit(129.250.35.251)
transmit(109.205.114.188)
203.185.69.60: Server dropped: no data
212.26.18.43: Server dropped: no data
129.250.35.251: Server dropped: no data
109.205.114.188: Server dropped: no data
server 203.185.69.60, port 123
stratum 0, precision 0, leap 00, trust 000
refid [203.185.69.60], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
transmit timestamp: 83aa8025.e221ea35 Thu, Jan 1 1970 2:07:01.883
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
server 212.26.18.43, port 123
stratum 0, precision 0, leap 00, trust 000
refid [212.26.18.43], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
transmit timestamp: 83aa8026.1555c52e Thu, Jan 1 1970 2:07:02.083
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
server 129.250.35.251, port 123
stratum 0, precision 0, leap 00, trust 000
refid [129.250.35.251], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
transmit timestamp: 83aa8026.48893b7d Thu, Jan 1 1970 2:07:02.283
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
server 109.205.114.188, port 123
stratum 0, precision 0, leap 00, trust 000
refid [109.205.114.188], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
transmit timestamp: 83aa8026.7bbc903e Thu, Jan 1 1970 2:07:02.483
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
1 Jan 02:07:04 ntpdate[1111]: no server suitable for synchronization found
As you can see, the servers get dropped, ultimately resulting in the Pi not being able to pull data from them. Like I said, absolutely nothing changed in my setup. The things I've tried:
- setting the Pi with a static IP
- using google DNS
- enable the 'wait for network on boot' option in OE settings
- opening inbound/outbound rules for UDP port 123
- updating ntpdate through autostart.sh
- rebooting my modem and router
Ultimately, I reverted everything back the the way it was. It's extremely frustrating, and I just can't pinpoint the cause. Please help with how should I proceed.