maybe then you can kill it manually and see which processes were living there,.. and which that should be were not?

On Wed, Dec 7, 2011 at 8:09 PM, Norbert Hartl <norbert@hartl.name> wrote:
The image didn't crash and in the debug log there is nothing hinting what could be the cause. The image just stopped serving the network and couldn't be restarted.

Norbert

Am 07.12.2011 um 19:52 schrieb Javier Pim��s <elpochodelagente@gmail.com>:

Probably you have a crash.dmp or a PharoDebug.log which tells you what is happening. Look at the backtrace to see what causes the error and then maybe there's some way to help you fixing it.

Cheers,
Javier.

On Wed, Dec 7, 2011 at 10:47 AM, Norbert Hartl <norbert@hartl.name> wrote:
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



--
Lic. Javier Pim��s
Ciudad de Buenos Aires



--
Lic. Javier Pim��s
Ciudad de Buenos Aires