Configuring the Time Service: Enabling the Debug Log

re: Configuring the Time Service: Enabling the Debug Log

Peter DuDeck — Fri, 25 Feb 2011 01:24:35 GMT

Example:

149803 23:58:59.2887417s - Time zone OK.

Equals

2/24/2011 23:58:59 UTC

To convert:

DateAdd ("D",149803,"1/1/1601")

The American National Standards Institute (ANSI) adopted a system of counting days; this system began with December 31, 1600 as Day 0. In turn, that made January 1, 1601 the first “official” day in history, with all subsequent dates and times being based on the number of nanoseconds elapsed since the 0 hour on January 1, 1601. (That day was a Monday, by the way.) These so-called ANSI decimal dates were originally designed for use with the COBOL programming language and have continued to be used by Windows and other operating systems.

re: Configuring the Time Service: Enabling the Debug Log

dladen — Fri, 11 Jul 2008 07:55:08 GMT

Looking at the debug logs, I see lines like the following:

148830 21:03:50.5225236s - ---------- Log File Opened -----------------

The second field looks like the time. I assume the first is a date, how do I convert it to month/day/year format.

Thank You,

Dan

re: Configuring the Time Service: Enabling the Debug Log

brorymes — Thu, 05 Jun 2008 22:50:55 GMT

Thanks Ryan!

With FileLogEntries = 62, only "ClockDiscpln Update" lines are logged - for example:

ClockDispln Update: SO:10326 KPhO:-392 PhO:10718 uT:3842 FllPPE:10718 PllPPE:10718 FllPPrE:192010 PllPPrE:190311 sysPollTicks:16383 FllDown:65533 PllUp:3842 PllDown:131064 FllRA:0 PllRA:0 RA:0 CR:156256 nT:1033 RAPhO:0 SD:299147 LI:0 S:2 RDl:312500 RDs:371744 TSF:0x0 Sync

Is this as expected?

Which of these many fields provides the clock offset - and what are the units?

Also: These lines appeared before in the "full" log, but were prefixed (as was every log entry) with date and timestamp:

148809 19:16:49.3914379s - ClockDispln:ClockDispln Update: SO:-219272 KPhO:358 PhO:-219630 uT:3842 FllPPE:-219630 PllPPE:-215788 FllPPrE:242964 PllPPrE:241624 sysPollTicks:16383 FllDown:65533 PllUp:3842 PllDown:131064 FllRA:0 PllRA:0 RA:0 CR:156256 nT:8 RAPhO:0 SD:320512 (i) LI:0 S:2 RDl:312500 RDs:594206 TSF:0x0 Sync

How do I get the date and time back? Are they controlled by a separate message number, and if so, what is it?

I would also like to include the individual peer response / offset lines, as in:

148809 19:17:49.2937259s - Response from peer NTPMMK-E0.fmr.com (ntp.m|0x9|10.86.33.181:123->10.32.108.10:123), ofs: -00.0050404s

Which message number would those be?

Thanks!

re: Configuring the Time Service: Enabling the Debug Log

Ryan Sizemore — Tue, 03 Jun 2008 19:53:27 GMT

The debug log is designed to be an internal debugging tool, but we ship it in the product anyway. As you pointed out, some of the message numbers are documented but not an exhaustive list because it isn't built as a customer tool. If you need specific entries, you can either ask here or use "trial and error".

Most of the calculations made by the service (that you are interested in) fall into a "discipline calculations" bucket, which is entry 62. Beyond that, you will need to parse the log to find a specific value.

re: Configuring the Time Service: Enabling the Debug Log

brorymes — Tue, 03 Jun 2008 18:32:25 GMT

Having set the registry entries as described, W32Time is indeed logging a lot of useful information - i.e. a complete blow-by-blow of peer polling, sample filtering, and clock disciplining.

Now - since I'm interested not in debugging W32Time, but rather in simply logging the clock offset as calculated by NTP - I would like to adjust FileLogEntries accordingly. How do I find out which message numbers correspond to which log messages? The Technet entry for FileLogEntries lists some, but not all - and not this one. (Also - including the numbers in the messages themselves would greatly simplify such adjustments, and log filtering after the fact.)

BioSensorAB » Configuring the Time Service: Enabling the Debug Log

BioSensorAB » Configuring the Time Service: Enabling the Debug Log — Fri, 29 Feb 2008 02:34:35 GMT

PingBack from http://www.biosensorab.org/2008/02/28/configuring-the-time-service-enabling-the-debug-log/