stratum サーバーとして稼動する RHEL の挙動: NTP うるう秒の no_sys_peer が確認される
Issue
- 以下の、うるう秒後のトレースは何を意味していますか?
- うるう秒に続いて、ログに
no_sys_peerが記録されるのはなぜですか?
Jun 30 09:23:54 nycommon-ns1 ntpd[52131]:Listening on routing socket on fd #24 for interface updates
Jun 30 09:23:54 nycommon-ns1 ntpd[52131]:0.0.0.0 c01e 0e TAI 36 leap 201507010000 expire 201512280000
Jun 30 09:23:54 nycommon-ns1 ntpd[52131]:0.0.0.0 c016 06 restart
Jun 30 09:23:54 nycommon-ns1 ntpd[52131]:0.0.0.0 c012 02 freq_set ntpd -0.311 PPM
Jun 30 09:24:43 nycommon-ns1 ntpd[52131]:0.0.0.0 c615 05 clock_sync
Jun 30 09:24:43 nycommon-ns1 ntpd[52131]:0.0.0.0 0619 09 leap_armed
Jun 30 20:00:00 nycommon-ns1 ntpd[52131]:0.0.0.0 061b 0b leap_event
Jun 30 20:02:33 nycommon-ns1 ntpd[52131]:0.0.0.0 0618 08 no_sys_peer
Jun 30 20:30:59 nycommon-ns1 ntpd[52131]:0.0.0.0 0628 08 no_sys_peer
Jun 30 20:40:44 nycommon-ns1 ntpd[52131]:0.0.0.0 0638 08 no_sys_peer
Environment
- Red Hat Enterprise Linux (RHEL) 4
- Red Hat Enterprise Linux (RHEL) 5
- Red Hat Enterprise Linux (RHEL) 6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.