Sometimes stdout ends in the error_log!
I have a problem thats bothering me. Sometimes one of the httpd childs start to send normal output to the error_log, and browsers report 'document contains no data'. Normally only one child does it, and the others respond normally, meaning that the user sees sporadic failure. Is this a known problem? Is it in apache or in mod_perl? I don't recall having seen anything on the mod_perl list, and dejanews didn't turn up anything for apache. It seems to happen after restarts, so I have taken to the habit of stopping the server completely and starting from scratch. Not a good solution, but better than serving docs to the error_log. It is not a very busy server, so high load is not a likely source of the problem. I am not running the latest and greatest, but neither very old versions: Perl version 5.00503 for Apache/1.3.11 (Unix) PHP/3.0.14 mod_perl/1.21 Statically linked mod_perl (php is a DSO). I also use HTML::Mason 0.81 on one vhost. Server is a PC, Linux 2.2.13 from slackware 7, 128Mb ram. -- René Seindal ([EMAIL PROTECTED]) http://www.seindal.dk/rene/
Re: Sometimes stdout ends in the error_log!
I've encountered a similar problem, in which 'die' statements that
should never be called end up printing to the error log. Recently I
even did
if (0) { die "whoops" }
and a "whoops" error message appeared in the error log. Even weirder,
if (1) { print "hello" } else { die "goodbye" }
outputs both "hello" to the browser and "goodbye" to the error log.
It only seems to happen in somewhat complex pages (inside a module,
which has a bunch of hash refs) and if I try to isolate the cause by
paring things down, the problem just goes away.
My specs:
apache 1.3.12
mod_perl 1.21 static (upgrading to 1.22 now to see if it fixes anything)
Apache::ASP 0.18
perl 5.005_03
Redhat 6.1 / kernel 2.2.12
Dan
René Seindal wrote:
I have a problem thats bothering me. Sometimes one of the httpd childs
start to send normal output to the error_log, and browsers report
'document contains no data'. Normally only one child does it, and the
others respond normally, meaning that the user sees sporadic failure.
Is this a known problem? Is it in apache or in mod_perl? I don't recall
having seen anything on the mod_perl list, and dejanews didn't turn up
anything for apache.
It seems to happen after restarts, so I have taken to the habit of
stopping the server completely and starting from scratch. Not a good
solution, but better than serving docs to the error_log.
It is not a very busy server, so high load is not a likely source of the
problem.
I am not running the latest and greatest, but neither very old versions:
Perl version 5.00503 for Apache/1.3.11 (Unix) PHP/3.0.14 mod_perl/1.21
Statically linked mod_perl (php is a DSO). I also use HTML::Mason 0.81
on one vhost. Server is a PC, Linux 2.2.13 from slackware 7, 128Mb ram.
--
René Seindal ([EMAIL PROTECTED]) http://www.seindal.dk/rene/
Re: Sometimes stdout ends in the error_log!
Give me the Apache::ASP page, and I'll try to duplicate
the problem on my end.
--Joshua
Dan McCormick wrote:
I've encountered a similar problem, in which 'die' statements that
should never be called end up printing to the error log. Recently I
even did
if (0) { die "whoops" }
and a "whoops" error message appeared in the error log. Even weirder,
if (1) { print "hello" } else { die "goodbye" }
outputs both "hello" to the browser and "goodbye" to the error log.
It only seems to happen in somewhat complex pages (inside a module,
which has a bunch of hash refs) and if I try to isolate the cause by
paring things down, the problem just goes away.
My specs:
apache 1.3.12
mod_perl 1.21 static (upgrading to 1.22 now to see if it fixes anything)
Apache::ASP 0.18
perl 5.005_03
Redhat 6.1 / kernel 2.2.12
Dan
René Seindal wrote:
I have a problem thats bothering me. Sometimes one of the httpd childs
start to send normal output to the error_log, and browsers report
'document contains no data'. Normally only one child does it, and the
others respond normally, meaning that the user sees sporadic failure.
Is this a known problem? Is it in apache or in mod_perl? I don't recall
having seen anything on the mod_perl list, and dejanews didn't turn up
anything for apache.
It seems to happen after restarts, so I have taken to the habit of
stopping the server completely and starting from scratch. Not a good
solution, but better than serving docs to the error_log.
It is not a very busy server, so high load is not a likely source of the
problem.
I am not running the latest and greatest, but neither very old versions:
Perl version 5.00503 for Apache/1.3.11 (Unix) PHP/3.0.14 mod_perl/1.21
Statically linked mod_perl (php is a DSO). I also use HTML::Mason 0.81
on one vhost. Server is a PC, Linux 2.2.13 from slackware 7, 128Mb ram.
--
René Seindal ([EMAIL PROTECTED]) http://www.seindal.dk/rene/
