Re: hard crash on leap second

On 2009-01-01 21:26:07 -0700, Paul E Condon wrote: > On Fri, Jan 02, 2009 at 12:23:18AM +0100, Vincent Lefevre wrote: > > I agree that sudden jumps or extended periods of stasis are bad. > > However this is how leap seconds currently work (it would have been > > better to have a continuous synchron

Re: hard crash on leap second

On Thu, 01 Jan 2009, Paul Cartwright wrote: > > What time server(s) do you use? > ntp.conf shows: > server 0.pool.ntp.org > server 1.pool.ntp.org > server 2.pool.ntp.org > server 0.debian.pool.ntp.org > server 1.debian.pool.ntp.org > server 2.debian.pool.ntp.org > server 3.debian.pool.ntp.org > ser

Re: hard crash on leap second

Hi, Ron Johnson wrote: > On 01/01/09 18:09, Yannick Patois wrote: >> My machine also crashed precisely at 0:59:59 - french time - (screen >> froze, KDE bar displaying this time). > What time sync method do you use? ntpdate, openntpd or ntp? I use ntp from debian, deb versionned as 1:4.2.4p4+dfsg

Re: hard crash on leap second

* Travis Crump: > I had a hard crash of my lenny system precisely when the leap second was > added. While X has flaked in the past, I've never had a hard crash > before. I have no other evidence they were related, but I wasn't doing > anything unusual at the time. Any ideas? Do you run Oracle

Re: hard crash on leap second

On Thu January 1 2009, Douglas A. Tutty wrote: > I was running openntpd and since the leap second switched to ntp. > > > I wonder if there is correlation between those of us who had a problem > and those of us who were running openntpd at the time? as I found out I WAS running openntpd. I didn't

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 20:31:50 -0500, Paul Cartwright (a...@pcartwright.com) wrote: > On Thu January 1 2009, Paul Cartwright wrote: > > On Thu January 1 2009, Bob Cox wrote: > > > > no, I have an always-on DSL connection. > > > > Westell modem->linksys router->PC. > > > > > > Hi Paul - what's

Re: hard crash on leap second

We're getting a little OT here, but let's carry on. It's fun ... On Fri, Jan 02, 2009 at 12:23:18AM +0100, Vincent Lefevre wrote: > On 2009-01-01 11:58:14 -0700, Paul E Condon wrote: > > IMHO, chrony's current behavior is already 'correct'. To me, it is > > far more important that the reported tim

Re: hard crash on leap second

On 01/01/09 18:09, Yannick Patois wrote: Hi, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard crash before. I have no other evidence they were related, but I wasn't doing anything unusual

Re: hard crash on leap second

On Friday 02 January 2009 03:26:15 Douglas A. Tutty wrote: > I wonder if there is correlation between those of us who had a problem > and those of us who were running openntpd at the time? > > Doug. I will not help in solving the problem, but, running Lenny, my mail did not work last night. Wit

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 08:04:01PM -0600, Dennis Wicks wrote: > Yannick Patois wrote the following on 01/01/2009 06:09 PM: > Well, just for another data point, I have 6 machines running > lenny at various levels of being up-to-date and none of them > crashed. > > I am running ntp 1:4.2.4p4+dfs

Re: hard crash on leap second

Yannick Patois wrote the following on 01/01/2009 06:09 PM: Hi, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard crash before. I have no other evidence they were related, but I wasn't doing

Re: hard crash on leap second

Hi, Travis Crump wrote: > I had a hard crash of my lenny system precisely when the leap second was > added. While X has flaked in the past, I've never had a hard crash > before. I have no other evidence they were related, but I wasn't doing > anything unusual at the time. Any ideas? Same behav

Re: hard crash on leap second

On Thu January 1 2009, Paul Cartwright wrote: > On Thu January 1 2009, Bob Cox wrote: > > > no, I have an always-on DSL connection. > > > Westell modem->linksys router->PC. > > > > Hi Paul - what's the output from ntpq -p please? > and then: # ntpq -p remote refid st t when pol

Re: hard crash on leap second

On Thu January 1 2009, Bob Cox wrote: > > no, I have an always-on DSL connection. > > Westell modem->linksys router->PC. > > Hi Paul - what's the output from ntpq -p please? installed ntp # /etc/init.d/ntp restart Stopping NTP server: ntpd. Starting NTP server: ntpd. paulandcilla:/etc# ps -ef|gre

Re: hard crash on leap second

* Paul Cartwright [2009 Jan 01 19:18 -0600]: > The following packages are BROKEN: > openntpd > The following NEW packages will be installed: > ntp > 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > Need to get 434kB of archives. After unpacking 1065kB will be used. >

Re: hard crash on leap second

On Thu January 1 2009, Bob Cox wrote: > > no, I have an always-on DSL connection. > > Westell modem->linksys router->PC. > > Hi Paul - what's the output from ntpq -p please? paulandcilla:/etc# ntpq -p bash: ntpq: command not found ... ok, so apt-cache search ntpq says hobbit-plugins that didn't c

Re: hard crash on leap second

On 2009-01-01 11:58:14 -0700, Paul E Condon wrote: > IMHO, chrony's current behavior is already 'correct'. To me, it is > far more important that the reported time is always increasing than > that it quickly settles into synchronism with a source that exhibits > sudden jumps or extended periods of

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 11:56:29AM -0600, John Hasler wrote: > ... > Chrony does not currently support leap seconds [1]. When the leap occurred > it lost synch, chose a different server, and then pulled back in. IMHO, chrony's current behavior is already 'correct'. To me, it is far more importan

Re: Re: hard crash on leap second

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > OoO En cette nuit nuageuse du jeudi 01 janvier 2009, vers 01:25, Travis > Crump disait : > >> I had a hard crash of my lenny system precisely when the leap second was >> added. While X has flaked in the past, I've never had a hard crash >> before

Re: hard crash on leap second

Paul E Condon writes: > You and I appear to be the only people posting to this thread who use > chrony. I run it just the way you set it up in the package. (except that > I'm always connected to the Internet, and edited out the 'offline' from > the server spec.s) Because of this long thread, and e

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 09:05:55 -0500, Paul Cartwright (a...@pcartwright.com) wrote: > On Thu January 1 2009, Bob Cox wrote: > > > Dec 31 19:59:46 paulandcilla ntpd[3701]: clock is now unsynced > > > Dec 31 20:07:27 paulandcilla ntpd[3701]: clock is now synced > > > Dec 31 20:56:19 paulandcilla

Re: hard crash on leap second

On Thu January 1 2009, Ron Johnson wrote: > > no, I have an always-on DSL connection. > > Westell modem->linksys router->PC. > > What time server(s) do you use? ntp.conf shows: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server 0.debian.pool.ntp.org server 1.debian.pool.ntp.or

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 07:44:07AM -0600, John Hasler wrote: > I wrote: > > Debian has time servers: > > > > 0.debian.pool.ntp.org > > 1.debian.pool.ntp.org > > 2.debian.pool.ntp.org > > 3.debian.pool.ntp.org > > > I prefer to use reliable sources. Also, as Chrony maintainer I feel that I > sho

Re: hard crash on leap second

On 01/01/09 08:05, Paul Cartwright wrote: On Thu January 1 2009, Bob Cox wrote: Dec 31 19:59:46 paulandcilla ntpd[3701]: clock is now unsynced Dec 31 20:07:27 paulandcilla ntpd[3701]: clock is now synced Dec 31 20:56:19 paulandcilla ntpd[3700]: adjusting local clock by -0.159575s Are you on a d

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 07:44:07 -0600, John Hasler (jhas...@debian.org) wrote: > I wrote: > > Debian has time servers: > > > > 0.debian.pool.ntp.org > > 1.debian.pool.ntp.org > > 2.debian.pool.ntp.org > > 3.debian.pool.ntp.org > > Bob Cox writes: > > These are all aliases for 0.pool.ntp.org, 1

Re: hard crash on leap second

On Thu January 1 2009, Bob Cox wrote: > > Dec 31 19:59:46 paulandcilla ntpd[3701]: clock is now unsynced > > Dec 31 20:07:27 paulandcilla ntpd[3701]: clock is now synced > > Dec 31 20:56:19 paulandcilla ntpd[3700]: adjusting local clock by > > -0.159575s > > Are you on a dial-up connection Paul?  I

Re: hard crash on leap second

On 01/01/09 07:07, John Hasler wrote: [snip] That only matters if you have a particular need to synchronise precisely with your ISP. Or want to put less stress on public time servers. (After all, I'm paying for time.cox.net... And ISP servers are often unreliable. Say wha

Re: hard crash on leap second

I wrote: > Debian has time servers: > > 0.debian.pool.ntp.org > 1.debian.pool.ntp.org > 2.debian.pool.ntp.org > 3.debian.pool.ntp.org Bob Cox writes: > These are all aliases for 0.pool.ntp.org, 1.pool.ntp.org and so on. That is how Debian and ntp.org have set it up. It could change. See

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 12:35:33PM -, Cameron Hutchison wrote: > Travis Crump writes: > > >I had a hard crash of my lenny system precisely when the leap second was > >added. While X has flaked in the past, I've never had a hard crash > >before. I have no other evidence they were related, bu

Re: hard crash on leap second

Ron Johnson writes: > See if your ISP has a timeserver. I wrote: > Debian has time servers: > > 0.debian.pool.ntp.org > 1.debian.pool.ntp.org > 2.debian.pool.ntp.org > 3.debian.pool.ntp.org Ron Johnson writes: > Right, but your ISP's time server is "closer". That only matters if you have a part

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 08:01:00 -0500, Paul Cartwright (a...@pcartwright.com) wrote: > On Wed December 31 2008, Ken Irving wrote: > > > Dec 31 18:03:01 haggis ntpdate[9521]: step time server 68.0.14.76 offset > > > -0.562385 sec > > > > I see the same as that in a machine running ntpdate.  I us

Re: hard crash on leap second

On Thu January 1 2009, Vincent Lefevre wrote: > Since it's a kernel message, it's at least in /var/log/kern.log, and > I have that one too: > > Jan  1 00:59:59 ay kernel: [220491.482702] Clock: inserting leap second > 23:59:60 UTC > > But I hadn't any crash here. I grepped for 59:59 in all logs an

Re: hard crash on leap second

On Wed December 31 2008, Ken Irving wrote: > > Dec 31 18:03:01 haggis ntpdate[9521]: step time server 68.0.14.76 offset > > -0.562385 sec > > I see the same as that in a machine running ntpdate.  I used to mainly use > ntpdate, but saw lots of references (though I have no citations to offer) > reco

Re: hard crash on leap second

Travis Crump writes: >I had a hard crash of my lenny system precisely when the leap second was >added. While X has flaked in the past, I've never had a hard crash >before. I have no other evidence they were related, but I wasn't doing >anything unusual at the time. Any ideas? I have a lenny a

Re: hard crash on leap second

On 2008-12-31 20:45:05 -0600, Nate Bargmann wrote: > Until earlier this year I was running ntpdate as well, but found > differences of a few to a few tens of seconds between my machines. > After installing ntp, they are in sync with each other as expected. Yes, IIRC if the difference is too large

Re: hard crash on leap second

On 2008-12-31 19:10:22 -0600, Ron Johnson wrote: > On 12/31/08 18:49, Justin Piszcz wrote: > [snip] >> >> System Events >> =-=-=-=-=-=-= >> Dec 31 18:59:59 p34 kernel: [38776.165550] Clock: inserting leap second >> 23:59:60 UTC > > Why don't I see this in my syslog or dmesg? Since it's a kernel m

Re: hard crash on leap second

On 01/01/09 00:25:25, Travis Crump wrote: > > I had a hard crash of my lenny system precisely when the leap second > was added. While X has flaked in the past, I've never had a hard > crash before. I have no other evidence they were related, but I > wasn't doing anything unusual at the time.

Re: hard crash on leap second

On Thu, Jan 01, 2009 at 10:22:52 +, Bob Cox (debian-u...@lists.bobcox.com) wrote: > Yes, that third listed peer does have an usual domain name ;-) Oops. Fourth. -- Bob Cox. Stoke Gifford, near Bristol, UK. Please reply to the list only. Do NOT send copies directly to me. Debian on the

Re: hard crash on leap second

On Wed, Dec 31, 2008 at 21:59:33 -0600, John Hasler (jhas...@debian.org) wrote: > Ron Johnson writes: > > See if your ISP has a timeserver. > > Debian has time servers: > > 0.debian.pool.ntp.org > 1.debian.pool.ntp.org > 2.debian.pool.ntp.org > 3.debian.pool.ntp.org These are all aliases for

Re: hard crash on leap second

OoO En cette nuit nuageuse du jeudi 01 janvier 2009, vers 01:25, Travis Crump disait : > I had a hard crash of my lenny system precisely when the leap second was > added. While X has flaked in the past, I've never had a hard crash > before. I have no other evidence they were related, but I was

Re: hard crash on leap second

On 12/31/08 21:59, John Hasler wrote: Ron Johnson writes: See if your ISP has a timeserver. Debian has time servers: 0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org Right, but your ISP's time server is "closer". -- Ron Johnson, Jr. Jefferson LA USA

Re: hard crash on leap second

Ron Johnson writes: > See if your ISP has a timeserver. Debian has time servers: 0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble?

Re: hard crash on leap second

* Ken Irving [2008 Dec 31 20:41 -0600]: > I see the same as that in a machine running ntpdate. I used to mainly use > ntpdate, but saw lots of references (though I have no citations to offer) > recommending ntp over ntpdate, and find that it *just works" now when I set > up a machine. Until ear

Re: hard crash on leap second

On Wed, Dec 31, 2008 at 08:20:41PM -0600, Ron Johnson wrote: > On 12/31/08 20:05, Ken Irving wrote: >> On Wed, Dec 31, 2008 at 07:48:41PM -0600, Ron Johnson wrote: >>> On 12/31/08 19:19, Ken Irving wrote: On Wed, Dec 31, 2008 at 04:02:03PM -0900, Ken Irving wrote: > On Wed, Dec 31, 2008 at

Re: hard crash on leap second

* Ron Johnson [2008 Dec 31 19:13 -0600]: > On 12/31/08 18:49, Justin Piszcz wrote: > [snip] >> >> System Events >> =-=-=-=-=-=-= >> Dec 31 18:59:59 p34 kernel: [38776.165550] Clock: inserting leap second >> 23:59:60 UTC > > Why don't I see this in my syslog or dmesg? Dunno. It's in this machine

Re: hard crash on leap second

On 12/31/08 20:00, Douglas A. Tutty wrote: On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard crash before. I have no other evidence they were relate

Re: hard crash on leap second

On 12/31/08 20:05, Ken Irving wrote: On Wed, Dec 31, 2008 at 07:48:41PM -0600, Ron Johnson wrote: On 12/31/08 19:19, Ken Irving wrote: On Wed, Dec 31, 2008 at 04:02:03PM -0900, Ken Irving wrote: On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: I had a hard crash of my lenny syste

Re: hard crash on leap second

On Wed, Dec 31, 2008 at 07:48:41PM -0600, Ron Johnson wrote: > On 12/31/08 19:19, Ken Irving wrote: >> On Wed, Dec 31, 2008 at 04:02:03PM -0900, Ken Irving wrote: >>> On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap sec

Re: hard crash on leap second

On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: > I had a hard crash of my lenny system precisely when the leap second was > added. While X has flaked in the past, I've never had a hard crash > before. I have no other evidence they were related, but I wasn't doing > anything unusual

Re: hard crash on leap second

On 12/31/08 19:19, Ken Irving wrote: On Wed, Dec 31, 2008 at 04:02:03PM -0900, Ken Irving wrote: On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard c

Re: hard crash on leap second

On Wed, Dec 31, 2008 at 04:02:03PM -0900, Ken Irving wrote: > On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: > > > > I had a hard crash of my lenny system precisely when the leap second was > > added. While X has flaked in the past, I've never had a hard crash > > before. I have n

Re: hard crash on leap second

On 12/31/08 18:49, Justin Piszcz wrote: [snip] System Events =-=-=-=-=-=-= Dec 31 18:59:59 p34 kernel: [38776.165550] Clock: inserting leap second 23:59:60 UTC Why don't I see this in my syslog or dmesg? -- Ron Johnson, Jr. Jefferson LA USA I like my women like I like my coffee - purchased

Re: hard crash on leap second

On Wed, Dec 31, 2008 at 07:25:25PM -0500, Travis Crump wrote: > > I had a hard crash of my lenny system precisely when the leap second was > added. While X has flaked in the past, I've never had a hard crash > before. I have no other evidence they were related, but I wasn't doing > anything unus

Re: hard crash on leap second

On 12/31/08 18:25, Travis Crump wrote: I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard crash before. I have no other evidence they were related, but I wasn't doing anything unusual at the time. Any ideas?

Re: hard crash on leap second

On Wed, 31 Dec 2008 19:25:25 -0500 Travis Crump wrote: > I had a hard crash of my lenny system precisely when the leap second > was added. While X has flaked in the past, I've never had a hard > crash before. I have no other evidence they were related, but I > wasn't doing anything unusual at t

Re: hard crash on leap second

On Wed, 31 Dec 2008, Travis Crump wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I had a hard crash of my lenny system precisely when the leap second was added. While X has flaked in the past, I've never had a hard crash before. I have no other evidence they were related, but I wasn't