[Seaside] Re: Handling errors - staging/production
sebastian at flowingconcept.com
Tue May 31 12:51:11 UTC 2011
We were using monit for a while but then it didn't quite fit our needs. So, we made a little seaside app we (use internally) that can be configured to monitor a cluster of worker-images (serving the real web apps)
When a worker is unresponsive for any reason it will receive a gentle kill -15 and if it's still there, say 30sec after the signal, it will receive a kill -9 (checking if it really isn't there anymore) and then it will be restarted.
So, by 'goes really bad' I mean (inside one of this workers) an exception that your custom error handler (like the one Boris show) didn't catch (a bug in the http server used by seaside can do that for example). Actually is rare. It didn't happen to us in production but happened in development a couple of times... I think I was implementing x-sendfile or something unusual.
On May 31, 2011, at 5:56 AM, Francois Stephany wrote:
>> first (optimist case) a custom error handler clones the walkback of the
>> exception and redirects the app to a custom error page (a tiny little
>> very simple seaside app.) So, this page gives the user the option to
>> write us about what was she doing or just click on "login again." In
>> either case, the walkback reach us printed in an email along with the
>> user who had the problem so we can provide support or notify her about
>> an upgrade that had fixed the issue.
> Interesting !
> I dont need such a level of feedback from the user but the process seems nice.
>> second, if things goes really bad, it falls back to a simple page saying
>> that some less gentle error happened :)
> What do you mean with 'goes really bad' ? I guess it means that your image is not responding anymore ?
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside