[ntp:questions] no drift-file on 2008 R2 vps and the time diff. is getting bigger and bigger?

Brian Inglis Brian.Inglis at SystematicSw.ab.ca
Mon Sep 15 04:45:24 UTC 2014


On 2014-09-13 23:27, gooly wrote:

>>> And this would not explain why ntp.drift is not created?
>>
>> As others have pointed out, if NTP is not succeeding, it need not
>> generate a drift file.

> No I compared the output of ntpq -crv of the vps against the one of my win-7 pc (pretty much at the same moment):
> the vps:
>> C:\Windows\System32>ntpq -crv
>> associd=0 status=c018 leap_alarm, sync_unspec, 1 event, no_sys_peer,
>> version="ntpd 4.2.6p5 at 1.2349-o Jul 30 11:55:08 (UTC+02:00) 2012  (2)",
>> processor="x86", system="Windows", leap=11, stratum=4, precision=-21,
>> rootdelay=30.116, rootdisp=2739.938, refid=5.9.67.110,
>> reftime=d7bf26ea.de20f8a0  Sat, Sep 13 2014 22:26:18.867,
>> clock=d7bf9fc1.ed49adcd  Sun, Sep 14 2014  7:01:53.926, peer=0, tc=6,
>> mintc=3, offset=0.000, frequency=500.000, sys_jitter=0.000,
>> clk_jitter=0.000, clk_wander=0.143
>
> the win-7 pc:
>> C:\Windows\system32>ntpq -crv
>> associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,
>> version="ntpd 4.2.6p5 at 1.2349-o Jul 30 11:55:08 (UTC+02:00) 2012  (2)",
>> processor="x86", system="Windows", leap=00, stratum=2, precision=-10,
>> rootdelay=9.705, rootdisp=123.040, refid=193.171.23.163,
>> reftime=d7bfa048.5247afc8  Sun, Sep 14 2014  7:04:08.321,
>> clock=d7bfa0c4.3e172bd3  Sun, Sep 14 2014  7:06:12.242, peer=20373,
>> tc=10, mintc=3, offset=98.888, frequency=-81.326, sys_jitter=35.732,
>> clk_jitter=22.769, clk_wander=0.025
>
>
> hmm ?
> 1) (is ntp started with the wrong setup on the vps?)
> vps-failed: status=c018 leap_alarm, sync_unspec
> pc-working: status=0618 leap_none, sync_ntp
>
> 2) (vps' ref-time is ~ the last restart of ntp, pc-ref ~= pc-clock)
> vps-failed: reftime=d7bf26ea.de20f8a0  Sat, Sep 13 2014 22:26:18.867
> pc-working: reftime=d7bfa048.5247afc8  Sun, Sep 14 2014  7:04:08.321
>
> 3) (does s.o. knows what that might mean?)
> vps-failed:
>      peer=0, tc=6, mintc=3, offset=0.000, frequency=500.000,
>      sys_jitter=0.000, clk_jitter=0.000, clk_wander=0.143
> pc-working:
>      peer=20373, tc=10, mintc=3, offset=98.888, frequency=-81.326,
>      sys_jitter=35.732, clk_jitter=22.769, clk_wander=0.025
>
> Remark on 1) both ntp are using the default set up of the installation, I only changed the server-list.

NTPd is doing nothing on your VPS system.
NTPd should quit when offset exceeds 1000s.
Check your Windows event log to see if NTPd is quitting and being restarted by the service controller.
Are you starting the service with -g (panicgate) -M (multimedia timer) and seeing a time step in the event log?
-- 
Take care. Thanks, Brian Inglis


More information about the questions mailing list