One of my NTP servers (Server D below) is rejecting both of its peers.
They, on the other hand, each have consistent candidate status for both
of *their* peers. This rejecting server does pick the master server as
it's reference source but has no candidates listed. I don't see anything
that would cause this. I'm worried that, should the master fail, this
naughty boy will not be a well-behaved Orphan Child.
Can someone explain why they think this might be happening and suggest a
course of action? I've included some relevant data below. Note that some
ntpq output has wrapped below. Please let me know if you need more info.
./Cal
=============
NTP Versions:
=============
Server A: ntp-4.1.2-0.rc1.2
Server B: ntp-4.2.0.a.20040617-6.el4
Server C: ntp-4.2.0.a.20040617-6.el4
Server D: ntp-4.2.4p2-6.fc8
========
Configs:
========
Server A - Master [fluid]:
--------------------------
tos orphan 5
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 1
driftfile /etc/ntp/drift
broadcastdelay 0.008
keys /etc/ntp/keys
--------------------------
Server B [jato]:
----------------
tos orphan 5
server 192.168.3.132
peer 192.168.1.30
peer 192.168.2.6
server 127.127.1.0
fudge 127.127.1.0 stratum 12
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
keys /etc/ntp/keys
----------------
Server C [pegasus]:
-------------------
tos orphan 5
server 192.168.3.132
peer 192.168.3.9
peer 192.168.1.30
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 8
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
keys /etc/ntp/keys
-------------------
Server D [axl]:
---------------
tos orphan 5
server 192.168.3.132
peer 192.168.3.9
peer 192.168.2.6
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
keys /etc/ntp/keys
---------------
=============
Associations:
=============
(ntpq -c pe -c as)
Server A:
---------
remote refid st t when poll reach delay offset
jitter
==============================================================================
*LOCAL(0) .LCL. 1 l 17 64 377 0.000 0.000
0.015
ind assID status conf reach auth condition last_event cnt
===========================================================
1 56268 9624 yes yes none sys.peer reachable 2
---------
Server B:
---------
remote refid st t when poll reach delay offset
jitter
==============================================================================
*fluid LOCAL(0) 2 u 108 256 377 0.275 -0.931
0.830
+axl 192.168.3.132 3 u 59 256 377 23.273 1.082
6.640
+pegasus 192.168.3.132 3 u 217 256 333 24.645 2.566
0.766
LOCAL(0) LOCAL(0) 12 l 24 64 377 0.000 0.000
0.004
ind assID status conf reach auth condition last_event cnt
===========================================================
1 63404 9614 yes yes none sys.peer reachable 1
2 63405 9414 yes yes none candidat reachable 1
3 63406 9414 yes yes none candidat reachable 1
4 63407 9014 yes yes none reject reachable 1
---------
Server C:
---------
remote refid st t when poll reach delay offset
jitter
==============================================================================
*fluid LOCAL(0) 2 u 793 1024 377 27.103 -4.505
2.406
+jato 192.168.3.132 3 u 221 256 166 24.675 -2.581
0.652
+axl 192.168.3.132 3 u 998 512 374 31.983 -1.971
0.199
LOCAL(0) LOCAL(0) 8 l 45 64 377 0.000 0.000
0.001
ind assID status conf reach auth condition last_event cnt
===========================================================
1 29660 9614 yes yes none sys.peer reachable 1
2 29661 9414 yes yes none candidat reachable 1
3 29662 9424 yes yes none candidat reachable 2
4 29663 9014 yes yes none reject reachable 1
---------
Server D:
---------
remote refid st t when poll reach delay offset
jitter
==============================================================================
*fluid LOCAL(0) 2 u 979 1024 377 24.665 -1.216
0.550
jato 192.168.3.132 3 u 177 256 376 24.585 -0.400
5.980
pegasus 192.168.3.132 3 u 227 1024 377 31.989 1.968
0.127
LOCAL(0) .LOCL. 10 l 30 64 377 0.000 0.000
0.001
ind assID status conf reach auth condition last_event cnt
===========================================================
1 48371 9624 yes yes none sys.peer reachable 2
2 48372 9024 yes yes none reject reachable 2
3 48373 9024 yes yes none reject reachable 2
4 48374 9024 yes yes none reject reachable 2
---------
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions
