www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kjell Krona <kr...@nada.kth.se>
Subject general/1509: Child processes becomes <defunct> after a couple of hours, server not responding
Date Thu, 04 Dec 1997 09:53:51 GMT

>Number:         1509
>Category:       general
>Synopsis:       Child processes becomes <defunct> after a couple of hours, server
not responding
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Dec  4 02:00:00 PST 1997
>Originator:     krona@nada.kth.se
>Release:        apache_1.2.4-sun4m-sun
SunOS hmi.nada.kth.se 5.5.1 Generic_103640-05 sun4m sparc SUNW,SPARCstation-4
I have installed the Apache server to run the BSCW system from bscw.gmd.de. Unfortunately,
it stops running sometime during each night, when it is not used. To make sure that it is
not the BSCW system that causes the problem, I started a separate httpd process on another
port last night. After verifying that it was running correctly (showing the lcoal homepage),
it was left in essentially idle state during the night. Today, the browser gives first the

error message "Document contains no data", then with the next click the connection just waits
forever. ps shows all child processes as "<defunct>". After stopping the server as described
in the docs, the browser reports that the connection was lost (so a connection is made bit
not responded to). Wehen the server is restarted, everything work as expected for a while.

The only workaround I have found is to make a script with at which restarts the server. It
to work (not disturbing anything else) but it does not feel proper..
See above. Perhaps it is due to the server being idle too long?

[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. ]

View raw message