[BK] status

[BK] status

[Larry McVoy]

The various BK machines we host are in at their new location and seem
to have stabilized (famous last words, every time I say something like
that something crashes).  kernel.bkbits.net, which is a shell account
machine for kernel developers, bk users or not, is not up yet, we've
had problems with that machine due to cooling and because we have a
much larger machine room we will be moving the guts of that machine to
a higher volume box to get better cooling.  ETA on that should be today.

We're moving towards remote control of the critical machines.  The machines
are already UPSed but they don't have serial consoles and/or remote power.
I've ordered a Sentry R2000 (model 203-0-1) which is supposed to be a pretty
nice remote power device.  We'll get serial consoles on the machines so 
that if they crash we can get the oops message and get some debugging help
(a couple of people, Bill Irwin in particular, went out of their way to
offer to help out with the the debugging.  I mention it only because it
was nice to that kind of friendly offer and I'm grateful).

We are currently on one T1 line, we moved one of the two to the new office
and one is at the old office so we had some overlap in case something
went horribly wrong.  It's clear that one T1 line isn't enough, you've
been keeping that T1 pretty full.  We'll be back up to two in a few
weeks.

Other than the up/down problems, have any of you noticed bkbits being 
slower since the move (which happened Friday or Saturday, it's sort of
a blur)?

Oregon State's open source lab has repeated their offer to take over hosting
bkbits.net and we may take them up on that if we can ever work out the 
logistics and you need the bandwidth.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

Re: [BK] status

[Sam Ravnborg]

> 
> Other than the up/down problems, have any of you noticed bkbits being 
> slower since the move (which happened Friday or Saturday, it's sort of
> a blur)?

I see no slowdown.
But this morning (something like 8 hours ago) I could not pull from
linux.bkbits.net - it just silently exited.

When trying to access www.bkbits.net I got a full list of projects,
but when I tried to access one of the projects (when it starts using port
8080) I after a while got a message that "I had not purchased BKWeb" or
something similar. I took this as overload but now you ask I report it.

	Sam

Re: [BK] status

[Larry McVoy]

On Tue, Apr 13, 2004 at 05:36:32PM +0200, Sam Ravnborg wrote:
> > 
> > Other than the up/down problems, have any of you noticed bkbits being 
> > slower since the move (which happened Friday or Saturday, it's sort of
> > a blur)?
> 
> I see no slowdown.
> But this morning (something like 8 hours ago) I could not pull from
> linux.bkbits.net - it just silently exited.
> 
> When trying to access www.bkbits.net I got a full list of projects,
> but when I tried to access one of the projects (when it starts using port
> 8080) I after a while got a message that "I had not purchased BKWeb" or
> something similar. I took this as overload but now you ask I report it.

All of that is related to the DNS screwup, it should all be back to normal now.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

Re: [BK] status

[Andy Isaacson]

On Tue, Apr 13, 2004 at 05:36:32PM +0200, Sam Ravnborg wrote:
> > Other than the up/down problems, have any of you noticed bkbits being 
> > slower since the move (which happened Friday or Saturday, it's sort of
> > a blur)?
> 
> I see no slowdown.
> But this morning (something like 8 hours ago) I could not pull from
> linux.bkbits.net - it just silently exited.
> 
> When trying to access www.bkbits.net I got a full list of projects,
> but when I tried to access one of the projects (when it starts using port
> 8080) I after a while got a message that "I had not purchased BKWeb" or
> something similar. I took this as overload but now you ask I report it.

Both problems due to an internal network error, which should be fixed
now.  Thanks for the report; please let us know if you see any further
problems.

-andy