From owner-freebsd-current@FreeBSD.ORG Fri Feb 21 09:09:10 2014 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB2D6B6; Fri, 21 Feb 2014 09:09:10 +0000 (UTC) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D94F13A1; Fri, 21 Feb 2014 09:09:10 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id s1L98ogE055966; Fri, 21 Feb 2014 01:08:54 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201402210908.s1L98ogE055966@gw.catspoiler.org> Date: Fri, 21 Feb 2014 01:08:50 -0800 (PST) From: Don Lewis Subject: Re: netstat: sysctl: net.route.0.0.dump.0: Cannot allocate memory To: ianf@clue.co.za In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Feb 2014 09:09:10 -0000 On 21 Feb, Ian FREISLICH wrote: > Hiroki Sato wrote: >> ia> While recieving my routing table I used to be able to check how far >> ia> it got by counting the output netstat -rn. It takes about 2 seconds >> ia> to recieve the routes from my route-server, but over a minute to >> ia> update the kernel routing table. >> ia> >> ia> I'm now getting this error until zebra completes route insertion. >> ia> >> ia> [firewall1.jnb1] ~ $ netstat -rn |wc -l >> ia> netstat: sysctl: net.route.0.0.dump.0: Cannot allocate memory >> ia> 1 >> ia> [firewall1.jnb1] ~ $ netstat -rn |wc -l >> ia> 480446 >> >> Perhaps does the attached patch fix this? > > Sadly, not. Maybe you are running into the wired page limit. Try bumping up the value of the sysctl vm.max_wired knob.