Oncore leap second bug at 11/29/2003 62:28:15
Sure enough, the Oncore 256 week leap second
bug showed up as predicted by Motorola. It was
a little different than we thought; this is how an
Oncore VP GPS receiver reported time yesterday:
If any of you saw NTP anomalies I'd be interested
to hear about them. Presumably the invalid hour
saved the day (the time stamp would be rejected).
For details see:
Tom Van Baak wrote:
> Sure enough, the Oncore 256 we...Leap second bug?
ntpd kicked my clock forward one second on January 1 at 00:19:38 UTC.
(My ntp.conf lists 12 servers. Delays range from 28 to 48 ms.)
Dec 31 23:25:39 offset 0.000329 sec freq -6.715 ppm error 0.000333 poll 8
Dec 31 23:28:39 offset 0.000329 sec freq -6.715 ppm error 0.000340 poll 8
Dec 31 23:31:39 offset 0.000329 sec freq -6.715 ppm error 0.000424 poll 8
Dec 31 23:34:39 offset 0.000403 sec freq -6.714 ppm error 0.000493 poll 8
Dec 31 23:37:39 offset 0.000270 sec freq -6.714 ppm error 0.000348 poll 8
Dec 31 23:40:39 offset 0.000270 sec freq -6.714 ppm error 0.000337 poll 8
Dec ...Leap second bug in Linux wastes electricity. More Linux Slopware.
"Power consumption at Hetzner Online's data centres jumped by "about
a megawatt" in the night from 30 June to 1 July due to a kernel bug
which resulted in many Linux systems reaching 100% processor usage
in dealing with the leap second added at midnight. The problem is
described in an email sent by the web hosting company to customers,
asking them to check their systems' CPU usage and, where necessary,
to restart their systems in order to...[News] Leap Second Bug Brings down Linux Servers at Linkedin, Reddit and Others
The leap second inserted at the weekend crippled Linux-powered servers
running one of the worlds largest airline reservation systems - delaying
and cancelling flights.
Machines running the mighty Amadeus Altea system were brought down soon
after an extra second was added to Coordinated Universal Time (UTC) at
midnight on Saturday, 30 June. The bonus second was inserted at the
direction of time boffins to keep UTC synchronised with Earth's slowing
The Altea system was taken offline for an hour, an...[ace-bugs] [asnmp]: [agent PDU receiving bug]
ACE VERSION: 5.5, released Sun Mar 05 11:10:32 2006.
HOST MACHINE and OPERATING SYSTEM:
MS Windows 2000, WINSOCK 2.0 (Product version 5.00.2195.6601 and
TARGET MACHINE and OPERATING SYSTEM, if different from HOST: -
COMPILER NAME AND VERSION (AND PATCHLEVEL):
C++ compiler MS Visual Studio.NET 2003 (with SP1)
AREA/CLASS/EXAMPLE AFFECTED: asnmp library, sagent class
DOES THE PROBLEM AFFECT:EXECUTION
SYNOPSIS: PDU receiving bug
I work with asnmp
library and "sagent" class for creating my simple SNMP agent.
I got no...-- Wolfram Research QA process defect: Bug in Mathematica 6 - N - 17 (MeijerG, no answer in 100000 seconds, regression bug)
If the same bugs exists through numerous software releases,
I think that is valuable public information.
It just should not happen.
-- Brad Cooper
-- NOT FIXED BUGS ARE DANGEROUS: THEY TEND TO GET MORE SEVERE --
Quality of CASs is our #1 care.
So our little demo continues. Hello again from the VM machine
which hopefully soon will be used by CAS manufacturers to the
benefit of...Leap seconds
There's a discussion on another group I follow about leap seconds - i.e.,
how 2009 was delayed for a second in Greenwich time because the rotation of
the earth is slowing.
Was this ever a concern for any Prime o/s'es?
On Jan 1, 3:38=A0pm, "tlmfru" <la...@mts.net> wrote:
> There's a discussion on another group I follow about leap seconds - i.e.,
> how 2009 was delayed for a second in Greenwich time because the rotation =
> the earth is slowing.
> Was this ever a concern for any Prime o/s'es?
Never meani...Leap Second
Since yesterday I saw the leap second Flag set on some servers of
ntp.pool.org. I'am quite surprise because the leap second add to be
set the 31/12/2008 and not the 1/12/2008.
Is it normal????
>Since yesterday I saw the leap second Flag set on some servers of
>ntp.pool.org. I'am quite surprise because the leap second add to be
>set the 31/12/2008 and not the 1/12/2008.
>Is it normal????
The leap is announced at the beginning of the month to make sure that all
ntp clients know about it. It always occurs at the...no more leap seconds?
Found this on Slashdot . Seems that some people want to get rid of
leap seconds .
Some excerpts that I found interesting (I like the last paragraph,
which is the last one in the story):
Because the moon's gravity has been slowing down the Earth, it
takes slightly longer than 24 hours for the world to rotate
completely on its axis. The difference is tiny, but every few
years a group that helps regulate global timekeeping, the
International Earth Rotation and Reference Systems Service, tells
governments, telecom companies, satellite operators and other...about leap second
I'm sorry my poor english.
I have a question about the specification of solaris, irix, hp-ux in
Our system has a time server which derives time and leap second
information from GPS. So time server supports leap second. Each UNIX
machine uses ntpd, but its operating system does not support leap second
in its configuration.
If leap second is inserted, how does each OS display its system clock
around leap second? I wonder if they display 58, 59, 59, 0, 1.... or 58,
59, 0, 0, 1....or go on normaly with one second difference and will be
adjusted after a few minutes.
tha...About the leap second
I have a question about the leap second.
In case of inserting a leap second,I see the figure
which repeats 00:00:00 twice on the P.79 of RFC1305.
However,NTPD4.2.0 repeats 23:59:59 twice.
Where dose this difference come from?
Just the difference of implementation? or the trouble on NTPD?
I am working with NTPD4.2.0 on FreeBSD4.9.
Please see the executive summary on leap seconds on the NTP project page
linked from www.ntp.org.
Yoshinobu Onozuka wrote:
> I have a question about the leap second.
> In case of insertin...Leap seconds
Talking of leap seconds, I see not indication here from any of my
servers, or their peers, of a leap-second, which is as it should be.
Checking reminded me that I did write a simple program with which you
can check your own NTP PCs, and it can be downloaded here:
David Taylor <email@example.com> writes:
>Talking of leap seconds, I see not indication here from any of my
>servers, or their peers, of a leap-second, which is as it should be. ...Leap second
AD 2005 will get an inserted leap second at 2005-12-31 23:59:60.
Obviously, this will affect systems that track (true) UTC time.
David R Tribble wrote:
> AD 2005 will get an inserted leap second at 2005-12-31 23:59:60.
> Obviously, this will affect systems that track (true) UTC time.
And those TV programs that count down the seconds to midnight
at New Year's...
On 26 Jul 2005 20:50:45 -0700,
Old Wolf <oldwo...Re: [ace-users] [ace-bugs] [asnmp]: [agent PDU receiving bug]
Thanks for using the PRF form. Wouldn't your change result in a possible
2650 AC Berkel en Rodenrijs
www.theaceorb.nl / www.remedy.nl
*** Integrated compile and test statistics see
*** Commercial service and support for ACE/TAO/CIAO ***
*** See http://www.theaceorb.nl/en/support.html ***
"Artem Nikitin" <firstname.lastname@example.org> wrote in message
news:<email@example.com...Re: [ace-users] [ace-bugs] [asnmp]: [agent PDU receiving bug] #2
> >Thanks for using the PRF form. Wouldn't your change result in a possible
> >memory leak?
> Can you please explain what would cause a memory leak?
I read the code not correctly, you are right, there is not a leak, but I am
not sure about the change the reporter wants. What change is exactly needed?
Could you please provide us with a bit more information about your
>> >Thanks for using the PRF form. Wouldn't your change result in a possible
>> >memory lea...No leap second on Windows
There was no leap second on my Windows 2000 Server NTP 4.2.0a systems
(3 servers). All servers are now <off> by 1 second after 23:59:60 UTC.
And a very strange behaviour - STEP correction does not work !
I'm not alone ! Browsing around I saw many time servers with the same
problem (including one in the the *.gov domain). And I supose there is
no Windows OS around there.
Maybe we could see the statistics from pool.ntp.org project - it seems
to be very interesting.
For sure, there is a lot of work to do here !
...Spurious leap second
Just for interest, one of my PCs started going wild on its timekeeping
just after midnight. It seems that one or more of the servers it was
synched to has sent leap-second announcements for 2007-Oct-01. Having
inserted the leap-second, the time keeping oscillated from the correct
second to the sprurious second, and a very high value became set in the
drift file (494 instead of about -70). I don't know which server caused
this (possibly in the pool). Stopping NTP, resetting the drift file value
to -72, and restarting NTP seems to have fixed the problem, and none of
the ...leap second happens on...
....on June 30th/July 1st transition, so we'll have:
June 30th 23:59:59
June 30th 23:59:60
July 1st 00:00:00
The question is: does it happen at 00:00:00 UTC (so it must be shifted
ahead/behind depending on the timezone) or, by convention, it happens at
00:00:00 at the local timezone?
I am quite sure the first is the right one, but a colleague of mine
asked me the question well enough to make a doubt arise in my brain :)
It happens at 23:59:59 UTC:
The bulletin states that the leap second is introduced...Leap second checking
As you may have heard, the economic slowdown of 2008 has caused the
earth to slow its course around the sun and they had to add an extra
second to 2008 before allowing 2009 to start.
While Microsoft's zune crashed at the tought of a leap year, there have
been a few reports of some unix systems crashing because of the leap second.
My VMS and os-X systems did not complain.
However, how can I check if those systems actually processed the leap
second and are in sync with the real time of 2009 ?
> INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS)...Leap second quirk
Two of my systems injected leap seconds at the end of Aug and Sep.
A couple of others didn't.
I thought I saw some discussion of this, but I can't find it. Has
anybody else seen this? Was I dreaming about seeing something here?
Is the bug in the Linux kernel for not waiting until December, or
should ntpd wait until December before telling the kernel?
I think both systems are/were running a recent ntp-dev on a reasonably recent
Linux (2.6) kernel.
I'm watching (noselect) both systems from a third box that didn't have
One did what I expect. It's clock was...the Leap second polka
Seems that the current ntp that comes in openbsd's port didn't like
the leap second at all. It is now ~1.5 hours after the leap second
and the time is royally messed up, showing a ~500ms offset from both
new and old UTC scales.
$ date -u
Sun Jan 1 01:26:17 GMT 2006
$ ntpq -p
remote refid st t when poll reach delay offset jitter
*capsicum.wsrcc. .GPS. 1 u 147 512 377 0.319 -524.66 78.777
+ntp.sonic.net 220.127.116.11 2 u 35 512 377 10.215 -559.59 42....mystery leap second
Can someone shed any light on what is going on here? Could
clock.sjc.he.net have jumped the gun and inserted a leap second a day
early? I've never seen it off by more than a millisecond or two
before and the offset of almost exactly a second is very suspicious,
especially since we are so close to a leap second event.
remote refid st t when poll reach delay offset jitter
*GPS_ONCORE(0) .GPS. 0 l 14 16 377 0.000 0.004 0.002
-bonnet.wsrcc.co 18.104.22.168 2 ...NTP and leap seconds
I'm sure this has been asnwered before but couldn't find the FAQ. I've
read the RFC and am still a bit confused.
Do NTP time signals include leap seconds?
I have a system running SNTP, do I need to add leap seconds to the
system clock after updating it with the timestamp SNTP sent?
Thanks in advance.
> I'm sure this has been asnwered before but couldn't find the FAQ. I've
> read the RFC and am still a bit confused.
> Do NTP time signals include leap seconds?
There is a specific two bit field for signaling leap seconds in NTP...Leap second hangover?
Two of my PCs have show a great NTP instability since 0000UTC this
morning, just like the events which happened on January 1st after the leap
second insertion. Please see:
At 06:00 UTC I restarted the NTP servers on those systems (Bacchus and
Stamsund), rewriting the ntp.drift file with a known good value for the
PCs in question.
Unfortunately, I didn't note which servers (in addition to my own simple
stratum 1 server - Pixie) those PC were clients to, but you may want to
look out for this behaviour in your own systems. Th...