From owner-freebsd-stable Mon Feb 5 8:32:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from utterlux.hq.communitconnect.com (unknown [206.28.215.90]) by hub.freebsd.org (Postfix) with ESMTP id A516B37B684 for ; Mon, 5 Feb 2001 08:32:20 -0800 (PST) Received: from localhost (marius@localhost) by utterlux.hq.communitconnect.com (8.11.1/8.11.1) with ESMTP id f15GWKG24009 for ; Mon, 5 Feb 2001 11:32:21 -0500 (EST) (envelope-from marius@mail.communityconnect.com) X-Authentication-Warning: utterlux.hq.communitconnect.com: marius owned process doing -bs Date: Mon, 5 Feb 2001 11:32:20 -0500 (EST) From: Marius X-Sender: marius@utterlux.hq.communitconnect.com To: stable@FreeBSD.ORG Subject: Re: Multiple dropped thttpd connections under high load. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To anyone who has been following my little trials with thttpd 2.17 and FreeBSD 4.x stable, I have one more piece of news. After remaking world, and recompiling our customized thttpd from scratch, we are still not working. In fact, I think it is worse. A ktrace and a truss both indicate that thttpd not surving very long, 10 seconds or less, then the process completely dies. The perl wrapper around thttpd had just been restarting it, so we didn't really notice at first. Obviously that is the source of our dropped connections when the load gets high enough. Since other people are uning thttpd on the 4.x branch, I doubt thttpd itself is to blaime. Perhaps some of the patches to thttpd we added arn't playing well with 4.x, or perhaps somthing has gone wrong on a hardware level on that machine. I might back ot to 3.5-S and see if it exhibits the same behavior. Either way, more testing/checking is called for on my part. I do thank the list for the input they have given me. I certainly don't want to appear as ungrateful. -Marius M. Rex > On Mon, 5 Feb 2001, Roman Shterenzon wrote: > > > On Thu, 1 Feb 2001, Marius wrote: > > > > > > > > I havn't quite gotten around to rebuilding thttpd as people kindly > > > suggested. Actually, the port of thttpd is an older version of thttpd then We > > > are running, so it is not just a matter of rebuilding a port. And > > > secondly, it is a highly customized version of thttpd, patched in several > > > places to work better with out local setup. It is not a trivial matter, > > > but I guess that _is_ what I will have to try next. I have been putting > > > it off. > > > > > > Thank you for the suggestions folks. I'll try to report back when I make > > > some progress for interested parties. (other thttpd users etc.) > > > > I aggree that the problem must be fixed (if it exists). > > But, in your specific situation, in production environment, why not stay > > with RELENG_3 ? > > Are you missing some features (since most bugfixes get MFS4'ed)? > > You can try using some tools like vmstat in order to undertand where's the > > bottleneck and why... > > > > --Roman Shterenzon, UNIX System Administrator and Consultant > > [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message