The worst thing a computer can do is grind to a halt and leave no trace of why it happened. In Dolphin, I had some success rigging deployed images (runtime session managers) to, on control-break, log callstacks for all non-dead processes. Conditions in which two threads were each waiting on the other to do something were fairly obvious from the callstacks. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Norbert Hartl [norbert@hartl.name] Sent: Wednesday, December 07, 2011 4:47 AM To: Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] How to resurrect an unrepsonsive image? I have a headless image that was running for a couple of days. Now it is not responding anymore. The image was running still but the sockets for http and vnc were closed and restarting the image just brings it up without any sockets opened. Injecting something via script does not work either. I copied the image to my desktop and tried a few things but no success. What would be a good way to get a glimpse of what is causing problems? I had Scheduler running that saved the image every hour. And the image itself issues http request to the outside world every 10 minutes. thanks, Norbert