[ntp:questions] Query regarding Ntp 4.2.8 p6, leap second tests

Sowmya Manapragada skoganty at gmail.com
Sat Apr 23 11:19:37 UTC 2016


Thank you Martin for all the details. These helped a lot and i could get
the leap file accepted by the server, but always leap bit leap=11 in the rv
output of server even when ,leap file is accepted by server ( i could see
in server ntpq rv 0 op as .leapsec=201507010000,expire=201612280000 , but
leap=11)

Please see details below:
     Server Machine> Windows 7
1:> server ntp.conf:>
      server 127.127.1.0  #sync to local clock
      fudge stratum 10
      leapfile "c:\\xxxx\xxxx\xxxx\leap-seconds.3629404800"  #path to leap
sec file
2:> server machine:
       "You should set the time of your NTP server at least 30 minutes
before
        the time of the leap second event, e.g. to 2015-06-30 23:30:00 UTC,
and
        then restart the NTP service"
        Done exactly the same , leap sec file is accepted . (changed my
server local clock to UTC 2015-06-30 23:30:00 UTC)
        ntpq -c rv 0 :> associd=0 status=c016 leap_alarm, sync_unspec, 1,
event,restart,refid=INIT,peer=0,tc=3,
        version "ntpd 4.2.8p4 at 1.3265 ....... leap=11........ ....
leapsec=201507010000,expire=201612280000
3:>        I waited for around 1 hr    server time now UTC 2015-07-01
12:30:00 , but could never see this
            "Also, the output should contain something like "leap=01"
during the
             hours before the leap second."
              In my case leap was always "leap=11"    even when the leap
file is accepted.

Am i missing something , kindly suggest. how do i know if leap sec is added
when leap=11 always, even when leap file is accepted by server.
Also any way to identify in a client taking this server time that a leap
sec is added.
Thank's in advance.

thanks,
Shyam


On Tue, Apr 19, 2016 at 5:29 PM, Sowmya Manapragada <skoganty at gmail.com>
wrote:

> Thank you, will try the steps you suggested.
>
> thanks,
> Shyam
>
> On Mon, Apr 18, 2016 at 4:34 PM, Martin Burnicki <
> martin.burnicki at burnicki.net> wrote:
>
>> Sowmya Manapragada wrote:
>> > Hello All,
>> > Request for inputs regarding a small leap second test which i am trying
>> to
>> > do with my ntp4.2.8p6..
>> >
>> > Environment :
>> >    Windows 7 client and windows 7 server test machines in a small
>> networked
>> > LAN.
>> > For Leap second configuration referred the following link:
>> >
>> >          :
>> > http://support.ntp.org/bin/view/Support/ConfiguringNTP#Section_6.14./
>> > Steps: followed:>
>> >
>> > 1)  Configured leap-second (and  impend leap seconds on Jul 1 Jul 2015)
>> >   2) server side: included this leapsecond file, and made it as orphan
>> > server.
>>
>> You should set the time of your NTP server at least 30 minutes before
>> the time of the leap second event, e.g. to 2015-06-30 23:30:00 UTC, and
>> then restart the NTP service. Please note leap seconds are scheduled for
>> *UTC* midnight, not midnight of some local time zone.
>>
>> If you set the system time on your NTP server too short before midnight
>> then ntpd may run in "frequency" mode for a while, and if "frequency"
>> mode lasts until after midnight then your NTP server may not insert the
>> leap second properly. See:
>> http://bugs.ntp.org/show_bug.cgi?id=2838
>>
>> You can run the command "ntpq -c rv" to check if your server has
>> accepted the leap second file. If it has then the output should contain
>> something like:
>>
>> leapsec=201507010000, expire=201612280000
>>
>> Also, the output should contain something like "leap=01" during the
>> hours before the leap second.
>>
>> >   3) client side:Moved back in time (just for testing) (example> moved
>> back
>> > to by june 31st 11.56 pm .)
>>
>> In *any* case you should restart ntpd when you have changed the system
>> time. Otherwise it will take up to 15 minutes until accepts a time step,
>> and if the time has changed by more than ~1000 seconds the service will
>> even stop itself with an appropriate message in the application event log.
>>
>> Martin
>>
>>
>


More information about the questions mailing list