| 1 |
Bruno Lustosa wrote: |
| 2 |
> Hello. I'm running ntpd as server on one of my machines, and it keeps |
| 3 |
> itself in sync with 6 time servers around the globe. The |
| 4 |
> synchronization works very well. |
| 5 |
> The problem is when I try to get the other machines on the network to |
| 6 |
> sync themselves with this one server. Most of them are running linux |
| 7 |
> (kernel 2.6.x), but some are still running windows. |
| 8 |
> Some machines can sync fine, and some don't. All of them can reach the |
| 9 |
> server (same network), and there is no firewall at all. |
| 10 |
> This is the output I get from ntpq on the machines that don't work: |
| 11 |
> |
| 12 |
> ntpq> peers |
| 13 |
> remote refid st t when poll reach delay offset jitter |
| 14 |
> ============================================================================== |
| 15 |
> timeserver 217.160.252.229 3 u 26 64 377 0.214 46927.6 716.379 |
| 16 |
> ntpq> assoc |
| 17 |
> |
| 18 |
> ind assID status conf reach auth condition last_event cnt |
| 19 |
> =========================================================== |
| 20 |
> 1 15036 9064 yes yes none reject reachable 6 |
| 21 |
> |
| 22 |
> The only differences between this one and another machines where it's |
| 23 |
> working fine are the status code (it varies a bit) and the condition |
| 24 |
> (instead of reject, sys.peer). |
| 25 |
> The ntp.conf for all machines have just: |
| 26 |
> |
| 27 |
> server 192.168.7.1 |
| 28 |
> |
| 29 |
> which is the ip address of the time server in question. |
| 30 |
> I don't know the internals of ntp. What can be wrong in my configuration? |
| 31 |
|
| 32 |
That offset looks rather large. NTP really wants to make constant small |
| 33 |
changes, not a single huge change. This is why the ntpd setup allows for |
| 34 |
an immediate sync via ntpdate before starting the daemon. To fix this |
| 35 |
I'd shut down ntpd, run ntpdate 192.168.7.1, and then start ntpd again. |
| 36 |
|
| 37 |
kashani |
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives