[Box-Admins] RE: [squeak-dev] http://build.squeak.org/ down?

[Levente Uzonyi]

I guess this belongs more to the box-admins list, so I moved it here.
I killed 45 runaway processes, and found that jenkins is down.

On Thu, 16 Oct 2014, Frank Shearar wrote:

> The VM processes are apt to leak for reasons unknown: Maybe Jenkins can't track the shell games I have to try play with Squeak. Suggestions for
> improvement actively sought.

I think it would be worth restarting jenkins, but disabling all but one of 
these VM-related processes until this is fixed.
It would help if you could give us some pointers about what is wrong, and 
where to start looking around.


Levente

> 
> __________________________________________________________________________________________________________________________________________________
> From: David T. Lewis
> Sent: ‎15/‎10/‎2014 01:52
> To: The general-purpose Squeak developers list
> Subject: Re: [squeak-dev] http://build.squeak.org/ down?
> 
> > On Tue, Oct 14, 2014 at 08:37:56PM -0400, Chris Cunnington wrote:
> > > On Oct 14, 2014, at 8:14 PM, Dale Henrichs <dale.henrichs at gemtalksystems.com> wrote:
> > >
> > > Getting a 503 at the moment ...
> >
> > Yes. I noticed this morning that Chris Muller has started a new SS process
> > on box4. And the usual address [1] is routing to the default when there is
> > no service on box2. I conclude that he is moving SS to box4 and is in-between
> > boxes. I would imagine that the process on box4 needs to be announced by
> > routing the dns on box2 to its new location [2].
> >
> 
> No this is nothing to do with anything on box4. The build.squeak.org service
> is on box3 along with squeaksource.com. Squeaksource is fine, but Jenkins is
> not. There are currently about 30 Squeak VMs of various flavors running under
> the Jenkins uid. Ick. I'll try to restart the Jenkins service and see if I can
> clear out the mess.
> 
> Dave
> 
> 
> 
>