You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/03/29 20:15:25 UTC

[jira] [Commented] (INFRA-11565) evaluate local clock binding for ntp

    [ https://issues.apache.org/jira/browse/INFRA-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216530#comment-15216530 ] 

Chris Lambertus commented on INFRA-11565:
-----------------------------------------

from sebb: The NTP monitoring method also may need to be checked - it looks as though the check may rely on the host self-reporting if it is not synch.

> evaluate local clock binding for ntp
> ------------------------------------
>
>                 Key: INFRA-11565
>                 URL: https://issues.apache.org/jira/browse/INFRA-11565
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: ntp
>            Reporter: Chris Lambertus
>            Assignee: Chris Lambertus
>            Priority: Minor
>
> The puppet-based ntp.conf appears to preferentially bind to an undisciplined local clock at stratum 10 when other pool servers are slow or unavailable. This should be evaluated as it may cause ntp to bind to itself as a preferred server and not sync properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)