<rdf:RDF
    xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'
    xmlns:s='http://snipsnap.org/rdf/snip-schema#'
    xml:base='http://bliki.rimuhosting.com/rdf'>
    <s:Snip rdf:about='http://bliki.rimuhosting.com/rdf#knowledgebase/linux/miscapplications/ntp'
         s:cUser='retep'
         s:oUser=''
         s:mUser='retep'>
        <s:name>knowledgebase/linux/miscapplications/ntp</s:name>
        <s:content>1. Time out of Sync on NTPd server?&#xD;&#xA;&#xD;&#xA;NTPd synchronizes a servers time with an external time source.  Keeping it up to date.&#xD;&#xA;&#xD;&#xA;Sometimes servers that are running ntpd get out of sync.&#xD;&#xA;&#xD;&#xA;In these cases restarting ntp regularly (weekly/monthly?) may help.&#xD;&#xA;&#xD;&#xA;e.g. in this case there were no peers found when we first looked (the peers only appeared after an ntpd restart).&#xD;&#xA;&#xD;&#xA;{code}&#xD;&#xA;[root@host82 ~]# ntpq -p&#xD;&#xA;     remote           refid      st t when poll reach   delay   offset  jitter&#xD;&#xA;==============================================================================&#xD;&#xA;*LOCAL(0)        LOCAL(0)        10 l   41   64  377    0.000    0.000   0.001&#xD;&#xA;# /etc/init.d/ntpd restart&#xD;&#xA;Shutting down ntpd:                                        [  OK  ]&#xD;&#xA;Starting ntpd:                                             [  OK  ]&#xD;&#xA;# ntpq -p&#xD;&#xA;     remote           refid      st t when poll reach   delay   offset  jitter&#xD;&#xA;==============================================================================&#xD;&#xA; ad.67.1343.stat 132.163.4.103    2 u    1   64    1    3.094  -41335.   0.001&#xD;&#xA; mail.landrin.ru .INIT.          16 u    -   64    0    0.000    0.000 4000.00&#xD;&#xA; vine.desynched. .INIT.          16 u    -   64    0    0.000    0.000 4000.00&#xD;&#xA; LOCAL(0)        LOCAL(0)        10 l    -   64    0    0.000    0.000 4000.00&#xD;&#xA;{code}&#xD;&#xA;&#xD;&#xA;It seems like ntpd establishes its peers when it first starts up.  Perhaps if there is a dns issue causing the ntp peer to not be found at that time the peer may not be used?  Also perhaps if a peer stops responding for a long period it will not be kicked out of the server list and replaced with another?  e.g. a good ntp server to use can be from ntps pooled servers: 0.pool.ntp.org, 1.pool.ntp.org, etc.&#xD;&#xA;</s:content>
        <s:mTime>2007-08-20 22:40:44.0</s:mTime>
        <s:cTime>2007-08-20 22:40:44.0</s:cTime>
        <s:comments
             rdf:type='http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag'/>
        <s:snipLinks>
            <rdf:Bag>
                <rdf:li rdf:resource='#snipsnap-search'/>
                <rdf:li rdf:resource='http://bliki.rimuhosting.com/rdf#knowledgebase/linux'/>
                <rdf:li rdf:resource='#knowledgebase'/>
                <rdf:li rdf:resource='http://bliki.rimuhosting.com/rdf#knowledgebase/linux/miscapplications'/>
                <rdf:li rdf:resource='#snipsnap-index'/>
            </rdf:Bag>
        </s:snipLinks>
        <s:attachments
             rdf:type='http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag'/>
    </s:Snip>
</rdf:RDF>
