<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ntp sync in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5920729#M482840</link>
    <description>&lt;P&gt;Thank you much for your support and explaination&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;prashanth&lt;/P&gt;</description>
    <pubDate>Thu, 03 Jan 2013 11:01:37 GMT</pubDate>
    <dc:creator>prashanth</dc:creator>
    <dc:date>2013-01-03T11:01:37Z</dc:date>
    <item>
      <title>ntp sync</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5918643#M482794</link>
      <description>&lt;P&gt;Dear All ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have recived the NTP related alert on 31 Dec 12 night .&lt;/P&gt;&lt;P&gt;xntpd[2279]: Unsynchronized, possible remote server failure&amp;nbsp; or defective hardware clock&lt;/P&gt;&lt;P&gt;when i chekced the syslog&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oct 20 11:55:56 sxpx123 xntpd[1959]: tickadj = 625, tick = 10000, tvu_maxslew = 61875&lt;BR /&gt;Oct 20 11:55:56 sxpx123 xntpd[1959]: precision = 7 usec&lt;BR /&gt;Oct 20 12:00:46 sxpx123 xntpd[1959]: synchronized to 172.19.19.30, stratum=7&lt;BR /&gt;Jan&amp;nbsp; 1 00:00:01 sxpx123 xntpd[1959]: leap second occurred, stepped time back 1 second&lt;BR /&gt;Jan&amp;nbsp; 1 02:29:27 sxpx123 xntpd[1959]: synchronisation lost&lt;BR /&gt;Jan&amp;nbsp; 1 02:41:37 sxpx123 xntpd[1959]: synchronized to 172.19.1.30, stratum=7&lt;BR /&gt;Jan&amp;nbsp; 1 02:41:38 sxpx123 xntpd[1959]: time reset (step) 1.030062 s&lt;BR /&gt;Jan&amp;nbsp; 1 02:41:38 sxpx123 xntpd[1959]: synchronisation lost&lt;BR /&gt;Jan&amp;nbsp; 1 02:46:58 sxpx123 xntpd[1959]: synchronized to 172.19.19.30, stratum=7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;after that is ysnchronised. So acn one help me to undetstand it . The alert which we got (xntpd[2279]: Unsynchronized, possible remote server failure&amp;nbsp; or defective hardware clock) because of only&amp;nbsp; (an&amp;nbsp; 1 00:00:01 sxpx123 xntpd[1959]: leap second occurred, stepped time back 1 second)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!!!&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jan 2013 13:00:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5918643#M482794</guid>
      <dc:creator>prashanth</dc:creator>
      <dc:date>2013-01-01T13:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: ntp sync</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5918921#M482815</link>
      <description>&lt;P&gt;A leap second is occasionally inserted into the world-wide clocks to compensate for the slightly longer time of the earth's rotation. Here's a couple of references:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki/Leap_second http://www.timeanddate.com/time/leapseconds.html" target="_blank"&gt;http://en.wikipedia.org/wiki/Leap_second&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki/Leap_second http://www.timeanddate.com/time/leapseconds.html" target="_blank"&gt;http://www.timeanddate.com/time/leapseconds.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;NTP assumes that a properly operating time source will not suddently jump without notice. It turns out that the NTP protocol does have a mechanism for handling a leap second:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.ntp.org/bin/view/Support/ConfiguringNTP#Section_6.14." target="_blank"&gt;http://support.ntp.org/bin/view/Support/ConfiguringNTP#Section_6.14.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, it appears that HP-UX/xntpd does not do anything with the leap second. As such, you'll see the out-of-sync message which then be corrected like any out of sync condition.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are a couple of discussions about HP-UX NTP and leap seconds:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hpe.com/t5/General/HP-Support-Statement-for-XNTPD-Leap-Second-Processing/td-p/3663790" target="_blank"&gt;http://h30499.www3.hp.com/t5/General/HP-Support-Statement-for-XNTPD-Leap-Second-Processing/td-p/3663790&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hpe.com/t5/System-Administration/HP-UX-and-Tru64-leap-second-handling/td-p/5609135" target="_blank"&gt;http://h30499.www3.hp.com/t5/System-Administration/HP-UX-and-Tru64-leap-second-handling/td-p/5609135&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So your system is fine. The pertubation was corrected automatically.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jan 2013 02:13:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5918921#M482815</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2013-01-02T02:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: ntp sync</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5920729#M482840</link>
      <description>&lt;P&gt;Thank you much for your support and explaination&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;prashanth&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jan 2013 11:01:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ntp-sync/m-p/5920729#M482840</guid>
      <dc:creator>prashanth</dc:creator>
      <dc:date>2013-01-03T11:01:37Z</dc:date>
    </item>
  </channel>
</rss>

