> Le 28 août 2015 à 12:36, ※踏梦狼※ <121156...@qq.com> a écrit :
>
> hello,
> you say 128ms max offset ,is it refer to the time difference of the
> client ntp system time and ntp peer time? if the time difference bigger
> 128ms, ntp don't sync clock ?
>
No, the system clock will be synced, but may be « stepped » rather than «
slewed ».
> 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
