Why after spike detect, most of the time ntp write 'no_sys_peer'?

环境

• Red Hat Enterprise Linux 6
• ntp

问题

• After 'spike_detect' and 'clock step' ntpd writes 'no_sys_peer'. What is the reason and why it write such message?

Raw

May  6 14:18:19 example.com ntpd[34933]: 0.0.0.0 0613 03 spike_detect -35.000067 s
May  6 14:22:25 example.com ntpd[34933]: 0.0.0.0 0618 08 no_sys_peer
May  6 14:30:38 example.com ntpd[34933]: 0.0.0.0 061c 0c clock_step -35.000340 s
May  6 14:30:38 example.com ntpd[34933]: 0.0.0.0 0615 05 clock_sync
May  6 14:30:39 example.com ntpd[34933]: 0.0.0.0 c618 08 no_sys_peer

决议

• When ntpd noticed the change in the clock, it step the clock, while stepping ntp resets almost everything i.e server trust etc.... The message is logged when the source selection doesn't have any selectable source (as ntp lose trust). After the clock step, ntp collects new samples for all sources, trust them again and reselect them.

 

time reset : The time error exceeds the step threshold and has been reset to the correct time.
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.