On 1/9/2013 12:41 AM, Arpith Nayak wrote:
Adding my .conf file:driftfile /tmp/ntp.drift/ server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server 3.pool.ntp.org Adding ntpq -p data: [Thu Feb 10 12:55:51 root@root-ubuntu:~]# ntpq -p 0.pool.ntp.org remote refid st t when poll reach delay offset jitter ============================================================================== *64.147.116.229 .ACTS. 1 u 151 1024 377 2.439 -0.632 0.052 +131.107.13.100 .ACTS. 1 u 879 1024 377 27.853 1.041 0.539 -time.nrc.ca 132.246.11.231 2 u 989 1024 377 86.821 -4.132 8.778 -time1.chu.nrc.c 209.87.233.52 2 u 53 1024 377 109.221 3.153 9.377 +dense.utcc.utor 128.100.200.166 2 u 88 1024 377 64.115 -1.841 0.454 -dns4.utoronto.c 128.100.103.253 2 u 167 1024 377 65.252 -43.422 56.093 _______________________________________________
Of much greater use would be "ntpq -p" from the system having the problem. Is ntpd still running on that system or has it exited. If it has exited, you should check the syslog for any messages. If it hasn't the ntpq output would be the next step to seeing what is happening.
By the way, the output of "ntpq -p 0.pool.ntp.org" isn't very useful for another reason. Since this is a roundrobin DNS address, there isn't any guarantee that it is even the same system that the ntpd process is using.
Brian. _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
