From owner-freebsd-questions@FreeBSD.ORG Tue Jun 2 23:17:28 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AE4E106564A for ; Tue, 2 Jun 2009 23:17:28 +0000 (UTC) (envelope-from chris@smartt.com) Received: from barium.smartt.com (mailout3.smartt.com [69.67.187.28]) by mx1.freebsd.org (Postfix) with ESMTP id 62A168FC16 for ; Tue, 2 Jun 2009 23:17:28 +0000 (UTC) (envelope-from chris@smartt.com) Received: from [69.31.174.220] (unknown [69.31.174.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by barium.smartt.com (Postfix) with ESMTPSA id 931F810E52B; Tue, 2 Jun 2009 16:17:48 -0700 (PDT) Message-ID: <4A25B309.7000701@smartt.com> Date: Tue, 02 Jun 2009 16:17:29 -0700 From: Chris St Denis User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Wojciech Puchar References: <4A25A415.5010502@smartt.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-questions@freebsd.org" Subject: Re: named: error sending response: not enough free resources X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 23:17:28 -0000 Wojciech Puchar wrote: >> lot of searching and have found others with similar problems, but no >> solutions. >> >> named[69750]: client *ip removed*: error sending response: not >> enough free resources >> named[69750]: client *ip removed*: error sending response: not >> enough free resources >> named[69750]: client *ip removed*: error sending response: not >> enough free resources >> named[69750]: client *ip removed*: error sending response: not >> enough free resources >> named[69750]: client *ip removed*: error sending response: not >> enough free resources > > quite misleading message, but the problem is that named want to send > UDP packet and get's error from kernel. > > > possible reasons > - your firewall rules are the cause - check it. Nope eureka# ipfw list 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65534 allow ip from any to any 65535 deny ip from any to any > - your network card produce problems (REALLY i have that case) I have had this kind of error on multiple servers over the years, so i don't think it's a hardware problem. > - the network/LAN named tries to sent UDP packet is somehow flooded. Dns is probably fairly busy. It's the primary authorative dns for some busy domains. Is there a setting I can do to increase the limits of UDP packets to keep it from causing problems? The server is approaching it's 10 mbps interface speed during peak hours, I may need to upgrade it to 100mbps. > > i experienced all 3 cases. last is of course easiest to detect. > >> >> Other messages on this subject suggest a shortage of mbuffs of an >> issue with > > no you are fine with mbufs, memory etc.. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" -- Chris St Denis Programmer SmarttNet (www.smartt.com) Ph: 604-473-9700 Ext. 200 ------------------------------------------- "Smart Internet Solutions For Businesses"