Bug 50151 - Software caused connection abort and apache process in "W" Sending Reply mode freezes
Summary: Software caused connection abort and apache process in "W" Sending Reply mode...
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.16
Hardware: HP Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-10-25 12:17 UTC by Dmitry Mitko
Modified: 2018-11-07 21:08 UTC (History)
2 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Mitko 2010-10-25 12:17:25 UTC
Apache writes "Software caused connection abort ..." error message to logfile like this:

[Sat Oct 23 06:20:32 2010] [error] Software caused connection abort at /home/prf/lib/atom_html.pm line 661.\n\t...propagated at /home/prf/lib/atom_html.pm line 668.\n

Then, we can see one of the apache processes freezed in "W" Sending Reply mode, that does nothing.

And we can see TCP CLOSE_WAIT connection, like this:

apache2   20336  apache    0u     IPv4  253746913        0t0        TCP node1:hosts2-ns->node1:40649 (CLOSE_WAIT)

I can restart apache server only to remove it freezed apache process.

I can't find any apache configuration settings to set CLOSE_WAIT timeout, did it manually as SIGALRM handler, that kills apache process, but it isn't a solution, of course.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:25 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.