On Thu, Aug 28, 2008 at 05:44:31PM +0200, Tobias Kremer wrote: > Quoting [EMAIL PROTECTED]: > > Tobias Kremer <[EMAIL PROTECTED]> wrote on 08/28/2008 09:02:24 AM: > > > Quoting Sebastian Willert <[EMAIL PROTECTED]>: > > > > Are you using Perlbal in front of FastCGI? Perlbal is prone to deliver > > > > blank pages if the back-end times out. Unfortunately I haven't found > > > > a way to avoid this behavior, but maybe someone on the list can help > > > > out ... > > > No, we're using lighttpd and nothing changed on that front during the > > last two > > > days :( > > Are they delivered instantly or after a long pause? > > Instantly. > > I just noticed that shortly after a series of those errors appear in the error > log, the process gets killed off (and restarted) by daemontools' softlimit due > to memory constraints.
You might want to load Catalyst::Plugin::AutoRestart as well so the processes restart themselves gracefully at the end of a request before it hits the softlimit. I notice downthread you've solved the underlying problem, but adding AutoRestart into your setup would mean that if something similar goes wrong again you'll avoid the firing blanks problem. -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Director http://www.shadowcat.co.uk/catalyst/ Shadowcat Systems Ltd. Want a managed development or deployment platform? http://chainsawblues.vox.com/ http://www.shadowcat.co.uk/servers/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/