Re: os-linux/3343: Server dies after 1-20 hours of usage. (fwd)

[Dean Gaudet <dg...@arctic.org>]

The following reply was made to PR os-linux/3343; it has been noted by GNATS.

From: Dean Gaudet <dg...@arctic.org>
To: apbugs@apache.org
Cc:  Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage. (fwd)
Date: Sat, 1 May 1999 10:41:56 -0700 (PDT)

 ---------- Forwarded message ----------
 Date: Wed, 17 Mar 1999 12:13:59 -0600
 From: Darrin Martin <da...@cajun.net>
 To: dgaudet@apache.org
 Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage.
 
 As per your request, the following is the netstat -nt command issued
 after the server hung...
 
 [root@www /root]# netstat -nt
 Active Internet connections (w/o servers)
 Proto Recv-Q Send-Q Local Address           Foreign Address
 State
 tcp      368      0 206.65.73.212:80        169.207.68.4:6337
 CLOSE_WAIT
 tcp      368      0 206.65.73.212:80        169.207.68.4:6326
 CLOSE_WAIT
 tcp      391      0 206.65.73.205:80        142.103.168.111:3458
 CLOSE_WAIT
 tcp      416      0 206.65.73.205:80        216.199.5.169:46679
 ESTABLISHED
 tcp      343      0 206.65.73.205:80        205.188.154.138:48871
 CLOSE_WAIT
 tcp      311      0 206.65.73.205:80        152.2.179.50:2072
 CLOSE
 tcp      391      0 206.65.73.205:80        142.103.168.111:3459
 CLOSE_WAIT
 tcp      311      0 206.65.73.205:80        152.2.179.50:2073
 CLOSE
 tcp      289      0 206.65.73.205:80        12.4.54.254:2060
 CLOSE
 tcp      322      0 206.65.73.205:80        139.78.213.97:3066
 CLOSE_WAIT
 tcp      311      0 206.65.73.205:80        152.2.179.50:2074
 CLOSE
 tcp      416      0 206.65.73.205:80        216.199.5.148:46680
 ESTABLISHED
 tcp     1715      0 206.65.73.205:80        142.103.168.111:3460
 CLOSE_WAIT
 tcp      140      0 206.65.73.205:80        209.67.244.80:2155
 ESTABLISHED
 tcp      289      0 206.65.73.205:80        12.4.54.254:2061
 CLOSE
 tcp      270      0 206.65.73.205:80        139.78.213.97:3094
 CLOSE_WAIT
 tcp      289      0 206.65.73.205:80        12.4.54.254:2062
 CLOSE
 tcp      320      0 206.65.73.205:80        128.171.242.1:23279
 CLOSE_WAIT
 tcp      343      0 206.65.73.205:80        205.188.154.138:60184
 CLOSE_WAIT
 tcp      391      0 206.65.73.205:80        142.103.168.111:3461
 CLOSE_WAIT
 tcp      264      0 206.65.73.212:80        206.101.224.99:34452
 CLOSE_WAIT
 tcp      348      0 206.65.73.205:80        12.4.54.254:2073
 ESTABLISHED
 tcp        0      0 206.65.73.205:80        142.103.168.111:3462
 ESTABLISHED
 tcp      385      0 206.65.73.205:80        142.103.168.111:3463
 CLOSE_WAIT
 tcp      264      0 206.65.73.212:80        206.101.224.99:34554
 CLOSE_WAIT
 tcp        0    124 206.65.73.205:23        206.65.72.12:3243
 ESTABLISHED
 tcp      241      0 206.65.73.205:80        142.103.168.111:3471
 ESTABLISHED
 tcp      342      0 206.65.73.205:80        205.188.154.138:6924
 ESTABLISHED
 
 Also, please be aware of the fact that the problem seemed to have
 changed when we upgraded to the Redhat 5.2rpm version of Apache......
 now, instead of crashing every 20-24 hours, it is not expiring all
 requests, and eventually will lock up all available processes... I'll
 try and include a copy or you can view it yourself at
 http://www.v6fbody.com/server-status Login:apache Password:group
 
 Thank you.
 Darrin Martin
 
 -------snip---------
 
 Comment-Added-By: dgaudet
 Comment-Added-When: Tue Mar 16 08:34:26 PST 1999
 Comment-Added:
 When the problem happens, do a "netstat -nt" -- that should
 show to where the ESTABLISHED port 80 connections are ...
 I suspect something is just holding connections open.
 
 If that doesn't help, use "strace" on a few of the children
 to see what they're doing:
 
 strace -p pid_of_child
 
 Dean