[ntp:questions] status f034 while exit from orphan status expected
Miernik, Jerzy (Jerzy)
jerzy.miernik at alcatel-lucent.com
Wed Nov 17 17:07:00 UTC 2010
Two notes:
1. I should have added the ntpd version: 4.2.4p7.
2. after ntpd restart in e.f.g.h, the ntpd immediately recognized server stratum 1:
# ntpq -np -c as
ind assID status conf reach auth condition last_event cnt
===========================================================
1 17955 8015 yes yes none reject clock expt 1
2 17956 8000 yes yes none reject
3 17957 f614 yes yes ok sys.peer reachable 1
4 17958 c000 yes yes bad reject
remote refid st t when poll reach delay offset jitter
==============================================================================
127.127.28.0 .GPS. 0 l - 64 0 0.000 0.000 0.004
127.127.22.0 .PPS. 0 l - 16 0 0.000 0.000 0.004
*10.77.0.6 .GPS. 1 u 1 64 37 1.068 18164.3 31.238
10.98.0.6 .INIT. 16 u - 64 0 0.000 0.000 0.000
kon4204_98:/var/log#
Still, could an expert please speculate why would an ntpd remain stuck in orphan mode?
Should some configuration be add to a very simple line 'tos orphan 5' to help ntpd's get out of orphan mode promptly?
Thanks,
Jerzy.
_____________________________________________
From: Miernik, Jerzy (Jerzy)
Sent: Wednesday, November 17, 2010 10:52 AM
To: 'questions at lists.ntp.org'
Subject: status f034 while exit from orphan status expected
I have two servers that were orphans stratum 5. One, a.b.c.d, got restored GPS signal and became a stratum 1 server, the other, e.f.g.h, seems to be stuck (for 15 hours thus far) in stratum 5, rejecting the time served by stratum 1 server.
Output from a.b.c.d:
# ntpq -np -c as
ind assID status conf reach auth condition last_event cnt
===========================================================
1 2174 9624 yes yes none sys.peer reachable 2
2 2175 8015 yes yes none reject clock expt 1
3 2176 f014 yes yes ok reject reachable 1
4 2177 c000 yes yes bad reject
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.28.0 .GPS. 0 l 21 64 377 0.000 951.561 69.112
127.127.22.0 .PPS. 0 l - 16 0 0.000 0.000 0.004
e.f.g.h 127.0.0.1 5 u 39 64 377 1.032 -17965. 53.979
a.b.c.d .INIT. 16 u - 1024 0 0.000 0.000 0.000
Output from e.f.g.h:
# ntpq -np -c as
ind assID status conf reach auth condition last_event cnt
===========================================================
1 47572 8015 yes yes none reject clock expt 1
2 47573 8015 yes yes none reject clock expt 1
3 47574 f034 yes yes ok reject reachable 3
4 47575 c000 yes yes bad reject
remote refid st t when poll reach delay offset jitter
==============================================================================
127.127.28.0 .GPS. 0 l - 64 0 0.000 0.000 0.004
127.127.22.0 .PPS. 0 l - 16 0 0.000 0.000 0.004
a.b.c.d .GPS. 1 u 194 256 377 1.072 17653.6 232.230
e.f.g.h .INIT. 16 u - 1024 0 0.000 0.000 0.000
Why the e.f.g.h could be rejecting time signals from a stratum1 ?
Thanks,
Jerzy Miernik.
More information about the questions
mailing list