Getting a 503 at the moment ...
Dale |
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]. Chris
|
> On Tue, Oct 14, 2014 at 08:37:56PM -0400, Chris Cunnington wrote:
> > On Oct 14, 2014, at 8:14 PM, Dale Henrichs <[hidden email]> 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 |
Thanks guys! On Tue, Oct 14, 2014 at 5:52 PM, David T. Lewis <[hidden email]> wrote: > On Tue, Oct 14, 2014 at 08:37:56PM -0400, Chris Cunnington wrote: |
In reply to this post by David T. Lewis
On Tue, Oct 14, 2014 at 08:52:03PM -0400, David T. Lewis wrote:
> > On Tue, Oct 14, 2014 at 08:37:56PM -0400, Chris Cunnington wrote: > > > On Oct 14, 2014, at 8:14 PM, Dale Henrichs <[hidden email]> 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 > I killed 41 rogue VMs running under Jenkins, and restarted the service. It is now apparently working. Frank ... we need to clean this up. Seriously. Dave |
In reply to this post by David T. Lewis
Actually, I misread the question and saw what I wanted to see. The question was about build.squeak.org and I thought I saw trunk.squeak.org.
Seems to me that what I’m saying about trunk.squeak.org is still true: it has been shut down on its usual subdomain; and, a new process has appeared on box4. Looks to me like trunk development is halted for the moment. Chris
|
Chris,
I do not understand what you mean. If Chris Muller had wanted to make a change that affected our servers or the trunk development process, I am sure he would have cleared it with Levente and mentioned it on box-admins, as any of us would do if we were making such a change. Trunk development happens on source.squeak.org. The mirror of source.squeak.org that runs on http://box4.squeak.org:8888 with a Magma back end has been in service for a long time, and has been discussed on squeak-dev. As far as I am aware, nothing has changed on any of the outward facing boxes. So no, trunk development is not halted. The only thing that happened is that the Jenkins service melted down, and I restarted it. Dave On Tue, Oct 14, 2014 at 09:45:38PM -0400, Chris Cunnington wrote: > Actually, I misread the question and saw what I wanted to see. The question was about build.squeak.org <http://build.squeak.org/> and I thought I saw trunk.squeak.org <http://trunk.squeak.org/>. > Seems to me that what I???m saying about trunk.squeak.org <http://trunk.squeak.org/> is still true: it has been shut down on its usual subdomain; and, a new process has appeared on box4. > Looks to me like trunk development is halted for the moment. > > Chris > > > On Oct 14, 2014, at 8:52 PM, David T. Lewis <[hidden email]> wrote: > > > >> On Tue, Oct 14, 2014 at 08:37:56PM -0400, Chris Cunnington wrote: > >>> On Oct 14, 2014, at 8:14 PM, Dale Henrichs <[hidden email]> 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 > > > > > > |
You’re absolutely right, David.
Chris > On Oct 14, 2014, at 11:19 PM, David T. Lewis <[hidden email]> wrote: > > Chris, > > I do not understand what you mean. If Chris Muller had wanted to make a change > that affected our servers or the trunk development process, I am sure he would > have cleared it with Levente and mentioned it on box-admins, as any of us would > do if we were making such a change. > > Trunk development happens on source.squeak.org. The mirror of source.squeak.org > that runs on http://box4.squeak.org:8888 with a Magma back end has been in service > for a long time, and has been discussed on squeak-dev. As far as I am aware, > nothing has changed on any of the outward facing boxes. > > So no, trunk development is not halted. The only thing that happened is that > the Jenkins service melted down, and I restarted it. > > Dave > > > On Tue, Oct 14, 2014 at 09:45:38PM -0400, Chris Cunnington wrote: >> Actually, I misread the question and saw what I wanted to see. The question was about build.squeak.org <http://build.squeak.org/> and I thought I saw trunk.squeak.org <http://trunk.squeak.org/>. >> Seems to me that what I???m saying about trunk.squeak.org <http://trunk.squeak.org/> is still true: it has been shut down on its usual subdomain; and, a new process has appeared on box4. >> Looks to me like trunk development is halted for the moment. >> >> Chris >> >>> On Oct 14, 2014, at 8:52 PM, David T. Lewis <[hidden email]> wrote: >>> >>>> On Tue, Oct 14, 2014 at 08:37:56PM -0400, Chris Cunnington wrote: >>>>> On Oct 14, 2014, at 8:14 PM, Dale Henrichs <[hidden email]> 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 >>> >>> >> > >> > > |
In reply to this post by David T. Lewis
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. From: [hidden email] Sent: 15/10/2014 01:52 To: [hidden email] Subject: Re: [squeak-dev] http://build.squeak.org/ down? > > On Oct 14, 2014, at 8:14 PM, Dale Henrichs <[hidden email]> 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 |
Free forum by Nabble | Edit this page |