NTP problem - Clock too fast for NTP to keep up?
zordah at zordah.net
Fri Feb 11 01:19:45 UTC 2005
I've kept on playing with tickadj and found out that 9000 seems to be
the lowest that FC3 will go in my virtual server. However this seems to
have slowed the clock down to within a couple of seconds gain every 2
Feb 11 10:41:56 krusty ntpdate: step time server 18.104.22.168
offset -4.675165 sec
Feb 11 10:42:01 krusty ntpdate: adjust time server 22.214.171.124
offset -0.165226 sec
Feb 11 10:43:58 krusty ntpdate: step time server 126.96.36.199
offset -2.661458 sec
Feb 11 10:45:57 krusty ntpdate: step time server 188.8.131.52
offset -4.160441 sec
Feb 11 10:47:59 krusty ntpdate: step time server 184.108.40.206
offset -2.028393 sec
Thinking that this might be within ntpd's tolerances now I turned off
the 2 minute ntpdate and restarted ntp.
Looks like ntpd still isn't working however:
# ntpq -p
remote refid st t when poll reach delay offset
fizban.zordah.n 0.0.0.0 5 u 3 64 377 0.948 14109.8
This could be important, even though the reach value is tell me it can
reach the NTP server ntptrace is telling me a different story!
# ntptrace 220.127.116.11
18.104.22.168: timed out, nothing received
***Request timed out
Why is this?
Zordah IT - IT Consultancy and Internet Services
Ph: (0414) 724-766 Fax: (07) 3344-5827
Web: www.zordah.net Email: zordah at zordah.net
More information about the users