Skip to contentSkip to conversation

lease.openlogging.org is unreachable

DISCUSSION Chuck Ebbert 12 participants 30 messages Dec 25, 2004 – Dec 28, 2004

lore
Share & tools
lore
#0 lore raw

lease.openlogging.org is unreachable today.

So I guess I need to set up a cron job to renew my lease every minute/hour/day/whatever so I can actually download new kernel releases when they come out? I can't even examine the code I downloaded yesterday without that lease... Now that's what I call having my source code held hostage!

--
Please take it as a sign of my infinite respect for you, that I insist on you doing all the work.
-- Rusty Russell

#1 lore raw
Quoted 7 lines · Chuck Ebbert

lease.openlogging.org is unreachable today.

So I guess I need to set up a cron job to renew my lease every minute/hour/day/whatever so I can actually download new kernel releases when they come out? I can't even examine the code I downloaded yesterday without that lease... Now that's what I call having my source code held hostage!

The tar ball edition works perfectly 8)

#2 lore raw
Quoted 10 lines · Alan Cox
Quoted 7 lines · Chuck Ebbert

lease.openlogging.org is unreachable today.

So I guess I need to set up a cron job to renew my lease every minute/hour/day/whatever so I can actually download new kernel releases when they come out? I can't even examine the code I downloaded yesterday without that lease... Now that's what I call having my source code held hostage!

The tar ball edition works perfectly 8)

And a very Merry Christmas to you too Alan. You're welcome for all that BK has done for you and the kernel effort, always a pleasure to work with such polite people.

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#3 lore raw

bkcvs seems to have stale data [was Re: lease.openlogging.org is unreachable]

Hi!

Quoted 8 lines
Quoted 8 lines
Quoted 7 lines

lease.openlogging.org is unreachable today.

So I guess I need to set up a cron job to renew my lease every minute/hour/day/whatever so I can actually download new kernel releases when they come out? I can't even examine the code I downloaded yesterday without that lease... Now that's what I call having my source code held hostage!

Quoted 5 lines
Quoted 1 line

The tar ball edition works perfectly 8)

And a very Merry Christmas to you too Alan. You're welcome for all that BK has done for you and the kernel effort, always a pleasure to work with such polite people.

:-)

Is something wrong with bkcvs? 2.6.10 was released 40 hours ago, but I still see -rc3 when I update... I'm doing

time rsync -zav --delete rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.5 .

and cvs update.
Pavel

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
#4 lore raw

Re: bkcvs seems to have stale data [was Re: lease.openlogging.org is unreachable]

Quoted 2 lines · Pavel Machek

Is something wrong with bkcvs? 2.6.10 was released 40 hours ago, but I still see -rc3 when I update... I'm doing

There is nothing wrong on our end, the conversion happened and was pushed to master.kernel.org about 30 hours ago as part of the normal nightly update.

I logged into to master.kernel.org and checked:

lm@hera:/pub/scm/linux/kernel/bkcvs/linux-2.5(0)$ grep v2.6.10 ChangeSet,v
        v2_6_10:1.24782
	v2_6_10-rc3:1.24616
	v2_6_10-rc2:1.24188
	v2_6_10-rc1:1.23259
Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#5 lore raw
In reply to Chuck Ebbert
Quoted 1 line · Chuck Ebbert

lease.openlogging.org is unreachable today.

Yup it is, I'm trying to reboot it remotely but it doesn't seem to want to come up. I'll go in and figure it out, it will be about 30 minutes before I can get there though.

Quoted 5 lines

So I guess I need to set up a cron job to renew my lease every minute/hour/day/whatever so I can actually download new kernel releases when they come out? I can't even examine the code I downloaded yesterday without that lease... Now that's what I call having my source code held hostage!

We'll put an offsite backup in place so it will take two failures to cause you a problem.

In general the leases are good for 30 days so only a few people should be effected by this.

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#6 lore raw

The interesting thing is that the code already has a backup in it and I just checked that code path and it works.

Has anyone else been shut down because of lease.openlogging.org being down and if so what version of BK were you running please?

It is true that both servers are at our offices so if the network had been down you would have been out of luck. We'll create some more backups and scatter them around the US, that's no problem. But if the logic in the code to get them is busted then we need to fix that.

Things should be stabilized now, the machine went up and down a few times after my last "it's OK mail", it turned out we had a dieing ethernet card; it's been replaced and we seem stable now.

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#7 lore raw
Quoted 8 lines · Larry McVoy

The interesting thing is that the code already has a backup in it and I just checked that code path and it works.

Has anyone else been shut down because of lease.openlogging.org being down and if so what version of BK were you running please?

It is true that both servers are at our offices so if the network had been down you would have been out of luck.

I've been bitten by that one, as I occasionally work off-line. Is there some way I can make BK renew the leases a week or so before they expire?

It would also be nice if a simple read-only 'get' were allowed without a lease at all.

Signature · 2 lines
Måns Rullgård
[email protected]
#8 lore raw
Quoted 3 lines · M?ns Rullg?rd

I've been bitten by that one, as I occasionally work off-line. Is there some way I can make BK renew the leases a week or so before they expire?

In theory, we do that already. By you can always do a "bk lease renew" and that will get you a new lease. "bk lease show" will show you your lease.

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#9 lore raw
Quoted 8 lines · Larry McVoy
Quoted 3 lines · M?ns Rullg?rd

I've been bitten by that one, as I occasionally work off-line. Is there some way I can make BK renew the leases a week or so before they expire?

In theory, we do that already. By you can always do a "bk lease renew" and that will get you a new lease. "bk lease show" will show you your lease.

Looking closer, the problem is that my hostname keeps changing, depending on which network the laptop is on, if any. I guess the simple solution is to remember to renew the lease for the no-net hostname before going offline.

Signature · 2 lines
Måns Rullgård
[email protected]
#10 lore raw
Quoted 7 lines · M?ns Rullg?rd
Quoted 5 lines · Larry McVoy
Quoted 3 lines · M?ns Rullg?rd

I've been bitten by that one, as I occasionally work off-line. Is there some way I can make BK renew the leases a week or so before they expire?

Quoted 8 lines
Quoted 3 lines

In theory, we do that already. By you can always do a "bk lease renew" and that will get you a new lease. "bk lease show" will show you your lease.

Looking closer, the problem is that my hostname keeps changing, depending on which network the laptop is on, if any. I guess the simple solution is to remember to renew the lease for the no-net hostname before going offline.

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#11 lore raw
Quoted 4 lines · Larry McVoy

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

Nothing even moderately portable like this exists. The best approximation imaginable would be starting to collect MAC address id's... But thats of corse the wrong protocol layer.

#12 lore raw
In reply to Larry McVoy
Quoted 3 lines · Larry McVoy

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

libuuid does that on straight statistical probability - what properties do you want your id to have ?

#13 lore raw
Quoted 8 lines · Alan Cox
Quoted 3 lines · Larry McVoy

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

libuuid does that on straight statistical probability - what properties do you want your id to have ?

Simply storing the first hostname used in a dot file for subsequent reuse on client side, would be even easier I guess. That would be basically the same strategy as used by ssh with regard to host keys. It wouldn't even perhaps make protocol changes necessary. But still not a perfect solution... (Remember the times you have delete something from .ssh/known_hosts).

#14 lore raw

* Martin Dalecki:

Quoted 2 lines

Simply storing the first hostname used in a dot file for subsequent reuse on client side, would be even easier I guess.

You mean localhost.localdomain? 8-)

#15 lore raw
Quoted 6 lines · Florian Weimer

* Martin Dalecki:

Quoted 2 lines

Simply storing the first hostname used in a dot file for subsequent reuse on client side, would be even easier I guess.

You mean localhost.localdomain? 8-)

No the first value that worked in the whole setup of course. And I said it clearly that would be just a workaround because uniqueness can be established in the easiest way on the side of the part which is interested in the persistency - the server peer not the client. "Simple" http servers do it by sending cookies around. Other call it "tokens".

#16 lore raw
Quoted 4 lines · Martin Dalecki

No the first value that worked in the whole setup of course. And I said it clearly that would be just a workaround because uniqueness can be established in the easiest way on the side of the part which is interested in the persistency - the server peer not the client.

actually, the bk lease server could give out id's and those could be caches in ~/.bk<whatever> --- server side it could be a counter that you just xor with some s3kr1t value and then blind using a hash or cryto-function, something good-enough (statistically unlikely to break) is all that is required, it doesn't have to be perfect surely?

#17 lore raw
Quoted 7 lines · Chris Wedgwood
Quoted 4 lines · Martin Dalecki

No the first value that worked in the whole setup of course. And I said it clearly that would be just a workaround because uniqueness can be established in the easiest way on the side of the part which is interested in the persistency - the server peer not the client.

Quoted 6 lines

actually, the bk lease server could give out id's and those could be caches in ~/.bk<whatever> --- server side it could be a counter that you just xor with some s3kr1t value and then blind using a hash or cryto-function, something good-enough (statistically unlikely to break) is all that is required, it doesn't have to be perfect surely?

Right that's precisely what's called a cookie or token. But it would involve a change in the on-wire protocol.

#18 lore raw
In reply to Larry McVoy

Larry McVoy <[email protected]> said:

[...]

Quoted 3 lines

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

MAC of eth0?

Signature · 4 lines
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
#19 lore raw
Quoted 1 line · Horst von Brand

MAC of eth0?

that changes for people (most commonly laptops)

#20 lore raw
In reply to Horst von Brand
Quoted 9 lines · Horst von Brand

Larry McVoy <[email protected]> said:

[...]

Quoted 3 lines

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

MAC of eth0?

ippp0?

#21 lore raw
In reply to Horst von Brand
Quoted 5 lines · Horst von Brand
Quoted 3 lines

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

MAC of eth0?

As others have pointed out that won't work.

I'm trying to remember why we get leases on a per host basis and I think it is for a simple reason, NFS. We update the leases in your home directory and if your home directory is nfs mounted then we can corrupt the leases file due to races (yes, we saw this all the time when we had one leases file). So we stick the leases for a particular host in that host's file.

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#22 lore raw
Quoted 11 lines · Larry McVoy
Quoted 5 lines · Horst von Brand
Quoted 3 lines

The other answer, which I'm happy to consider, is to come up with a unique id on a per host basis and use that for the leases. That's not a fun task, does anyone have code (BSD license please) which does that?

MAC of eth0?

As others have pointed out that won't work.

I'm trying to remember why we get leases on a per host basis and I think it is for a simple reason, NFS.

Citing from: http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html

"NFS fails at the goal of allowing a computer to access files over a network as if they were on a local disk. In many ways, NFS comes close to the objective, and in certain circumstances (detailed later), this is acceptable. However, the subtle differences can cause subtle bugs and greater system issues. The widespread misconception about the compatibility and transparency of NFS means that it is often used inappropriately, and often put into production when better, more acceptable solutions exist."

I don't know of a proper solution, other then writing in big letters in the documentation about the circumstances under which you can shoot yourself in the feet.

Where is NFSv4?

#23 lore raw
Quoted 12 lines · Martin Dalecki

Citing from:
http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html

"NFS fails at the goal of allowing a computer to access files over a network as if they were on a local disk. In many ways, NFS comes close to the objective, and in certain circumstances (detailed later), this is acceptable. However, the subtle differences can cause subtle bugs and greater system issues. The widespread misconception about the compatibility and transparency of NFS means that it is often used inappropriately, and often put into production when better, more acceptable solutions exist."

Quoted 4 lines

I don't know of a proper solution, other then writing in big letters in the documentation about the circumstances under which you can shoot yourself in
the feet.

And that, my friends, is the difference between a project which is a hobby and a project which is a product. We don't have the option of saying "this doesn't work".

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
#24 lore raw
Quoted 10 lines · Larry McVoy
Quoted 5 lines · Martin Dalecki

I don't know of a proper solution, other then writing in big letters in the documentation about the circumstances under which you can shoot yourself in
the feet.

And that, my friends, is the difference between a project which is a hobby and a project which is a product. We don't have the option of saying "this doesn't work".

Fully agreed. And those are the reasons why the completely non professional solutions, which I never saw in deployment of course...
like ... for example the pure hobby-student-project ClearCase are going to the extent of requiring you to run their own networked filesystem if running on Linux. They do it simply out of fun and for educational purposes and because they where to dumb to find much easier solution which are out there ready and waiting. They simply don't have to deal with something as exceptional as customers. They love to spend about 10 man years to develop a reliable networked filesystem which is OS minor version specific like burning money for heat...

OK I was just kidding. ;-)

#25 lore raw
Quoted 3 lines · Martin Dalecki

for example the pure hobby-student-project ClearCase are going to the extent of requiring you to run their own networked filesystem if running on Linux.

WTF are talking about? MVFS is required *everywhere* you want to use dynamic views... solaris, aix, hpux, windows, and *yes* LINUX.

And MVFS is not 100% filesystem -- it's part fs, part db, part proxy, ... (it's just weird, but I like it.)

--Ricky

#26 lore raw
In reply to Larry McVoy
Quoted 3 lines · In article <[email protected]> you wrote:

And that, my friends, is the difference between a project which is a hobby and a project which is a product. We don't have the option of saying "this doesn't work".

Thats why more and more commercial solutions do not use licensing services or dongles anymore. It just introduces to much failure possibilities.

Greetings
Bernd

#27 lore raw
In reply to Martin Dalecki

On Mon, 27 Dec 2004, Martin Dalecki wrote:
...

Quoted 6 lines

I don't know of a proper solution, other then writing in big letters in the documentation about the circumstances under which you can shoot yourself in
the feet.

Where is NFSv4?

The problem is the protocol, it's the fact that the directory is shared among more than one machine. It's the false assumption that a given location is unique to just one machine. Yes, I've fallen into this mess too. (And I wasn't using NFS, btw.)

--Ricky

#28 lore raw

In reply to Larry McVoy
Quoted 2 lines · Larry McVoy

Has anyone else been shut down because of lease.openlogging.org being down and if so what version of BK were you running please?

Yes, I had bk pull and bk export fail for me yesterday. If I did a bk pull it would sit there for a while and then put up a window saying it couldn't get to lease.openlogging.org. If I clicked OK, after a while another window would come up with a similar message (but I didn't read it carefully).

Quoted 2 lines

It is true that both servers are at our offices so if the network had been down you would have been out of luck.

I did a traceroute and it looked like a network problem. From memory it stopped after about 10 hops, and it seems to be 17 hops to openlogging.org from here now.

My setup is possibly a little unusual, and may be causing problems for your lease code: I have my BK repos on a firewire-attached disk, which I move from machine to machine - specifically, it commutes between home and work with me.

Paul.

#29 lore raw
In reply to Chuck Ebbert
Quoted 7 lines · Chuck Ebbert

lease.openlogging.org is unreachable today.

So I guess I need to set up a cron job to renew my lease every minute/hour/day/whatever so I can actually download new kernel releases when they come out? I can't even examine the code I downloaded yesterday without that lease... Now that's what I call having my source code held hostage!

It's back up. Go to a repo and say "bk lease renew" and you should be all set.

Signature · 2 lines
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com