[Box-Admins] box3.squeak.org off line - HELP neeeded

[Chris Muller]

> On Tue, Oct 08, 2013 at 07:54:05PM -0500, Chris Muller wrote:
>> I just deployed an updated image for "new trunk" at
>> box4.squeak.org:8888/trunk.  This is the one that uses the Magma
>> backend.  I haven't done any benchmarks but the response time seems
>> pretty snappy, even compared to regular source.squeak.org.  Could be
>> due to Cog, the Magma backend, or box4 being under less load than
>> box3.
>
> It might be all of the above. I'm thinking that the priority for the
> squeaksource.com image is to first get it up to date to the level of
> source.squeak.org, then at our leisure we can bring both of them together
> up to a the level that you are demonstarting with Cog and Magma. But
> the main thing is to get squeaksource.com stable, which is not yet the case.

source.squeak.org is getting slow too, and it runs on an old image.
The work I've done to bring it to a trunk image under Cog is based on
the source.squeak.org image, and really not that many changes.

> It turns out that the following snippet from the workspace that SCG provided
> took care of the problem for now:
>
>         " kill runaway processes "
>         ProcessBrowser open.
>         Process allInstances do: [ :each |
>                 each priority = 30 ifTrue: [
>                         each terminate ] ].

OMG!  No wonder SS has so many problems if it is so unloved that
someone would arbitrarily kill processes based on their priority!

> So I'm guessing that some Seaside handler got wedged, presumably concurrent
> with an excessive memory usage condition, and it probably failed in some way
> that did not let the garbage collector clean up the mess.

SS forks the email out to Project subscribers at priority 30. See
SSEMailSubscription>>#versionAdded:to:.  I wonder whether that's what
those were?