www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From T.V.Raman <ra...@adobe.com>
Subject os-solaris/3749: Apparent memory leak +httpd processes that refuse to die
Date Fri, 22 Jan 1999 18:05:26 GMT

>Number:         3749
>Category:       os-solaris
>Synopsis:       Apparent memory leak +httpd processes that refuse to die
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Jan 22 10:10:00 PST 1999
>Last-Modified:
>Originator:     raman@adobe.com
>Organization:
apache
>Release:        1.3.4
>Environment:
SunOS labrador 5.6 Generic_105181-03 sun4u sparc SUNW,Ultra-2
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.7.2/specs
gcc version 2.7.2

Apache 1.3.4 --built with mod_dso support --configured as 
./configure \
"--prefix=/export/local/apache" \
"--enable-module=most" \
"--enable-shared=max" 


>Description:
On a moderately  loaded server  (around 3000 requests per day on acerage,
Apache 1.3.4 (as well as 1.3.1 and 1.3.3 before it)
hits serious trouble. The server in question exports a large number of Novell shares to the
Intranet via NFS; the problems appear to emerge when the Novell servers dont respond. In this
case, the number of httpd processes grows, memory drains, and things grind to a halt.

Attempting to stop apache by saying
bin/apachectl stop 
produces the following warnings in error_log about children refusing to die;
httpd: [Fri Jan 22 09:39:30 1999] [warn] child process 483 still did not exit, sending a SIGTERM
... similar lines omitted --

>How-To-Repeat:
The problem appears to be specific to Solaris 2.6 and exporting novell volumes via NFS and
apache.
>Fix:
None known yet, 
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]




Mime
View raw message