Re: lease.openlogging.org is unreachable

[David Brownell]

> There's something in BK that refuses to work when it can't contact
> lease.openlogging.org, regardless of whether you just renewed the lease
> or not.  

For the record, I've seen this regularly too.  BK 3.2.3
was the last that showed it for me.  I'm glad to know
it wasn't just me ... but would be more glad if none
of us saw the problem!  :)

Last time I looked at the failure mode there was no issue
of network connectivity being missing, or even changing.
Host names on these systems don't change; neither do IP
addresses (though they're behind a NAT gateway).

>From memory (== may not be quite right), what I did was
"bk lease renew", then "bk pull" (or maybe clone; it failed
because it thought openlogging.org was playing hide/seek);
then "bk lease show" showed three (!!) current licences.

I've also had the "...unreachable" messages immediately after
renewing a lease, when cloning from a private tree but with
the network link down.  (That is, same as previous setup,
except the link is down.)  It's actually kind of annoying
to fail at the _end_ of a clone operation, leaving a tree
that doesn't seem recoverable, rather than at the start.

- Dave


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/