Software caused connection abort at
am 01.08.2009 05:32:36 von Jim Albert
I recently upgraded software on my apache servers so that I am now running:
Apache/2.2.3
MOD_PERL = mod_perl/2.0.4
MOD_PERL_API_VERSION = 2
perl 5.8.8
Operating system: Red Hat Linux 2.6.18-128.2.1
In my web server error logs I started seeing messages such as:
Software caused connection abort at 'some_module_name.pm' line
'some_line_number'.
All the modules that appear in these messages give me the impression it
is likely mod_perl scripts that are causing them.
My mod_perl scripts are configured as such:
SetHandler perl-script
PerlHandler ModPerl::PerlRun
Options ExecCGI
PerlSendHeader On
The line numbers in the error message seem to all point to lines of code
in modules that are doing output to stdout.
Any thoughts on the circumstances that might produce those errors?
--
Jim Albert
Re: Software caused connection abort at
am 03.09.2009 06:41:00 von Rob Mueller
Hi
We recently started seeing this appearing in our logs as well, and I'm not
sure what's causing it. We didn't change our software in any way that I can
see would have caused this to start happening, so it's quite odd.
Did you work out what was causing it?
Rob
----- Original Message -----
From: "Jim"
To:
Sent: Saturday, August 01, 2009 1:32 PM
Subject: Software caused connection abort at
>I recently upgraded software on my apache servers so that I am now running:
> Apache/2.2.3
> MOD_PERL = mod_perl/2.0.4
> MOD_PERL_API_VERSION = 2
> perl 5.8.8
>
> Operating system: Red Hat Linux 2.6.18-128.2.1
>
> In my web server error logs I started seeing messages such as:
> Software caused connection abort at 'some_module_name.pm' line
> 'some_line_number'.
>
> All the modules that appear in these messages give me the impression it is
> likely mod_perl scripts that are causing them.
>
> My mod_perl scripts are configured as such:
>
> SetHandler perl-script
> PerlHandler ModPerl::PerlRun
> Options ExecCGI
> PerlSendHeader On
>
>
> The line numbers in the error message seem to all point to lines of code
> in modules that are doing output to stdout.
>
> Any thoughts on the circumstances that might produce those errors?
>
> --
> Jim Albert
>