From owner-freebsd-stable@FreeBSD.ORG Fri Jul 20 07:37:16 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0925F16A417 for ; Fri, 20 Jul 2007 07:37:16 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id B7DAD13C459 for ; Fri, 20 Jul 2007 07:37:15 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id 7E8BE1B10F00; Fri, 20 Jul 2007 09:37:14 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 7B84F1B10EFB; Fri, 20 Jul 2007 09:37:14 +0200 (CEST) Message-ID: <46A0662A.7060401@sun-fish.com> Date: Fri, 20 Jul 2007 10:37:14 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: "[LoN]Kamikaze" References: <469F9A85.4090209@gmx.de> <469FA50E.9080705@gmx.de> In-Reply-To: <469FA50E.9080705@gmx.de> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: FreeBSD Stable Subject: Re: ntpd just sits there and does nothing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2007 07:37:16 -0000 Hi, [LoN]Kamikaze wrote: > Doug Hardie wrote: > >> On Jul 19, 2007, at 10:08, [LoN]Kamikaze wrote: >> >> >>> As the subject says, on my 6-stable systems ntpd just sits there and does >>> nothing. The logs only mention when the daemon gets started or shut >>> down. It >>> complains when servers are not reachable, but does nothing when they >>> are available. >>> >>> The drift file always contains 0.00. >>> >>> ntpdate and openntpd both successfully manage to set the time, so I >>> suppose >>> it's a problem with ntpd. >>> >> Are you on a static IP address? If not, ntpd obtains its IP address >> when it starts up and uses it forever. If your IP address changes then >> it will not be able to communicate with the upstream ntp servers. It >> has to be restarted everytime your IP address changes. >> > > I have a static address. The trouble is it seems to operate fine, only it > forgets to change the time when it differs from the time servers too much. > Sometimes my clock goes wrong more than 1 second within a day. > ntpd will not change time if the difference is too big - I think it should be less then 1000s. ntpdate will :) Also if you have increased your kernel secure level 2+ : In addition, kernel time changes are restricted to less than or equal to one second. Attempts to change the time by more than this will log the message ``Time adjustment clamped to +1 second''. So grep for ntpd in /var/log/messages and I'm sure you will find the problem. Other problem that I see is if you are behind NAT/firewall. Because ntpd make a request and wait for response on different port, so check your firewall configuration and blocked packets. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Best Wishes, Stefan Lambrev ICQ# 24134177