Ken, thank you so much. The cause of the slowness we've been seeing the last few days is some runaway seaside client Process. It was busy rendering HTML on the difference between two different versions of 45Deprecated-fbs.8 (with two different UUID's) but, somehow, had itself caught in an endless loop that was sucking resources and causing the image to grow.
I downloaded the image to my local machine, terminated the rogue process from the Process Browser, reuploaded it, renamed the old Squeak3.11-8824-SS.image to .bad, then killed the SS process.
At first, it looked like daemontools was restarting it, but something looked weird when I grepped for the process; there were two of them.
chrismuller@box2:/home/squeaksource$ ps -ef | grep Squeak3.11-8824-SS.image
root 2218 2109 0 Sep13 ? 00:00:01 readproctitle service errors: ...in BlockContext>newProcess?+ exec /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-display-none /home/squeaksource/Squeak3.11-8824-SS.image?+ exec /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-display-none /home/squeaksource/Squeak3.11-8824-SS.image?
squeaks 30167 2224 0 21:34 ? 00:00:00 /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-display-none /home/squeaksource/Squeak3.11-8824-SS.image
And yet, I could not access
source.squeak.org.
So, I killed both of those and waited for daemontools to start it again. I thought it would be immediate, but repeated ps checks did not show anything. Maybe I didn't wait long enough, but I went ahead and started it manually.
So
source.squeak.org is up but now there are two processes, each owned by root, instead of squeaksource. Hmph.
root 5753 26447 0 21:45 pts/0 00:00:00 sudo /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-display-none /home/squeaksource/Squeak3.11-8824-SS.image
root 5754 5753 15 21:45 pts/0 00:00:12 /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-display-none /home/squeaksource/Squeak3.11-8824-SS.image
I don't know why daemontools didn't start it automatically, but as I was sitting there, waiting for it, I realized how much I dislike not being in control of whether the process is running or not...
Any advice?