From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1E7Yfu-0005OF-S4 for garchives@archives.gentoo.org; Tue, 23 Aug 2005 13:18:47 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7NDGvmw013635; Tue, 23 Aug 2005 13:16:57 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7NDDHP6016542 for ; Tue, 23 Aug 2005 13:13:18 GMT Received: by zproxy.gmail.com with SMTP id x7so883740nzc for ; Tue, 23 Aug 2005 06:14:09 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BMYC7DjMpdlJEsUR5J7N8j9iCKUB1eRvgojP6DSsb53Qz7r8gVF4NtQ7g+5X/QI3je5ROkR8M+CHF2++501sKNYoP7QHUBdLk2yF0+GJ/4b4fffVCpoE0uXIEejG25niAzk+J3rGsRwJIpUfLC2oxkmMhds5dhmD+pV48sdMwDo= Received: by 10.37.15.63 with SMTP id s63mr1631583nzi; Tue, 23 Aug 2005 06:14:09 -0700 (PDT) Received: by 10.36.67.4 with HTTP; Tue, 23 Aug 2005 06:14:09 -0700 (PDT) Message-ID: <2ab8d39a050823061477493acb@mail.gmail.com> Date: Tue, 23 Aug 2005 15:14:09 +0200 From: krzaq To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ntp problem In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j7NDDHP6016542 X-Archives-Salt: 81220068-3d8f-4a9d-984b-f8af6e627b0f X-Archives-Hash: c864018c0b975c7b9ca1a5166ac6dfff On 8/23/05, Bruno Lustosa wrote: > Hello. I'm running ntpd as server on one of my machines, and it keeps > itself in sync with 6 time servers around the globe. The > synchronization works very well. > The problem is when I try to get the other machines on the network to > sync themselves with this one server. Most of them are running linux > (kernel 2.6.x), but some are still running windows. > Some machines can sync fine, and some don't. All of them can reach the > server (same network), and there is no firewall at all. > This is the output I get from ntpq on the machines that don't work: > > ntpq> peers > remote refid st t when poll reach delay offset jitter > ============================================================================== > timeserver 217.160.252.229 3 u 26 64 377 0.214 46927.6 716.379 > ntpq> assoc > > ind assID status conf reach auth condition last_event cnt > =========================================================== > 1 15036 9064 yes yes none reject reachable 6 > > The only differences between this one and another machines where it's > working fine are the status code (it varies a bit) and the condition > (instead of reject, sys.peer). > The ntp.conf for all machines have just: > > server 192.168.7.1 > > which is the ip address of the time server in question. > I don't know the internals of ntp. What can be wrong in my configuration? I am no NTP expert, but there may be nothing wrong with your configuartion. NTP is a complex protocol. The machine has decided not to sync with the requested server. It thinks that the provided server is inacurate (the machine's internal clock is more acurate). Leave it running a couple of days and then see what happens. The whole idea is to calculate the drift of the machines internal clock. NTP will not trust specified timeservers blindly. Frankly I think that ntp works best with several timeservers. If you want your local machines to blindly set the date to your local timeserver try nptdate instead. -- Regards Karol Krzak -- gentoo-user@gentoo.org mailing list