Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
Hi! With the above mentioned Setting ntpq works! C:\Program Files (x86)\NTP\binntpq -p remote refid st t when poll reach delay offset jitter == *toa1.bkh.at .GPS.1 u 38 64 170.514 -0.909 0.977 toa2.bkh.at .GPS.1 u 41 64 170.015 -0.768 0.977 ip146255057034. 91.189.94.4 3 u 40 64 17 14.074 -3.193 22.992 boxi.trexler.at 193.171.23.163 2 u 39 64 17 14.490 43.767 1.913 manage.mediainv 193.171.23.163 2 u 38 64 17 13.4280.971 5.573 ntp1.sil.at 86.59.80.170 3 u 38 64 17 14.1872.870 58.004 C:\Program Files (x86)\NTP\bin Let's wait Hartmut ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
Hi! Not working again. Actual polling rate: 256. The internal system clock (windows time UTC) was only one time altered between 16:00 and 21:00: Die Systemzeit wurde von 2014-06-04T14:12:55.993298900Z in 2014-06-04T14:12:55.82900Z geändert. Änderungsgrund: Die Uhrzeit wurde von einer Anwendung oder von einer Systemkomponente geändert.. Hartmut ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
hschu...@gmail.com wrote: Not working again. Offhand you likely have a perception problem. What makes you think its not working? ntpq -clpe -clas -crv In ntpq, Does the peers have e.g. a server with a * in front of it, are there maybe others with + in front of them, is the reach for those servers e.g. 377; reasonable delays, offsets, jitters? Does an association have e.g. reach yes for a condition sys.peer and last event sys_peer, and likely other candidates reachable? Does your client's variables have e.g. sync_ntp, leap 00, a stratum lower than 16, Actual polling rate: 256. The polls should get longer, and shorter based on what ntp needs; they get longer as the systems frequency is stabilized, or shorter if ntp thinks it needs shorter polls, based on the data it has (I think mostly dispersion of a server), and the adjustments its recently / currently making. The internal system clock (windows time UTC) was only one time altered between 16:00 and 21:00: Die Systemzeit wurde von 2014-06-04T14:12:55.993298900Z in 2014-06-04T14:12:55.82900Z geändert. Änderungsgrund: Die Uhrzeit wurde von einer Anwendung oder von einer Systemkomponente geändert.. https://translate.google.com/#de/en/ The system time was 2014-06-04T14: 12:55.993298900 Z 2014-06-04T14: 12:55.82900 Z changed. Reason for change: The time has been changed by an application or a system component .. Whats that from? NTP only sets the date / time once, rarely steps the time, and normally makes small changes to the frequency. http://www.eecis.udel.edu/~mills/ntp.html http://www.eecis.udel.edu/~mills/database/brief/arch/arch.pdf e.g. pg 23 Clock discipline algorithm http://www.eecis.udel.edu/~mills/database/brief/flow/ntp4.pdf http://www.eecis.udel.edu/~mills/database/brief/clock/clock.pdf http://www.eecis.udel.edu/~mills/database/brief/precise/precise.pdf http://www.eecis.udel.edu/~mills/database/brief/algor/algor.pdf http://www.eecis.udel.edu/~mills/ntp/html/warp.html http://www.ntp.org/ntpfaq/NTP-s-algo.htm -- E-Mail Sent to this address blackl...@anitech-systems.com will be added to the BlackLists. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
hschu...@gmail.com wrote in message news:c7ea1a65-eb51-4708-98cb-5aa0d4b31...@googlegroups.com... Not working again. Actual polling rate: 256. The internal system clock (windows time UTC) was only one time altered between 16:00 and 21:00: You keep repeating that. If any of your associations has a '*' in front of it, NTP is working and the offset to that server should be low. That should tell you that your clock is running very close to 'real' time. NTP does _not_ work by setting your clock to a different time, over and over. It works by making your clock run faster or slower, as required. If this works, you see a lot of nothing happening. Groetjes, Maarten Wiltink ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
hschu...@gmail.com wrote: Hi! Not working again. Actual polling rate: 256. The internal system clock (windows time UTC) was only one time altered between 16:00 and 21:00: As has been already mentioned ntpd needs write access to some of its files. Can you confirm that it has, particularly ntpd.drift (whatever is default or has been cofigured). David Die Systemzeit wurde von 2014-06-04T14:12:55.993298900Z in 2014-06-04T14:12:55.82900Z geändert. Änderungsgrund: Die Uhrzeit wurde von einer Anwendung oder von einer Systemkomponente geändert.. Hartmut ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
Hi! ntp.drift is configured and the actual value is 8.898. Hartmut ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Some issues about NTP ( Server 2008R2)
hschu...@gmail.com wrote: Hi! ntp.drift is configured and the actual value is 8.898. Hartmut How do you know that ntpd isn't running? If 'ntpq -p' is still working then so is ntpd. If you are wanting ntpd to behave same as windows time then you'd better forget about running ntpd and then you'll be happy (but your time probably won't be as good as from ntpd). David Not from a windows system: $ ntpq -crv -p associd=0 status=011d leap_none, sync_pps, 1 event, kern, version=ntpd 4.2.7p444@1.2483-o Thu May 22 09:51:04 UTC 2014 (1), processor=i386, system=NetBSD/6.1_STABLE, leap=00, stratum=1, precision=-18, rootdelay=0.000, rootdisp=400.150, refid=PPSb, reftime=d73a384b.914e86bc Thu, Jun 5 2014 0:28:59.567, clock=d73a3856.6f6569fc Thu, Jun 5 2014 0:29:10.435, peer=31562, tc=4, mintc=3, offset=-0.000312, frequency=-35.047, sys_jitter=0.003815, clk_jitter=0.001, clk_wander=0.002 remoterefidst t when poll reach delay offset jitter *GPS_NMEA(2) .GPSb.7 l 44 64 3770.000 -1.416 12.035 oPPS(2) .PPSb.0 l 11 16 3770.0000.000 0.004 me6000g.home xxx.xxx 2 u 19 64 3770.4700.185 0.560 +ns0.lordynet xxx.xxx 3 u 53 64 3772.0600.737 0.594 +ns1.lordynet xxx.xxx 3 u 45 64 3770.5480.151 0.586 +ns3.lordynet xxx.xxx 3 u 34 64 3770.5120.233 0.565 +ntp2.xxx xxx.xxx 2 u 232 256 377 22.3172.002 0.473 ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
