Received: (qmail 26359 invoked from network); 25 Feb 1999 22:15:28 -0000
Message-Id: <36D5D83B.5C4F5A67@uswest.com>
Date: Thu, 25 Feb 1999 15:09:47 -0800
From: Derek Andree <dxandr2@uswest.com>
Sender: dxandr2@uswest.com
To: apbugs@hyperreal.org
Cc: apbugs@Apache.Org
Subject: Servers hang on either Keepalive or on Read (if keepalive is turned off)

>Number:         3968
>Category:       pending
>Synopsis:       Servers hang on either Keepalive or on Read (if keepalive is turned off)
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   unknown
>Arrival-Date:   Thu Feb 25 14:20:02 PST 1999
>Last-Modified:  Tue Apr 20 16:02:13 PDT 1999
>Originator:     
>Organization:
>Release:        
>Environment:
>Description:
>How-To-Repeat:
>Fix:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: dgaudet
State-Changed-When: Tue Apr 20 16:02:13 PDT 1999
State-Changed-Why:
just like 3967
>Unformatted:
More curious stuff here...

Telnet to port 80 on the machine (i.e. telnet localhost 80) and simply
leaving the connection open without typing anything behaves as it
should: Apache closes the connection after the Timeout period.  When
I telnet to the machine from a different host (othermachine# telnet
machinename 80) the connection will never be closed by Apache, and that
slot is forever hosed in a "...reading..." state when viewing the
server-status page.

Assuming this to be a Solaris issue, I went and got all the recommended
patches from Sun for Solaris 2.6.  After installing and rebooting the
machine, it behaved normally for awhile.

But a day later hung servers are there again, thus I assume the reboot
probably made things work rather than the patches from sun.

I know there are LOTS of issues with Solaris (after looking at the
apache source tree) ... my guess is something to do with the networking
stuff in Solaris.

--Derek