For information:

There is currently a problem with several services running on squeak.org,
including source.squeak.org. Discussion is on the box-admins list, although
the web interface to the list archives is also off line.

The problem is related to URL mapping, as opposed to the services themselves,
and source.squeak.org is currently accessible through http://source.squeak.org:9090.

Dave

On Mon, Jun 09, 2014 at 07:45:46AM -0400, David T. Lewis wrote:
> On Mon, Jun 09, 2014 at 07:29:20AM -0400, David T. Lewis wrote:
> > The problem seems to be back. The symptoms that I see are:
> > 
> > - http://source.squeak.org and http://bugs.squeak.org are not responding
> > - http://squeak.org is working normally
> > - http://source.squeak.org:9090 brings up the source.squeak.org page
> > 
> > Processes are running normally on box2.squeak.org.
> > 
> > The last time this happened, restarting apache2 two times seems to have
> > resolved the problem. I will try doing that now.
> > 
> 
> I have restarted apache a total of three times (sudo /etc/init.d/apache2 restart),
> and the problem remains.
> 
> The last time this happened was one week ago, and at the time we noticed
> an rsync backup job eating a lot of system resource. That is not the case
> right now, but it's possible there is some issue associated with backup
> jobs (run from cron) that somehow affects the apache addressing.
> 
> I will probably not be able to take any further action on this today. My
> suggestion is that someone (anyone) on box-admins restart the apache2
> service about an hour from now, and keep trying every hour until it decides
> to start working.
> 
> Dave
> 
> 
> > On Mon, Jun 02, 2014 at 02:35:01PM +0200, Tobias Pape wrote:
> > > Hi,
> > > 
> > > On 02.06.2014, at 13:18, David T. Lewis <lewis at mail.msen.com> wrote:
> > > 
> > > [?]
> > > >> 
> > > >> Thanks Tobias,
> > > >> 
> > > >> I will be away with no easy access to box2 for the next day, so I
> > > >> don't want to touch anything that might cause a bigger problem that
> > > >> I can't fix. That said ... I don't think the runaway rnapshot process
> > > >> is the cause of the problem, although it might be a symptom of something
> > > >> else. I can connect to source.squeak.org on 9090 and it works fine, so
> > > >> the CPU usage is not directly causing a problem.
> > > >> 
> > > >> I will try restarting apache (sudo /etc/init.d/apache2 restart) and see
> > > >> if it helps.
> > > >> 
> > > > 
> > > > No, that did not fix it. www.squeak.org remains active, but source.squeak.org
> > > > and bugs.squeak.org are not available.
> > > > 
> > > > As before, connecting to http://source.squeak.org:9090 brings up the web page
> > > > normally.
> > > 
> > > It turns out that apache did not successfully restart.
> > > Why, remains a mystery. Yet I now have started it and
> > > the pages should be fine again.
> > > 
> > > Best
> > > 	-Tobias
> > > 
> >