> Le 28 août 2015 à 12:12, ※踏梦狼※ <121156...@qq.com> a écrit :In > /var/log/messages have like "no_sys_peer" information,but the time is correct! >
no_sys_peer - means that the configured servers are not considered usable. Maybe they could not be accessed. See ntpq -pn stats for clues. Is « reach » not equal to 377, has « when » value exceeded the "poll" interval? It could be that it is a connection issue (routing?). Are your ntp servers used exclusively for ntpd or do they get high application use as well? > Aug 24 18:31:40 service ntpd[1596]: peers refreshed > Aug 24 18:32:49 service ntpd[1596]: 0.0.0.0 0613 03 spike_detect +0.155167 s > Aug 24 19:26:24 service ntpd[1596]: 0.0.0.0 061c 0c clock_step +0.158865 s When you say the time is correct, it is difficult to say by eyeballing a wall clock. Try ntpdate -d « server name » to see what the offset is. > Aug 24 19:26:24 service ntpd[1596]: 0.0.0.0 0615 05 clock_sync > Aug 24 19:26:25 service ntpd[1596]: 0.0.0.0 c618 08 no_sys_peer > Aug 25 15:46:54 service ntpd[1596]: Deleting interface #53 br_wan, > 192.168.122.208#123, interface stats: received=180, sent=287, dropped=0, > active_time=101542 secs > Aug 25 15:46:54 service ntpd[1596]: 202.120.2.101 interface 192.168.122.208 > -> (none) > Aug 25 15:46:54 service ntpd[1596]: 202.112.31.197 interface 192.168.122.208 > -> (none) > Aug 25 15:46:54 service ntpd[1596]: 202.112.10.36 interface 192.168.122.208 > -> (none) > Aug 25 15:46:54 service ntpd[1596]: peers refreshed > Aug 25 15:46:56 service ntpd[1596]: Listen normally on 55 br_wan > 192.168.123.208 UDP 123 > Aug 25 15:46:56 service ntpd[1596]: peers refreshed > Aug 25 15:46:57 service ntpd[1596]: 0.0.0.0 0628 08 no_sys_peer > service:/root# date > Fri Aug 28 18:07:49 CST 2015 > > Is it related ntp version result time is not normal ? my ntp version like > below: > > [root@S10-2-4-2 ~]# rpm -qa|grep ntp > ntpdate-4.2.6p5-1.el6.centos.x86_64 > ntp-4.2.6p5-1.el6.centos.x86_64 I don’t know about CentOS, but although 4.2.6p5 is not recommended, I have it running without your issues. > > > thanks > ------------------ 原始邮件 ------------------ > 发件人: "Mike Cook";<michael.c...@sfr.fr>; > 发送时间: 2015年8月28日(星期五) 下午5:59 > 收件人: "※踏梦狼※"<121156...@qq.com>; > 抄送: "questions"<questions@lists.ntp.org>; > 主题: Re: [ntp:questions] what's the matter with my ntp > > > > Le 28 août 2015 à 11:43, ※踏梦狼※ <121156...@qq.com> a écrit : > > > > The ntp client have stand alone and virtual machines, Those machines run > > serveral days,the time differ 30 seconds compare the normal time。 you look > > the below log: > > > > > 20 Aug 20:05:15 ntpd[14554]: 0.0.0.0 0615 05 clock_sync > > > 20 Aug 20:05:16 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 20 Aug 20:42:53 ntpd[14554]: 0.0.0.0 c613 03 spike_detect +0.949681 s > > > 20 Aug 21:00:09 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 21 Aug 14:24:50 ntpd[14554]: ntpd exiting on signal 15 > > > > could you tell me what's the meaning of no_sys_peer、spike_detect and > > clock_step ? Are those normal ? > > What’s normal? The messages are in response to what the client ntpd > detects when comparing the local clock with the set of configured servers > (peers). > IIRC: > no_sys_peer Indicates that there is no server that satisfies ntpd’s > stability criteria. > spike_detect This is informational in that a difference between the local > clock and the valid servers was temporarily greater than the 128ms max offset. > clock_step Normally modifies the local system clock frequency to adjust > for differences between it and the valid servers. If the offset is greater > than 128ms, then unless > configured otherwise, will step the system clock. > Mike > > > > > my clock seeting like this: > > [root@S10-2-1-3 ~]# cat /etc/sysconfig/clock > > ZONE="Asia/Shanghai" > > > > How i solved this problem ? > > > > > > ------------------ 原始邮件 ------------------ > > 发件人: "Mike Cook";<michael.c...@sfr.fr>; > > 发送时间: 2015年8月28日(星期五) 下午5:25 > > 收件人: "※踏梦狼※"<121156...@qq.com>; > > 抄送: "questions"<questions@lists.ntp.org>; > > 主题: Re: [ntp:questions] what's the matter with my ntp > > > > > > > Le 28 août 2015 à 04:52, ※踏梦狼※ <121156...@qq.com> a écrit : > > > > > > 20 Aug 12:42:52 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 20 Aug 12:58:17 ntpd[14554]: 0.0.0.0 c612 02 freq_set kernel -586.374 PPM > > > ********* > > > 20 Aug 12:58:17 ntpd[14554]: 0.0.0.0 c61c 0c clock_step -0.522594 s > > > 20 Aug 12:58:17 ntpd[14554]: 0.0.0.0 c615 05 clock_sync > > > 20 Aug 12:58:18 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 20 Aug 13:11:51 ntpd[14554]: 0.0.0.0 0613 03 spike_detect +0.247108 s > > > 20 Aug 13:28:12 ntpd[14554]: 0.0.0.0 061c 0c clock_step +0.174737 s > > > 20 Aug 13:28:12 ntpd[14554]: 0.0.0.0 0614 04 freq_mode > > > 20 Aug 13:28:13 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 20 Aug 13:43:52 ntpd[14554]: 0.0.0.0 c612 02 freq_set kernel -461.842 PPM > > > 20 Aug 13:43:52 ntpd[14554]: 0.0.0.0 c615 05 clock_sync > > > 20 Aug 19:48:08 ntpd[14554]: 0.0.0.0 0613 03 spike_detect +1.010504 s > > > ********* > > > 20 Aug 20:05:14 ntpd[14554]: 0.0.0.0 061c 0c clock_step +1.491656 s > > > 20 Aug 20:05:15 ntpd[14554]: 0.0.0.0 0615 05 clock_sync > > > 20 Aug 20:05:16 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 20 Aug 20:42:53 ntpd[14554]: 0.0.0.0 c613 03 spike_detect +0.949681 s > > > 20 Aug 21:00:09 ntpd[14554]: 0.0.0.0 c618 08 no_sys_peer > > > 21 Aug 14:24:50 ntpd[14554]: ntpd exiting on signal 15 > > > 28 Aug 10:25:48 ntpd[5937]: 0.0.0.0 c016 06 restart > > > 28 Aug 10:25:48 ntpd[5937]: 0.0.0.0 c012 02 freq_set kernel -471.344 PPM > > > 28 Aug 10:29:04 ntpd[5937]: 0.0.0.0 c61c 0c clock_step +0.233855 s > > > 28 Aug 10:29:04 ntpd[5937]: 0.0.0.0 c614 04 freq_mode > > > 28 Aug 10:29:05 ntpd[5937]: 0.0.0.0 c618 08 no_sys_peer > > > 28 Aug 10:44:43 ntpd[5937]: 0.0.0.0 c612 02 freq_set kernel -25.526 PPM > > > 28 Aug 10:44:43 ntpd[5937]: 0.0.0.0 c61c 0c clock_step +0.418623 s > > > 28 Aug 10:44:44 ntpd[5937]: 0.0.0.0 c618 08 no_sys_peer > > > > > > > The above indicates that this clients local clock (cpu) is running too > > slow, exceeding the ntpd’s max drift factor of 500ppm and also the max > > offset factor of 128ms. > > So if this is the only system affected it looks like the clock is sick. > > Monitor it’s drift outside NTP . > > Is this the only client seeing the issue, or are others? Are the clients > > stand alone or virtual machines? If virtual, maybe you are missing a system > > config parameter. > > > > Hope that helps. > > > > "Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une > > petite et provisoire sécurité, ne méritent ni liberté ni sécurité." > > Benjimin Franklin > > "Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une > petite et provisoire sécurité, ne méritent ni liberté ni sécurité." > Benjimin Franklin "Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une petite et provisoire sécurité, ne méritent ni liberté ni sécurité." Benjimin Franklin _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions