httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50261] New: graceful restart with multiple listeners using prefork MPM can result in hung processes
Date Fri, 12 Nov 2010 15:08:05 GMT

           Summary: graceful restart with multiple listeners using prefork
                    MPM can result in hung processes
           Product: Apache httpd-2
           Version: 2.2.17
          Platform: PC
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: prefork

Created an attachment (id=26286)
 --> (
Build configuration command

I have symptoms like those described on bug 42829. However, since that bug was
marked RESOLVED FIXED on 2009-02-13 I am starting a new bug. I am sorry if this
is the wrong thing to do.

I am running Apache 2.2.17 (prefork) compiled from source using the Sun
Studio 12.1 C compiler on a Solaris 10 x86/64 system at kernel patch
level 142910-17. I will attach the configuration options used for the
build, and the cut-down httpd.conf I have used to reproduce the problem.

The problem is that, almost every time I do a graceful (USR1) restart, one
or more child processes remain stuck indefinitely in the 'Gracefully
finishing' state (represented bu a 'G' in the status display). My
configuration contains more that one Listen directive. In the simplified
example, I listen on an IPv4 address and an IPv6 address.

I cannot reproduce the problem if I have only one Listen directive. It is
this detail which leads me to suspect that my problem is related to bug

I have managed to reproduce the problem with an httpd running under truss,
so I have a system call trace covering a graceful restart which left two
stuck processes. I will attach this, and pstack backtraces of the two
processes which were stuck. (Truss alters the timing, and reduces the
chance of stuck processes.)

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message