Am 07.12.2011 um 12:26 schrieb Henrik Sperre Johansen:
On 07.12.2011 10:47, Norbert Hartl 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 Could it be related to http://forum.world.st/Too-many-semaphores-image-blocked-td3871970i20.html#a3... ?
Yes, it could. My image was a #13315 image so it made a good candidate for the problem. Furthermore I got the external semaphore message in my development image a few times. There I just could restart the image. So I don't understand really what happened. If I'm able to restart my development image and solve the problem then what makes my server image incapable of doing the same. Is it by coincidence that there is a warning about the external semaphore but there is even more usage of them so that the image is saved with such a shortage on semaphores that makes a new start of the image block? Norbert