NTP issues with 5.4 (SOLVED) (fwd)

Darrel dlevitch at iglou.com
Thu May 19 16:01:15 PDT 2005


I wrote:
> Hello,
>
> I run ntpd in daemon mode on several FreeBSD computers and synchronize
> with 'ntpd -q' all others.
>
> I've just updated one machine to 5.4 (from 5.3) and noticed the daemon
> was unhappy, often logging 'time reset' and resynchronizing with peers.
> On other machines I also only recently (after the upgrade to 5.4) see
> ntp problems - 'ntpd -q' gets stuck and time goes off. The machines were
> all fine before.
>
> I searched the web and archives and found some more people complaining
> about similar issues but I haven't found any good answer. At first I
> thought it was happening only on SMP computers but it isn't the case.
> The machines have all kinds of timecounters - ACPI-fast, ACPI-safe and
> i8254.

I'd like to let you all know that I don't think the problem is as
widespread as I originally thought.

After tens of restarts of ntpd processes I've never experienced any
problem synchronizing. No more hung 'ntpd -q' processes either. I
suspect the latter was a consequence of my server having problems
synchronizing.

Michal
---------
I installed openntpd considering that it should run with reduced 
privileges.  The Workgroup did not sync up right away and I reinstalled 
NTP4.

Currently, I can sync Window XP and Windows 98.  My /var/log/messages:

May 19 12:25:37 ntpd[379]: kernel time sync enabled 6001
May 19 12:42:40 ntpd[379]: kernel time sync enabled 2001
May 19 14:59:14 ntpd[379]: kernel time sync enabled 6001
May 19 15:16:19 ntpd[379]: kernel time sync enabled 2001
May 19 18:24:09 ntpd[379]: kernel time sync enabled 6001
May 19 18:41:14 ntpd[379]: kernel time sync enabled 2001

I am not sure, but this could be  normal phase-lock-loop of the 
kernel.

Darrel



More information about the freebsd-questions mailing list