Re: time issue
In the last episode (Aug 27), Michael P. Soulier said: > On 25/08/07 Bill Moran said: > > If this turns out to be your problem, I recommend using > > pool.ntp.org. Read up a bit, it should be much more reliable on a > > consistent basis. Also, OpenNTP has support built in to > > automatically talk to all of ntp.org's servers without any funky > > configuration: http://www.pool.ntp.org/use.html > > The only problem with the ntp pool is that ntp does its best to > factor out problems with specific ntp servers, by learning about > their quirks over time. An ntp pool where the specific servers that > you're talking to change regularly defeats this. ntpd does a single DNS lookup for each server at startup and doesn't shift from them even if the DNS changes, so that's not an issue. > Good enough to keep time on my server though, I suppose, since I'm > not running a cellular network. :) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time issue
On 25/08/07 Bill Moran said: > If this turns out to be your problem, I recommend using pool.ntp.org. > Read up a bit, it should be much more reliable on a consistent basis. > Also, OpenNTP has support built in to automatically talk to all of > ntp.org's servers without any funky configuration: > http://www.pool.ntp.org/use.html The only problem with the ntp pool is that ntp does its best to factor out problems with specific ntp servers, by learning about their quirks over time. An ntp pool where the specific servers that you're talking to change regularly defeats this. Good enough to keep time on my server though, I suppose, since I'm not running a cellular network. :) Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgplEixpqmftK.pgp Description: PGP signature
Re: time issue
In response to "Michael P. Soulier" <[EMAIL PROTECTED]>: > On 24/08/07 Modulok said: > > > Is this a system that is left running 24/7 connected to the Internet, > > or a system which is frequently turned off? If the latter, you might > > It's the former. I'll try the suggested ntp sync option anyway. I'm adding > more sources too, in case the one that I'm syncing too isn't good enough. > > Ah, in fact I think that it is not. Perhaps the NRC isn't permitting public > access to their time servers anymore. If this turns out to be your problem, I recommend using pool.ntp.org. Read up a bit, it should be much more reliable on a consistent basis. Also, OpenNTP has support built in to automatically talk to all of ntp.org's servers without any funky configuration: http://www.pool.ntp.org/use.html -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time issue
On 24/08/07 Modulok said: > Is this a system that is left running 24/7 connected to the Internet, > or a system which is frequently turned off? If the latter, you might It's the former. I'll try the suggested ntp sync option anyway. I'm adding more sources too, in case the one that I'm syncing too isn't good enough. Ah, in fact I think that it is not. Perhaps the NRC isn't permitting public access to their time servers anymore. [EMAIL PROTECTED] ~]$ ntpq -p remote refid st t when poll reach delay offset jitter == time.nrc.ca .INIT. 16 u- 6400.0000.000 4000.00 tick.usask.ca .GPS.1 u9 641 111.674 27760.6 0.002 tock.usask.ca .GPS.1 u8 641 107.417 27759.2 0.002 boudicca.tux.or 65.212.71.1022 u7 641 95.680 27758.6 0.002 LOCAL(0)LOCAL(0)10 l6 6410.0000.000 0.002 Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein signature.asc Description: Digital signature
Re: time issue
In response to "Michael P. Soulier" <[EMAIL PROTECTED]>: > Hello, > > I recently noticed that my clock was running a few minutes slow, even though I > have ntpd running on the box. Now I'm seeing this on occasion. > > Aug 24 20:17:10 kanga dovecot: Time just moved backwards by 105 seconds. This > might c > ause a lot of problems, so I'll just kill myself now. > http://wiki.dovecot.org/TimeMov > edBackwards > > > Does this suggest a hardware clock issue? In addition to the other suggestions, FreeBSD may have chosen a crappy clock. Believe it or not, most motherboards have multiple clocks. Depending on the type of clock and the quality of the mobo, not all of these clocks are good for keeping time. FreeBSD tries to choose the best clock at boot time, but doesn't always get it right. For some interesting discussions on this topic, search the list archives for "calcru" or check out this FAQ entry: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#LAPTOP-CLOCK-SKEW -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time issue
> Hello, > > I recently noticed that my clock was running a few minutes slow, even though > I > have ntpd running on the box. Now I'm seeing this on occasion. > > Aug 24 20:17:10 kanga dovecot: Time just moved backwards by 105 seconds. > This > might c > ause a lot of problems, so I'll just kill myself now. > http://wiki.dovecot.org/TimeMov > edBackwards > > > Does this suggest a hardware clock issue? Is this a system that is left running 24/7 connected to the Internet, or a system which is frequently turned off? If the latter, you might want to do as has been suggested by re-syncing the clock at boot time, and check the CMOS battery on the mainboard. The current recommended method of clock sync at boot time is is via ntpd(8) instead of ntpdate(8), (as of FreeBSD 6.1 and possibly earlier). To quote the ntpdate(8) manual page: "Note: The functionality of this program is now available in the ntpd(8) program. See the -q command line option in the ntpd(8) page. After a suitable period of mourning, the ntpdate utility is to be retired from this distribution." To accomplish this simply add the following like to /etc/rc.conf ntpd_sync_on_start="YES" # Synchronize clock at startup. -Modulok- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time issue
> Hello, > > I recently noticed that my clock was running a few minutes slow, even thoug= > h I > have ntpd running on the box. Now I'm seeing this on occasion.=20 > > Aug 24 20:17:10 kanga dovecot: Time just moved backwards by 105 seconds. Th= > is > might c > ause a lot of problems, so I'll just kill myself now. > http://wiki.dovecot.org/TimeMov > edBackwards > > > Does this suggest a hardware clock issue? > Hi, Do you do an "ntpdate" at boot, or just run "ntpd"? If just ntpd, you should consider ntpdate, that way the "major" adjustment is done before most anything else is started up and your dovecot probably will stop committing hara-kiri. Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
