[Box-Admins] squeaksource.com image update (was: Does source.squeak.org have the socket leak problem?)

[David T. Lewis]

On Sat, Oct 12, 2013 at 05:58:06PM -0400, David T. Lewis wrote:
> On Wed, Oct 02, 2013 at 05:33:31PM +0200, Bert Freudenberg wrote:
> > On 2013-10-02, at 17:17, "David T. Lewis" <lewis at mail.msen.com> wrote:
> > 
> > > Would you mind putting a copy of the image and changes files for source.squeak.org
> > > on box3 so I can take a look at it (I don't have access to box2)? Thanks.
> > 
> > Done: ~bertfreudenberg/
> >
> 
> I have replaced the older squeaksource.com image with a newer image based on
> the source.squeak.org image that Bert provided. I activated the new image
> on box3.squeak.org today, and am monitoring it for problems.
> 
> I started the repository export yesterday and completed the import to the new
> image today. During that period there have been no commits to squeaksource.com,
> so I anticipate no loss of data.
> 
> The new image is called ~ssdotcom/SqueakSource/squeaksource.3.image. In the
> event of problems, the rollback plan is to reactivate the older
> ~ssdotcom/SqueakSource/squeaksource.2.image (see ~ssdotcom/README for details).
> 
> Currently the new image is running and appears to work fine (although users
> may have noticed some brief outages, for which I apologize).  However it is
> currently consuming a heavy CPU load, so I am watching to see if this goes
> down (I have seen similar patterns in the past related to cache updates,
> which seem to settle down after a while). If the CPU load does not go back
> down within the next hour, I will revert back to the old image and try this
> again on another day.
>

All is well now. The initial CPU load was associated with the Cache-Thread
process, which runs a statistics gathering job once daily. This is normal,
and the system is now running with 98% idle as expected. I will continue to
monitor, but I think the upgrade is successful.

Dave