RedThree has asked for the wisdom of the Perl Monks concerning the following question:

Like the title says, I've started to see "Software caused connection abort" errors from my mod_perl scripts on print statements.

The thing is, there are no external issues, and I haven't changed, well, anything that I know of, to get these errors to start. I'd have never known had I not checked the logs. Of every, say, thousand executions of these scripts, it throws one error - and it still works and outputs just fine.

However, I'm afraid that I'm missing something here, that will end up messing things up.

Any ideas?

Edit Update: What I'm looking for, I guess, is "what does this error mean"..
Further info edit: This error only started showing up after these three 'emergency security patches' were added to the system:
RHEL5: http://rhn.redhat.com/errata/RHSA-2009-1222.html
RHEL4: http://rhn.redhat.com/errata/RHSA-2009-1223.html
RHEL3: http://rhn.redhat.com/errata/RHSA-2009-1233.html
  • Comment on "Software caused connection abort" mod_perl errors on 'print' statement

Replies are listed 'Best First'.
Re: "Software caused connection abort" mod_perl errors on 'print' statement
by ikegami (Patriarch) on Oct 05, 2009 at 01:35 UTC
    Could that mean the client closed?
[reply]
      As in "user stopped their browser load before it go to the print statement?" I didn't think it worked that way (apologies for my noobishness)
[reply]
        I think mod_cgi buffers the output, but it wouldn't surprise me if mod_perl gives you a more direct path to the client. I don't know either, which is why I phrased it as a question.
[reply]

Back to Seekers of Perl Wisdom