From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 04:56:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87E3C16A60C for ; Fri, 5 Mar 2004 04:56:01 -0800 (PST) Received: from mail.komquats.com (h24-108-145-252.gv.shawcable.net [24.108.145.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09A9343D39 for ; Fri, 5 Mar 2004 04:56:01 -0800 (PST) (envelope-from Cy.Schubert@komquats.com) Received: from cwsys.cwsent.com (cwsys [10.1.1.1]) by mail.komquats.com (Postfix) with ESMTP id 2189A5A82F for ; Fri, 5 Mar 2004 04:56:00 -0800 (PST) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.12.10/8.12.8) with ESMTP id i25Ctx0f030827 for ; Fri, 5 Mar 2004 04:55:59 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Resent-Message-Id: <200403051255.i25Ctx0f030827@cwsys.cwsent.com> Message-Id: <200403051255.i25Ctx0f030827@cwsys.cwsent.com> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Don Lewis In-Reply-To: Your message of "Thu, 04 Mar 2004 23:00:08 PST." <200403050700.i257087E006207@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 2004 04:54:58 -0800 Sender: Cy.Schubert@komquats.com Resent-To: freebsd-current@freebsd.org Resent-Date: Fri, 05 Mar 2004 04:55:59 -0800 Resent-From: Cy Schubert Subject: Re: sysctl spinning (was: Re: ps Causes Hard Hang) (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2004 12:56:01 -0000 In message <200403050700.i257087E006207@gw.catspoiler.org>, Don Lewis writes: > On 4 Mar, Cy Schubert wrote: > > So far so good, the problem appears to be fixed. I'll leave it in > > production tonight. If I have any fallout tonight, I'll notify you tomorrow > > > morning. > > I'm somewhat suprised that you haven't seen any other signs of breakage. > I'd expect to see either some sysctl calls that fail with an ENOMEM > error, or the continuation of the looping problem, depending on which > limit gets hit first. > I'm only seeing this problem on only one of my systems, the firewall, which has the smallest memory configuration (48 MB). The problem doesn't occur immediately after reboot but does occur a few minutes later when the squid proxy finally comes up. So far I'm seeing an uptime of: 4:45AM up 8 mins, 1 user, load averages: 0.07, 0.64, 0.46 I'll watch it for the rest of the day. Interestingly the other four systems running -CURRENT, three here at home and my desktop UNIX system at work (sorry, my prod systems at work still run -STABLE) have not exhibited any symptoms. As far as any other symptoms are concerned, it never stayed up long enough for me to notice any other symptoms. What prompted me to notice is that my Internet connectivity disappeared because my firewall was down. As I hardly log into the box (it normally just... happily runs), I never really noticed anything else. I only log into it to maintain it, the rest of it's pretty much automated. So, no, I didn't notice any other symptoms as it just stopped working after the upgrade. I will let you know by tonight how it fares. So far so good and this is a good sign so far. Cheers, -- Cy Schubert http://www.komquats.com/ BC Government . FreeBSD UNIX Cy.Schubert@osg.gov.bc.ca . cy@FreeBSD.org http://www.gov.bc.ca/ . http://www.FreeBSD.org/