From owner-freebsd-questions@FreeBSD.ORG Thu Dec 16 03:44:49 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B685E16A4CE for ; Thu, 16 Dec 2004 03:44:49 +0000 (GMT) Received: from wonkity.com (wonkity.com [65.173.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B9DF43D49 for ; Thu, 16 Dec 2004 03:44:49 +0000 (GMT) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.13.1/8.13.1) with ESMTP id iBG3imGn054306; Wed, 15 Dec 2004 20:44:48 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.13.1/8.13.1/Submit) with ESMTP id iBG3im1e054303; Wed, 15 Dec 2004 20:44:48 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 15 Dec 2004 20:44:48 -0700 (MST) From: Warren Block To: Chris Kelly In-Reply-To: Message-ID: <20041215204023.D54277@wonkity.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (wonkity.com [127.0.0.1]); Wed, 15 Dec 2004 20:44:48 -0700 (MST) cc: freebsd-questions@freebsd.org Subject: Re: Network Problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 03:44:49 -0000 On Wed, 15 Dec 2004, Chris Kelly wrote: > FreeBSD www.piyeepress.com 4.8-RELEASE Pretty old... > Server version: Apache/1.3.27 (Unix) Quite old for Apache, and with some known security vulnerabilities, I think. > When accessed via a web browser, it will return pages for a few minutes. > Eventually access is super super slow, as if some TCP state table is > filling up. I reboot the server and it returns web pages as it should, > but only for five or so minutes, when it won't return any more pages, or > it returns pages but very slowly. It may not be a network problem. > The output of netstat -ap tcp doesn't show too many open > states. I swear that some tcp state table is filling up; > otherwise I have no clues. Here's something too: if I use lynx to access > the site, and I access the site from another server in the same rack, the > page is returned instantly. Here's some more confusion: non-Windows > machines seem to do better at getting pages from the server than do > Windows machines. A router choking? Some kind of firewall problem? Either way, I'd still suggest updating to 4.10 and Apache 1.3.33 for a start. -Warren Block * Rapid City, South Dakota USA