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
On Wed, Sep 03, 2008 at 01:45:47PM +0300, Octavian Rasnita wrote:
From: Matt S Trout [EMAIL PROTECTED]
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.
Do you know if there
Quoting Tomas Doran [EMAIL PROTECTED]:
On 28 Aug 2008, at 19:32, [EMAIL PROTECTED] wrote:
That was my guess, too. But if the problem is really situated
there it should have occurred much earlier. Nothing dramatically
changed in our setup or application. I'll try a rollback of the
Two days ago I suddenly started receiving intermittent blank pages. Immediately
reloading the page led to the expected response. Looking at the error logs of
the past two days I can see loads of the following error:
Use of uninitialized value in concatenation (.) or string at
Tobias Kremer wrote:
Two days ago I suddenly started receiving intermittent blank pages. Immediately
reloading the page led to the expected response. Looking at the error logs of
the past two days I can see loads of the following error:
Use of uninitialized value in concatenation (.) or string
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
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
On Thu, Aug 28, 2008 at 7:02 AM, Tobias Kremer [EMAIL PROTECTED] wrote:
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
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
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
Tobias Kremer [EMAIL PROTECTED] wrote on 08/28/2008 10:44:31 AM:
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
On 28.08.2008, at 18:48, [EMAIL PROTECTED] wrote:
Is it possible that the concat error and resstart are related
(memory load)
but the blank pages are due to the restart killing (restarting) the
procs
off before the fastcgi payload is sent
That was my guess, too. But if the problem is
Tobias Kremer [EMAIL PROTECTED] wrote on 08/28/2008 12:29:13 PM:
On 28.08.2008, at 18:48, [EMAIL PROTECTED] wrote:
Is it possible that the concat error and resstart are related
(memory load)
but the blank pages are due to the restart killing (restarting) the
procs
off before the
On 28 Aug 2008, at 19:32, [EMAIL PROTECTED] wrote:
That was my guess, too. But if the problem is really situated
there it
should
have occurred much earlier. Nothing dramatically changed in our
setup or
application. I'll try a rollback of the Rose::HTML::Form module to
eliminate it
from the
14 matches
Mail list logo
