[Seaside] Seaside image health check

[Sebastian Sastre]

BTW, I've tried a couple of times CogVM but always failed to get it stable.

Who can make use of the dump logs?

sebastian

o/




On Dec 22, 2011, at 2:46 PM, Levente Uzonyi wrote:

> On Thu, 22 Dec 2011, Paul DeBruicker wrote:
> 
>> I have a Pharo 1.3-13315/Seaside 3.0.6.3 headless image on 64bit linux that sometimes stops responding to HTTP requests and acts like its in an infinite loop. If I connect to that image with the RFB after a couple minutes I can enter my password and it drops out of the infinite loop and resumes answering HTTP requests as if nothing was wrong.  The hang happens irregularly and I haven't yet been able to get access to a debugger when it is hanging. CPUWatcher doesn't catch it either.
>> 
>> I'm thinking to use the Scheduler package + ZnClient to send a request from that image to itself requesting a page, and if it times out, to write the ProcessBrowser + CPU usage data to a log file.
>> 
>> Is there an established/better/other way to attempt to diagnose these intermittent hangs?
> 
> If you're using CogVM, then you can force printing the content of all smalltalk stacks to stdout by sending a USR1 signal to the process with the following command:
> 
> kill -USR1 <pid>
> 
> The currently active process will be printed first.
> 
> 
> Levente
> 
>> 
>> Thanks
>> 
>> Paul
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20111222/3f471c67/attachment.htm