Benches Mac desktops

8

Inaccurate clock - ntpd always adjusting …

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I have a Mac Pro Quad 2.93 (Early 2009). Every 20-30 minutes, I get a log file entry like this:

3/07/09 9:05:28 PM ntpd[16] time reset +0.315745 s

3/07/09 9:27:29 PM ntpd[16] time reset +0.243919 s

It is always approx +0.3s, or around 15s per day!

If I turn off the Mac at night, when I wake it in the morning, the time reset is many seconds. But my Mac is turned off only rarely, so I'm not sure about the accuracy when off.

I can't find any specification for the accuracy of the real time clock, but this seems to be very poor. I have mechanical clocks that keep better time.

My Mac stays very busy (high CPU and constant disk IO) - could it be losing time due to dropped interrupts?

How accurate is the Mac Pro real-time clock supposed to be?

8 replies

Sign in or join Beachball Help to reply.

  1. 0

    Malcolm Rayfield

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are you using an operating system from a different Mac, or installed from a DVD that didn't come with this Mac Pro? The Mac clock should be accurate, but an older version of OSX might not have the correct settings for the latest Mac Pro.

  2. 0

    Torkn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    OS is the factory installed 10.5.6, upgraded to 10.5.7 via Software Update.

    There are various reports of some other models of Macs with inaccurate clocks caused by a failing backup battery. My Mac Pro is (naturally) only several months old, but perhaps I have a bad battery. Anybody know where this battery is located, and if it is user replaceable or how it can be tested?

  3. 0

    Malcolm Rayfield

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    There is a battery on the main logic board, but it will only affect the clock when the computer is off.

  4. 0

    kaz-k

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    My Mac Pro almost always reset the clock when it wakes up from the deep sleeps.

  5. 0

    lispm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    As it comes out of the box + Software Update (a few days old):

    Jul 4 05:24:27 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight

    Jul 4 05:24:41 dor ntpdate[73]: can't find host time.euro.apple.com

    Jul 4 05:24:41 dor org.ntp.ntpd[14]: Error : nodename nor servname provided, or not known

    Jul 4 05:24:41 dor ntpdate[73]: no servers can be used, exiting

    Jul 4 05:28:54 dor ntpd[14]: time reset +0.290514 s

    Jul 4 09:29:17 dor ntpd[14]: sendto(17.72.255.12) (fd=23): No route to host

    Jul 4 14:43:15 dor ntpd[14]: time reset +0.345822 s

    Jul 4 18:59:51 dor ntpd[14]: time reset +0.272855 s

    {change System Pref time server to time.apple.com}

    Jul 4 19:46:55 dor com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight

    Jul 4 19:47:36 dor com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight

    HAd SHAuthorizationRight got something to do with this ntpd polling?

  6. 0

    Torkn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I spotted this post describing a similar problem:

    http://wirespeed.xs4all.nl/mediawiki/index.php/Ntpdtimereset

    On leopard, the ntp.drift file is here:

    /private/var/db/ntp.drift

    Mine was not empty (and last modified in March 2009). So I set it to 0.000, and the rapid ntpd resets have stopped.

    I don't yet know if my clock is now accurate, but at least it is not overloading the ntp server anymore.

  7. 0

    direwolf8

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It doesn't look like you're reaching an ntp server. To verify whether your time is being synchronized, open a terminal window and type:

    ntpq

    ntpq> host localhost

    ntpq> peers

    This should show a list of servers that are synchronizing your clock and some other details. Check to be sure you are actually synchronizing.

  8. 0

    Torkn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    ntpq> peers

    remote refid st t when poll reach delay offset jitter

    ==============================================================================

    *sng-ntp-ext.asi 17.254.0.49 2 u 91 64 336 294.304 13.494 8.944

    Not exactly a list of servers, but that is the one I set in Time/Date preferences. The preferences dialog only lists 3 choices (USA, Asia, Europe).

    Since reseting ntp.drift, I have had no "ntp reset" messages. I'm marking this thread as "solved", and putting it down to a defective ntp.drift file (probably shipped with my machine).