From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ntp problem
Date: Tue, 23 Aug 2005 08:26:14 -0500 [thread overview]
Message-ID: <430B23F6.9070706@badapple.net> (raw)
In-Reply-To: <b9e0c3fe0508230536222e3b53@mail.gmail.com>
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?
That offset looks rather large. NTP really wants to make constant small
changes, not a single huge change. This is why the ntpd setup allows for
an immediate sync via ntpdate before starting the daemon. To fix this
I'd shut down ntpd, run ntpdate 192.168.7.1, and then start ntpd again.
kashani
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-23 13:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 12:36 [gentoo-user] ntp problem Bruno Lustosa
2005-08-23 13:14 ` krzaq
2005-08-23 13:21 ` Bruno Lustosa
2005-08-23 13:25 ` Uwe Thiem
2005-08-23 14:30 ` Bruno Lustosa
2005-08-23 15:46 ` Michael Kintzios
2005-08-23 17:50 ` Bruno Lustosa
2005-08-23 13:26 ` kashani [this message]
2005-08-23 13:29 ` Bruno Lustosa
2005-08-23 14:19 ` krzaq
2005-08-23 14:26 ` Bruno Lustosa
2005-08-23 14:28 ` Bruno Lustosa
2005-08-24 1:25 ` W.Kenworthy
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 7:32 [gentoo-user] NTP problem Anthony E. Caudel
2006-02-22 8:10 ` Brandon Enright
2006-02-22 8:41 ` Anthony E. Caudel
2006-02-22 16:29 ` Brandon Enright
2006-02-22 18:38 ` Anthony E. Caudel
2006-02-22 19:05 ` Boyd Stephen Smith Jr.
2006-02-22 19:13 ` Brandon Enright
2006-02-22 20:03 ` Boyd Stephen Smith Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430B23F6.9070706@badapple.net \
--to=kashani-list@badapple.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox