Translated message

A translation of this page exists in English.

spike_detect が発生したあと、多くの場合に ntp が no_sys_peer を書き込むのはなぜですか?

Solution Verified - Updated -


  • spike_detectclock step のあとに ntpd が no_sys_peer を書き込みます。このメッセージは何を示していますか? メッセージが出力されたのはなぜですか?
May  6 14:18:19 ntpd[34933]: 0613 03 spike_detect -35.000067 s
May  6 14:22:25 ntpd[34933]: 0618 08 no_sys_peer
May  6 14:30:38 ntpd[34933]: 061c 0c clock_step -35.000340 s
May  6 14:30:38 ntpd[34933]: 0615 05 clock_sync
May  6 14:30:39 ntpd[34933]: c618 08 no_sys_peer


  • Red Hat Enterprise Linux 6
  • ntp

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content