From owner-freebsd-stable@FreeBSD.ORG Thu Feb 11 18:26:08 2010 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 8A176106566C for ; Thu, 11 Feb 2010 18:26:08 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout025.mac.com (asmtpout025.mac.com [17.148.16.100]) by mx1.freebsd.org (Postfix) with ESMTP id 7380F8FC14 for ; Thu, 11 Feb 2010 18:26:08 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp025.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KXO00BCHWJBUQ00@asmtp025.mac.com> for freebsd-stable@freebsd.org; Thu, 11 Feb 2010 10:26:00 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-1002110148 From: Chuck Swiger In-reply-to: <20100211190652.6a66c618.torfinn.ingolfsen@broadpark.no> Date: Thu, 11 Feb 2010 10:25:59 -0800 Message-id: References: <20100211190652.6a66c618.torfinn.ingolfsen@broadpark.no> To: Torfinn Ingolfsen X-Mailer: Apple Mail (2.1077) Cc: freebsd-stable@freebsd.org Subject: Re: ntpd struggling to keep up - how to fix? 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: Thu, 11 Feb 2010 18:26:08 -0000 Hi-- On Feb 11, 2010, at 10:06 AM, Torfinn Ingolfsen wrote: [ ... ] > Feb 7 16:11:45 kg-f2 ntpd[910]: time reset +2.373325 s > > and this goes on an on, forever. At any give time, no matter how long the machine has been up, ntpq ca report this: > root@kg-f2# ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > kg-omni1.kg4.no 129.240.64.3 3 u 13 64 37 0.162 703.094 444.681 The rate at which this machine is losing time is probably exceeding the ~50 seconds per day that NTPd is willing to correct without extreme measures (ie, it has to step time rather than drift-correct). You might help it maintain a more sane idea of time by using at least 4 timeservers. You might take a look at 'vmstat -i' and look out for an interrupt storm, but it's possible your hardware's clock is simply busted. Regards, -- -Chuck