none
Problem mit Zeitsynchronisierung RRS feed

  • Frage

  • Hallo,

    die Zeit auf dem DC ist nicht korrekt. Ich wollte deshalb die Zeitsynchronisierung durchführen. Nach dem Ausführen dieser Befehle:

    w32tm /config /update /syncfromflags:MANUAL /manualpeerlist:"de.pool.ntp.org" /reliable:YES
    net start w32time
    net stop w32time
    w32tm /resync


    wird die korrekte Zeit zwar angezeigt, aber nur für eine Sekunde und dann wird wieder die falsche Zeit angezeigt. Sie wurde quasi nicht "abgespeichert". Port 123 in der Firewall ist freigeschaltet. Woran kann es sonst noch liegen?

    Hier ein Ausschnitt aus der NTP-Log:

    151708 05:17:43.3993750s - ---------- Log File Opened -----------------
    151708 05:17:55.3837500s - RPC Caller is <Benutzer> 
    151708 05:17:55.3837500s - RPC Call Attribute is local=1, kernel=0, session=0, authentication=6, protocol=2, OpNum=0
    151708 05:17:55.3837500s - RPC Call - HardResync
    151708 05:17:55.3837500s - W32TmServiceMain: ********** Time Slip Notification **********
    151708 05:17:55.3837500s - ClockDispln TimeSlip:TimeSlip LastUTC:358893 SetUnsync: LI:0 S:2 RDl:0 RDs:100000000 TSF:0x0 
    151708 05:17:55.3837500s - ClockDispln: we're a reliable time service with no time source: LS: 0, TN: 864000000000, WAIT: 86400000
    151708 05:17:55.3837500s - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
    151708 05:17:55.3837500s - Peer poll: Max:3600.0000000s (special) Cur:3163.7645000s151708 05:17:55.3837500s -  New:01.0803136s
    151708 05:17:55.3837500s - TimeProvCommand([NtpServer], TPC_TimeJumped) called.
    151708 05:17:55.3837500s - W32TmServiceMain: waiting i16.000s (64.000s)
    151708 05:17:55.3837500s - PeerPollingThread: PeerListUpdated
    151708 05:17:55.3837500s - PeerPollingThread: waiting 1.081s
    151708 05:17:55.3837500s - PeerPollingThread: PeerListUpdated
    151708 05:17:55.3837500s - PeerPollingThread: waiting 1.081s
    151708 05:17:56.4775000s - PeerPollingThread: WaitTimeout
    151708 05:17:56.4775000s - Polling peer de.pool.ntp.org,0x1 (ntp.m|0x1|0.0.0.0:123->131.188.3.221:123)
    151708 05:17:56.4775000s - Peer poll: Max:3600.0000000s (special) Cur:00.0000000s
    151708 05:17:56.4775000s - PeerPollingThread: waiting 3600.000s
    151708 05:17:56.5243750s - ListeningThread -- DataAvailEvent set for socket 1 (0.0.0.0:123)
    151708 05:17:56.5243750s - ListeningThread -- response heard from 131.188.3.221:123 <- 172.20.1.3:123
    151708 05:17:56.5243750s - /-- NTP Packet:
    151708 05:17:56.5243750s - | LeapIndicator: 0 - no warning;  VersionNumber: 3;  Mode: 2 - SymmetricPassive;  LiVnMode: 0x1A
    151708 05:17:56.5243750s - | Stratum: 1 - primary reference (syncd by radio clock)
    151708 05:17:56.5243750s - | Poll Interval: 6 - 64s;  Precision: -22 - 238.419ns per tick
    151708 05:17:56.5243750s - | RootDelay: 0x0000.0000s - unspecified;  RootDispersion: 0x0000.004Cs - 0.00115967s
    151708 05:17:56.5243750s - | ReferenceClockIdentifier: 0x44434670 - source name: "DCFp"
    151708 05:17:56.5243750s - | ReferenceTimestamp:   0xDADFE10709E58588 - 13107590023038658500ns - 151708 05:13:43.0386585s
    151708 05:17:56.5243750s - | OriginateTimestamp:   0xDADFE2047A3D70A3 - 13107590276477500000ns - 151708 05:17:56.4775000s
    151708 05:17:56.5243750s - | ReceiveTimestamp:     0xDADFE1115092BB4F - 13107590033314738900ns - 151708 05:13:53.3147389s
    151708 05:17:56.5243750s - | TransmitTimestamp:    0xDADFE11150977A25 - 13107590033314811400ns - 151708 05:13:53.3148114s
    151708 05:17:56.5243750s - >-- Non-packet info:
    151708 05:17:56.5243750s - | DestinationTimestamp: 151708 05:17:56.5243750s - 0xDADFE204863D70A3151708 05:17:56.5243750s -  - 13107590276524375000ns151708 05:17:56.5243750s -  - 151708 05:17:56.5243750s
    151708 05:17:56.5243750s - | RoundtripDelay: 46802500ns (0s)
    151708 05:17:56.5243750s - | LocalClockOffset: -243186162300ns - 4:03.186162300s
    151708 05:17:56.5243750s - \--
    151708 05:17:56.5243750s - ListeningThread STC:358966
    151708 05:17:56.5243750s - Peer poll: Max:3600.0000000s (special) Cur:3599.9531250s
    151708 05:17:56.5243750s - Response from peer de.pool.ntp.org,0x1 (ntp.m|0x1|0.0.0.0:123->131.188.3.221:123), ofs: -243.1861623s
    151708 05:17:56.5243750s - 5 Age:5 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0001764s Dst:16.0001764s FDsp:08.0000000s
    151708 05:17:56.5243750s - 4 Age:4 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0001764s Dst:16.0001764s FDsp:12.0000000s
    151708 05:17:56.5243750s - 3 Age:3 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0001764s Dst:16.0001764s FDsp:14.0000000s
    151708 05:17:56.5243750s - 2 Age:2 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0001764s Dst:16.0001764s FDsp:15.0000000s
    151708 05:17:56.5243750s - 1 Age:1 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0001764s Dst:16.0001764s FDsp:15.5000000s
    151708 05:17:56.5243750s - 0 Age:0 Ofs:-243.1861623s Dly:+00.0468025s RDly:+00.0000000s Dsp:00.0156257s RDsp:00.0011597s Pnt:00.0000000s Dst:00.0390269s FDsp:07.7500000s
    151708 05:17:56.5243750s - W32TmServiceMain: resync req, user requested, get samples as soon as possible.
    151708 05:17:56.5243750s - W32TmServiceMain: waiting i0.000s (62.859s)
    151708 05:17:56.5243750s - W32TmServiceMain: timeout
    151708 05:17:56.5243750s - Sample Prepared at 131075902765243750 for peer de.pool.ntp.org,0x1 (ntp.m|0x1|0.0.0.0:123->131.188.3.221:123)
    151708 05:17:56.5243750s - NtpClient returned 1 samples.
    151708 05:17:56.5243750s - Sample 0 offset:-243.1861623s delay:+00.0468025s dispersion:07.7667854s
    151708 05:17:56.5243750s - Intersection successful with 0 dropped samples.
    151708 05:17:56.5243750s -   0: Sample:0 SyncDist:237901866 SelectDisp:0
    151708 05:17:56.5243750s - Sample 0 chosen. Select Dispersion:00.0000000s STC:358966
    151708 05:17:56.5243750s - ClockDispln Update: LastUTC:358966 SO:-2431861623 KPhO:0 *PhO:-2431861623 uT:73 SD:67261982 LI:0 S:2 RDl:468025 RDs:77767854 TSF:0x0 Unset->Hold
    151708 05:13:53.3382127s - ClockDispln Discipline: *SET*TIME* - PhCR:3474088 KPho:-2431861623
    151708 05:13:53.3382127s - ClockDispln Discipline: *SKEW*TIME* - PhCRR:0 CR:156250 PhCR:3474088 UI:100 phcT:73 KPhO:0
    151708 05:13:53.3382127s - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
    151708 05:13:53.3382127s - TimeProvCommand([NtpServer], TPC_TimeJumped) called.
    151708 05:13:53.3382127s - W32TmServiceMain: waiting 64.000s
    151708 05:13:53.3382127s - W32TmServiceMain: ********** Time Slip Notification **********
    151708 05:13:53.3382127s - ClockDispln TimeSlip:TimeSlip LastUTC:358966 SetUnsync: LI:0 S:2 RDl:0 RDs:100000000 TSF:0x0 ReleaseClock2CMOS
    151708 05:13:53.3380000s - ClockDispln: we're a reliable time service with no time source: LS: 0, TN: 864000000000, WAIT: 86400000
    151708 05:13:53.3380000s - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
    151708 05:13:53.3380000s - TimeProvCommand([NtpServer], TPC_TimeJumped) called.
    151708 05:13:53.3380000s - W32TmServiceMain: waiting i16.000s (64.000s)
    151708 05:13:53.3380000s - PeerPollingThread: PeerListUpdated
    151708 05:13:53.3380000s - PeerPollingThread: waiting 3599.954s
    151708 05:13:53.3380000s - PeerPollingThread: PeerListUpdated
    151708 05:13:53.3380000s - PeerPollingThread: waiting 3599.954s

    Wireshark hat "NTP Version 3, symmetric active" und "NTP Version 3, symmetric passive" gemeldet.

    • Bearbeitet -honeybee- Freitag, 13. Mai 2016 05:23
    Freitag, 13. Mai 2016 05:21

Antworten

  • Sorry, es war ein Tippfehler meinerseits. Ausgeführt wurden die Befehle in dieser Reihenfolge:

    w32tm /config /update /syncfromflags:MANUAL /manualpeerlist:"de.pool.ntp.org" /reliable:YES
    net stop w32time
    net start w32time
    w32tm /resync

    edit:

    Problem gefunden. Die Zeitsynchronisierung auf dem Hyper-V-Host war nicht korrekt.

    • Als Antwort markiert -honeybee- Freitag, 13. Mai 2016 06:13
    • Bearbeitet -honeybee- Freitag, 13. Mai 2016 06:13
    Freitag, 13. Mai 2016 05:43

Alle Antworten

  • Hallo Tux,

    ich es Absicht dass du den Zeitdienst zuerst startest und dann sofort wieder beendest? Nach meinem Verständnis müsste es doch anders herum richtig sein. Dies würde auf jeden Fall die kurze Phase mit der richtigen Zeit erklären.

    Gruß Benjamin 


    Benjamin Hoch
    MCSE: Data Platform
    MCSA: Windows Server 2012
    Blog

    Freitag, 13. Mai 2016 05:34
  • Sorry, es war ein Tippfehler meinerseits. Ausgeführt wurden die Befehle in dieser Reihenfolge:

    w32tm /config /update /syncfromflags:MANUAL /manualpeerlist:"de.pool.ntp.org" /reliable:YES
    net stop w32time
    net start w32time
    w32tm /resync

    edit:

    Problem gefunden. Die Zeitsynchronisierung auf dem Hyper-V-Host war nicht korrekt.

    • Als Antwort markiert -honeybee- Freitag, 13. Mai 2016 06:13
    • Bearbeitet -honeybee- Freitag, 13. Mai 2016 06:13
    Freitag, 13. Mai 2016 05:43
  • > Die Zeitsynchronisierung auf dem Hyper-V-Host war nicht korrekt.
     
    Solltest Du abschalten - zu viele Köche verderben den Brei :-)
     
    Freitag, 13. Mai 2016 10:02