From owner-freebsd-stable@FreeBSD.ORG Thu Aug 16 18:16:33 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 526F216A46C for ; Thu, 16 Aug 2007 18:16:33 +0000 (UTC) (envelope-from freebsd@violetlan.net) Received: from mail.violetlan.net (ns2.violetlan.net [80.81.242.6]) by mx1.freebsd.org (Postfix) with ESMTP id D4B0213C457 for ; Thu, 16 Aug 2007 18:16:32 +0000 (UTC) (envelope-from freebsd@violetlan.net) Received: from mail.violetlan.net (localhost [127.0.0.1]) by mail.violetlan.net (Postfix) with ESMTP id BFB061144D; Thu, 16 Aug 2007 20:17:49 +0200 (CEST) Received: by mail.violetlan.net (Postfix, from userid 65534) id 892421144C; Thu, 16 Aug 2007 20:17:49 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on scurvy.violetlan.net X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=ham version=3.2.1 Received: from www.violetlan.net (mbali.violetlan.net [10.0.100.150]) by mail.violetlan.net (Postfix) with ESMTP id 4DF641144A; Thu, 16 Aug 2007 20:17:46 +0200 (CEST) Received: from 212.99.207.3 (SquirrelMail authenticated user freebsd@violetlan.net) by www.violetlan.net with HTTP; Thu, 16 Aug 2007 20:16:31 +0200 (CEST) Message-ID: <56041.212.99.207.3.1187288191.squirrel@www.violetlan.net> In-Reply-To: <20070816180710.GA22257@eos.sc1.parodius.com> References: <55620.212.99.207.3.1187285304.squirrel@www.violetlan.net> <20070816180710.GA22257@eos.sc1.parodius.com> Date: Thu, 16 Aug 2007 20:16:31 +0200 (CEST) From: "Reinhold" To: "Reinhold" , freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: apache problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 18:16:33 -0000 Thanks for the reply I'm having some mail problems as well, today is not my day. I'll remove all the stuff you mentioned and change back to 4BSD Will I have to recompile all the ports as well? I don't think its a PF problem because I have used this rule set of mine for a few years with no problems at all, but I'll recheck that just to make sure. Now for the mail problem I'm having its got to do with postfix sending mail from any ip address and not from the one that I want it to, but thats a later problem and on another box, I first want to get this apache thing sorted.. On Thu, August 16, 2007 20:07, Jeremy Chadwick wrote: > On Thu, Aug 16, 2007 at 07:28:24PM +0200, Reinhold wrote: > >> Hi >> > > Hello. First off, you sent mail to the list twice. I don't know why, > but you did. Be patient. :-) > >> I am having some problems with apache22 on my box. What happens is, >> when I'm viewing loads and loads of pages, apache will stop responding >> untill I restart it again. This normally happens when the free memory >> shown by top gets to about +- 100MB. > > I'm guessing that might be due to you using the ULE scheduler in your > kernel. Try switching back to 4BSD and see if that fixes it. > >> I'm also getting this error when I do a gracful restart of apache >> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter [Thu Aug 16 05:12:16 2007] [warn] >> (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter >> >> and in my /boot/loader.conf I have added accf_data_load="YES" >> accf_http_load="YES" > > Remove those. Here's why: > > > The apache rc.d startup script automatically will load accf_http.ko. > I also believe if that fails, Apache will try to load it. From my > experiences kldload/kldunload with accf_* is not very friendly; I've seen > where you can double-load the modules, and where you can't unload the > modules despite nothing using them. If you have them built-in to your > kernel, it gets even worse. > > AFAIK, using accf_data.ko isn't recommended. accf_http.ko on the other > hand is OK. Try not loading accf_data.ko in addition to my above > recommendation (re: 4BSD scheduler). > >> device pf device pflog device pfsync > > Finally, make sure your pf rules aren't doing anything stupid. If > ultimately you think it's a problem with pf rules, unload the pf module > and/or set pf_enable="no" in rc.conf and reboot. If the problem goes away > after that, then you'll know. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ > | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB > | > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >