From: "Bitbucket" <[EMAIL PROTECTED]>
I had a quick look, but didn't find the bit that deals with
'responding reasonably to multiple queries' - probably because I am
not at all versed in perl scripts... It seemed to make just two
requests where it does 'fetch offset by NTP'
It makes a request then if the score isn't 1* it immediately requests again.
*: stratum is <=5 and the average of the receive and transmit timestamp
differences is <= 0.1
In my case I was in the pool briefly two weeks ago when I joined but since
then my score hovers around -40 as my server flips between "server offset is
ok" and "server is unreachable".
I can see the packets coming in and going out with tcpdump, but they don't
reach the monitoring server:
This exchange just got logged as "server is unreachable":
2006-09-02 07:06:00.067958 IP (tos 0x0, ttl 53, id 25012, offset 0, flags
[DF], length: 76) 63.251.223.163.38636 > 192.168.123.189.123: [udp sum ok]
NTPv3 client, strat 0, poll 0, prec 0 dist 0.000000, disp 0.000000, ref
(unspec)@0.000000000 orig 0.000000000 rec 0.000000000 xmt
1157180759.437371432 (1936/09/02 08:05:59)
2006-09-02 07:06:00.068017 IP (tos 0x10, ttl 64, id 13498, offset 0, flags
[DF], length: 76) 192.168.123.189.123 > 63.251.223.163.38636: [bad udp cksum
6644!] NTPv3 server, strat 2, poll 0, prec -20 dist 0.057434, disp 0.039703,
ref [EMAIL PROTECTED] (2006/09/02 08:00:15) orig
1157180759.437371432 (1936/09/02 08:05:59) rec -2085978495.369394421
xmt -2085978495.369375437
2006-09-02 07:06:02.038219 IP (tos 0x0, ttl 53, id 25212, offset 0, flags
[DF], length: 76) 63.251.223.163.38643 > 192.168.123.189.123: [udp sum ok]
NTPv3 client, strat 0, poll 0, prec 0 dist 0.000000, disp 0.000000, ref
(unspec)@0.000000000 orig 0.000000000 rec 0.000000000 xmt
1157180761.435410887 (1936/09/02 08:06:01)
2006-09-02 07:06:02.038267 IP (tos 0x10, ttl 64, id 13499, offset 0, flags
[DF], length: 76) 192.168.123.189.123 > 63.251.223.163.38643: [bad udp cksum
5ce5!] NTPv3 server, strat 2, poll 0, prec -20 dist 0.057434, disp 0.039733,
ref [EMAIL PROTECTED] (2006/09/02 08:00:15) orig
1157180761.435410887 (1936/09/02 08:06:01) rec -2085978495.397173881
xmt -2085978495.397154897
I wonder what the timeout is on the get_ntp_response function deciding no
packet was received..? When there were the monitoring issues yesterday the
non-American servers seemed to be affected more than American ones. Maybe
the timeout needs to be increased?
Laurence
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
