general/6545: unkilled child process occur, and apache hang up (give no response).

[Le...@locus.apache.org, Dong-Hyun <sa...@shinbiro.com>]

>Number:         6545
>Category:       general
>Synopsis:       unkilled child process occur, and apache hang up (give no response).
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   unknown
>Arrival-Date:   Sat Sep 16 20:00:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     sayit@shinbiro.com
>Release:        1.3.12
>Organization:
apache
>Environment:
SunOS ktfweb 5.6 Generic_105181-22 sun4u sparc SUNW,Ultra-Enterprise-10000
>Description:
in spite of 'kill -9' of root user, process is alive.
then, apachectl stop, but this process is unkilled,
and apachectl start, but apache starting is fail.
(because of binding 80 port of that process).

* nfs is only /vol, other directory is ufs.
* use cronolog-1.6.1 for rotating log.
* use ssl module - 'mod_ssl-2.6.4-1.3.12'.
* virtual host - upon IP, 80 and 8080, ssl - 443.

something doubted
* error_log : [warn] (22) Invalid argument: setsockopt: (TCP_NODELAY)
             - occur 10-20 per day,( web page have 500000 hit per day )
* heavy flash : about 700k
* attack?? 
>How-To-Repeat:
??
>Fix:
server rebooting -_-;;
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]