Ntpdate not updating objectives accomadating instruction for individual

16 u - 64 0 0.000 0.000 0.000 ntpq as ind assid status conf reach auth condition last_event cnt =========================================================== 1 22183 8011 yes no none reject mobilize 1 2 22184 8011 yes no none reject mobilize 1 3 22185 8011 yes no none reject mobilize 1 4 22186 8011 yes no none reject mobilize 1 ntpq 31 Dec ntpd[124]: Deferring DNS for gov 1 31 Dec ntpd[124]: Deferring DNS for 01 31 Dec ntpd[124]: Deferring DNS for 11 31 Dec ntpd[124]: Deferring DNS for 21 31 Dec ntpd[124]: Deferring DNS for ntp.1 31 Dec ntpd[132]: signal_no_reset: signal 17 had flags 4000000 31 Dec ntpd[132]: host name not found: gov 31 Dec ntpd[132]: host name not found: 031 Dec ntpd[132]: host name not found: 131 Dec ntpd[132]: host name not found: 231 Dec ntpd[132]: host name not found: ntp.31 Dec ntpd[124]: Listen normally on 2 eth0 192.168.0.104 UDP 123 31 Dec ntpd[124]: peers refreshed 31 Dec ntpd[124]: new interface(s) found: waking up resolver 31 Dec ntpd[132]: DNS gov - server gov iburst server 0iburst server 1iburst server 2iburst server ntp.iburst restrict default noquery nopeer restrict 127.0.0.1 restrict ::1 driftfile /var/lib/ntp/ntp.drift logfile /var/log/[Unit] Description=Network Time Service After=network.target nss-lookup.target [Service] Type=forking Private Tmp=true PIDFile=/var/run/Exec Start=/usr/bin/ntpd -g -u ntp:ntp -p /var/run/Restart=always [Install] Wanted By=multi-user.target [[email protected] ~]# ntpd -qd ntpd [email protected] Sat Jan 11 UTC 2014 (1) 31 Dec ntpd[296]: proto: precision = 1.000 usec event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled Finished Parsing!!

ntpdate not updating-73

PORT STATE SERVICE 123/udp open|filtered ntp Nmap done: 1 IP address (1 host up) scanned in 2.09 seconds $ sudo nmap -p 123 -s U localhost Starting Nmap 6.40 ( at 2016-09-19 CEST Nmap scan report for localhost (127.0.0.1) Host is up (0.00018s latency).

PORT STATE SERVICE 123/udp open ntp Nmap done: 1 IP address (1 host up) scanned in 1.12 seconds $ sudo nmap -p 123 -s U Starting Nmap 6.40 ( at 2016-09-19 CEST Nmap scan report for (127.0.1.1) Host is up.

Seems a little weird to do that without a specific reason. The b option forces the time to be stepped using the settimeofday() system call.

I am running Ubuntu on an ARM based embedded system that lacks a battery backed RTC. Thus, I use the NTP service to update the time to the current time.

PORT STATE SERVICE 123/udp open|filtered ntp Nmap done: 1 IP address (1 host up) scanned in 0.78 seconds $ sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination $ sudo tcpdump udp port 123 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes .733037 IP ntp .

Other addresses for localhost (not scanned): 127.0.0.1 r DNS record for 127.0.0.1: localhost.localdomain PORT STATE SERVICE 123/udp open ntp Nmap done: 1 IP address (1 host up) scanned in 1.08 seconds $ sudo nmap -p 123 -s U zzz.142 Starting Nmap 6.40 ( at 2016-09-19 CEST Nmap scan report for (zzz.142) Host is up (0.046s latency).[[email protected] ~]# ntpdate -dq gov 31 Dec ntpdate[299]: ntpdate [email protected] Sat Jan 11 UTC 2014 (1) Looking for host gov and service ntp host found : nist1-chi.transmit(216.171.120.36) receive(216.171.120.36) transmit(216.171.120.36) receive(216.171.120.36) transmit(216.171.120.36) receive(216.171.120.36) transmit(216.171.120.36) receive(216.171.120.36) server 216.171.120.36, port 123 stratum 1, precision -29, leap 00, trust 000 refid [ACTS], delay 0.07671, dispersion 0.00000 transmitted 4, in filter 4 reference time: d69d8005.439fdedc Wed, Feb 5 2014 .264 originate timestamp: d69d800c.753a297e Wed, Feb 5 2014 .457 transmit timestamp: 83aa80af.2239d5e4 Wed, Dec 31 1969 .133 filter delay: 0.07681 0.07671 0.07689 0.07681 0.00000 0.00000 0.00000 0.00000 filter offset: 13916567 13916567 13916567 13916567 0.000000 0.000000 0.000000 0.000000 delay 0.07671, dispersion 0.00000 offset 1391656797.298671 31 Dec ntpdate[299]: step time server 216.171.120.36 offset 1391656797.298671 sec peers remote refid st t when poll reach delay offset jitter ============================================================================== nist1certic . What's available on raspi to debug DNS problems? I just stopped and restarted ntpd on my arch linux server, and I didn't see those lines.fake-hwclock is a simple set of scripts to save the kernel's current clock periodically (including at shutdown) and restore it at boot so that the system clock keeps at least close to realtime.$ ntpdate -qv 194.177.4.2 16 Sep ntpdate[21836]: ntpdate [email protected] Thu Feb 11 UTC 2016 (1) server 194.177.4.2, stratum 2, offset 17.656685, delay 0.06981 16 Sep ntpdate[21836]: step time server 194.177.4.2 offset 17.656685 sec $ ntpdate -qd 2.42 16 Sep ntpdate[21841]: ntpdate [email protected] Thu Feb 11 UTC 2016 (1) Looking for host 2.42 and service ntp host found : 2.42 transmit(2.42) receive(2.42) transmit(2.42) receive(2.42) transmit(2.42) receive(2.42) transmit(2.42) receive(2.42) server 2.42, port 123 stratum 2, precision -20, leap 00, trust 000 refid [2.42], delay 0.03363, dispersion 0.00159 transmitted 4, in filter 4 reference time: db86ca25.1cf0982a Fri, Sep 16 2016 .113 originate timestamp: db86cb28.8dda4c1d Fri, Sep 16 2016 .554 transmit timestamp: db86cb16.da7f48f5 Fri, Sep 16 2016 .853 filter delay: 0.03363 0.03381 0.03365 0.03368 0.00000 0.00000 0.00000 0.00000 filter offset: 17.69400 17.69494 17.69572 17.69653 0.000000 0.000000 0.000000 0.000000 delay 0.03363, dispersion 0.00159 offset 17.694009 16 Sep ntpdate[21841]: step time server 2.42 offset 17.694009 sec $ sudo ntpd -d4L ntpd [email protected] Thu Feb 11 UTC 2016 (1) 16 Sep ntpd[21468]: proto: precision = 2.793 usec event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled Finished Parsing!! Finally, my ISP confirmed that precedent ISP blocks source port 123 on my IP address. I read the man page for ntpdate's -u option it states that -d always uses this option, so thats why I saw transmit/receive/transmit/receive on my ntpdate -dq command -- well, big NOPE!

Tags: , ,