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

Solution Verified - Updated -

Issue

  • After 'spike_detect' and 'clock step' ntpd writes 'no_sys_peer'. What is the reason and why it write such message?
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

Environment

  • Red Hat Enterprise Linux 6
  • ntp

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.