www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sara Marxen <smar...@sccd.ctc.edu>
Subject os-linux/3387: Regularly the httpd children will all die with no errors given, the root process will still be running, must stop and restart httpd.
Date Thu, 12 Nov 1998 16:02:30 GMT

>Number:         3387
>Category:       os-linux
>Synopsis:       Regularly the httpd children will all die with no errors given, the root
process will still be running, must stop and restart httpd.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Nov 12 08:10:01 PST 1998
>Last-Modified:
>Originator:     smarxen@sccd.ctc.edu
>Organization:
apache
>Release:        1.3.1
>Environment:
Linux eddie.sccd.ctc.edu 2.0.34 #3 Wed Aug 26 15:23:44 PDT 1998 i686 unknown
redhat 5.1, apache 1.3.1, gcc-2.7.2.3-11, glibc-debug-2.0.7-19, glibc-profile-2.0.7-19, glibc-devel-2.0.7-19,
glibc-2.0.7-19

>Description:
I cannot pinpoint any specific time or reason that the server dies.   Just every 6 or 7 hours
the all the the httpd children will slowly die (within about 10 minutes) until there is
only one process left, the one owned by root.  I then stop and restart the server using the
method
described on apaches web page ( kill -TERM `cat /var/run/httpd.pid`).  About every three days
this
method of stopping and restarting the server does not work because it says the 
port (80) is still in use and there is no /var/run/httpd.pid file and I must reboot the server.
 I have recompiled httpd
recently and it only caused the problem to be worse.  I also increased min and max
spare servers so as to ensure the server was not getting overloaded.  But this problem
does not seem to be related to the nubmer of processes running on the system.  
I'm also attaching a process and netstat report from when the server dies.  Don't
know if it will help or not, but I hope so.

-------------------------
server up,  11 processes, at 18:48:00Monday
server up,  11 processes, at 18:50:01Monday
server up,  11 processes, at 18:52:00Monday
server up,  10 processes, at 18:54:01Monday
server up,  10 processes, at 18:56:00Monday
server up,  10 processes, at 18:58:01Monday
 
server up,  6 processes, at 19:00:00Monday
PS output
root      1160  0.0  0.2   848   348  ?  S    19:00   0:00 grep httpd
root     31731  0.0  0.6  1648   880  ?  S    16:21   0:00 httpd
wuser      782  0.0  0.8  1764  1052  ?  S    18:32   0:00 httpd
wuser      785  0.0  0.8  1764  1052  ?  S    18:32   0:00 httpd
wuser      789  0.0  0.8  1764  1052  ?  S    18:33   0:00 httpd
wuser      790  0.0  0.8  1764  1052  ?  S    18:33   0:00 httpd
wuser      791  0.0  0.8  1764  1052  ?  S    18:33   0:00 httpd
wuser      792  0.0  0.8  1764  1052  ?  S    18:33   0:00 httpd
Netstat output
tcp        0      0 *:www                   *:*                     LISTEN
tcp        0      0 eddie.sccd.ctc.edu:www  cs207-21.student.w:1034 FIN_WAIT2
tcp        0   9003 eddie.sccd.ctc.edu:www  cs207-21.student.w:1035 FIN_WAIT1
tcp        0   3327 eddie.sccd.ctc.edu:www  cs207-21.student.w:1036 FIN_WAIT1
tcp        1      0 eddie.sccd.ctc.edu:www  134.39.67.90:1888       TIME_WAIT
tcp        1      0 eddie.sccd.ctc.edu:www  134.39.67.90:1889       TIME_WAIT
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1438      ESTABLISHED
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1439      ESTABLISHED
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1440      ESTABLISHED
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1441      ESTABLISHED
 
server up,  1 processes, at 19:01:00Monday
PS output
root      1177  0.0  0.2   848   348  ?  S    19:01   0:00 grep httpd
root     31731  0.0  0.6  1648   880  ?  S    16:21   0:00 httpd
wuser      792  0.0  0.8  1764  1052  ?  S    18:33   0:00 httpd
Netstat output
tcp        0      0 *:www                   *:*                     LISTEN
tcp        0      0 eddie.sccd.ctc.edu:www  cs207-21.student.w:1034 FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  cs207-21.student.w:1035 FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  cs207-21.student.w:1036 FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1438      FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1440      FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.240:1441      FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.80:1439       FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.80:1441       FIN_WAIT2
 
server up,  1 processes, at 19:02:01Monday
 
PS output
root      1194  0.0  0.4  1160   624  ?  R    19:02   0:00 grep httpd
root     31731  0.0  0.6  1648   880  ?  S    16:21   0:00 httpd
wuser      792  0.0  0.8  3248  1096  ?  S    18:33   0:00 httpd
Netstat output
tcp        0      0 *:www                   *:*                     LISTEN
tcp        0      0 eddie.sccd.ctc.edu:www  cs207-21.student.w:1035 FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  cs207-21.student.w:1036 FIN_WAIT2
tcp        0      0 eddie.sccd.ctc.edu:www  134.39.67.145:1451      FIN_WAIT2
tcp        0  38652 eddie.sccd.ctc.edu:www  134.39.67.145:1452      ESTABLISHED
 
server down 19:03:01Monday
 
Shutting down http: httpd
Starting httpd: httpd
 
server up,  20 processes, at 19:04:00Monday
server up,  20 processes, at 19:06:00Monday
server up,  22 processes, at 19:08:01Monday
server up,  22 processes, at 19:10:00Monday
server up,  22 processes, at 19:12:01Monday
server up,  22 processes, at 19:14:00Monday
server up,  23 processes, at 19:16:01Monday
server up,  23 processes, at 19:18:00Monday
server up,  23 processes, at 19:20:01Monday
server up,  23 processes, at 19:22:00Monday
>How-To-Repeat:
I cannot recreate this problem.  The URL is http://edison.sccd.ctc.edu
>Fix:
I have seen similar problems in the bug database but nothing that is the same problem or the
same version, 
and I do not know how to fix it.
>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