Kurt Roeckx schrieb: > On Tue, Oct 17, 2006 at 02:26:10PM +0200, Christoph Martin wrote: >> Hi Kurt, >> >> Oct 16 17:50:35 gonzo ntpd[27046]: frequency initialized 0.000 PPM from >> /var/lib/ntp/ntp.drift >> Oct 16 17:50:45 gonzo ntpd[27046]: synchronized to 134.93.227.254, stratum 2 >> Oct 16 17:48:59 gonzo ntpd[27046]: time reset -105.185036 s > > That would be caused by the -g option, just picking one of the clocks at > startup, so that your more or less correct.
And this is also not working every time. Sometime it does not log a
synchronisation.
>> Well, I am not shure about that because the other host which works has
>> the following stats:
>>
>> 134.93.226.2 134.93.225.254 5 u 27 64 377 0.262 -3116.1
>> 1075.62
>> 134.93.226.19 134.93.227.254 3 u 54 64 377 0.330 -1174.2
>> 1370.48
>> *134.93.227.254 131.188.3.220 2 u 48 64 377 0.313 -1791.6
>> 917.537
>
> So, it's synched to 134.93.227.254, but it's 1.8 seconds off? And there
> is a difference of 1.3 seconds between the clocks?
>
> What is also weird is that your interval still is at 64 second? Did it
> have a time reset recently or something? Or was it recently restarted?
> If it's been running for a while without problems it really should be at
> an interval of 1024 seconds.
I now have it running for over 12 hours with only one server to sync
with and I still have the same problem. I initially set the time with
ntpdate because I could not get ntpd to sync it:
134.93.226.19 134.93.227.254 3 u 6 64 377 0.416 -469257
1570.32
The next server (134.93.226.19) is running sarge version of ntpd and
successfully syncs:
134.93.226.2 131.188.3.220 2 u 199 1024 3 0.983 2.203
0.310
*134.93.227.254 192.53.103.108 2 u 443 1024 377 0.446 -0.277
0.340
>
> If you ask me, atleast 134.93.226.2 and 134.93.226.19 aren't working
> properly either.
The two proxies 134.93.226.2 and 134.93.227.254 have exactly the same
setup (sarge) connecting to upstream servers and having eachother as peers:
134.93.226.2 was recently restarted:
-134.93.227.254 192.53.103.108 2 u 24 128 376 0.337 -2.296
1.671
+134.93.144.1 217.198.242.4 3 u 25 128 377 0.885 0.900
0.131
*131.188.3.220 .GPS. 1 u 19 128 377 5.098 -1.001
0.592
+192.53.103.108 .PTB. 1 u 21 128 377 20.641 1.520
4.802
134.93.227.254 is running for longer:
-134.93.226.2 131.188.3.220 2 u 79 128 377 0.402 2.281
1.644
+134.93.144.1 217.198.242.4 3 u 958 1024 377 0.830 3.377
0.013
+131.188.3.220 .GPS. 1 u 966 1024 377 7.154 2.193
0.243
*192.53.103.108 .PTB. 1 u 175 1024 277 29.349 7.485
5.884
>> That is true. I have to look into it. But it might be because the two
>> servers have the same list of upstream ntp servers but decide to sync to
>> different ones. But I should make shure that they have the same time. Do
>> you have any idea how to bind two ntp daemons tightly?
>
> Afaik, ntp doesn't really bind to a single ntp server, but to a group of
> servers, and selects the one it thinks is the most accurate.
>
> Having them select different servers shouldn't be a problem, as long as
> all servers actually give proper time back.
>
> Maybe you should give an overview of how things are all setup?
To summerize it: 134.93.226.2 and 134.93.227.254 are firewall hosts
which act as ntp proxies (and others). They have the same configuration
and peer eachother. 134.93.226.19 is the internal network ntp server
which connects to the two firewall proxies. Most of the other servers
just connect to the internal server or additionally to the proxies.
Christoph
--
============================================================================
Christoph Martin, Leiter der EDV der Verwaltung, Uni-Mainz, Germany
Internet-Mail: [EMAIL PROTECTED]
Telefon: +49-6131-3926337
Fax: +49-6131-3922856
signature.asc
Description: OpenPGP digital signature
