From owner-freebsd-questions@FreeBSD.ORG Wed Jun 3 09:45:52 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 63EE4106564A for ; Wed, 3 Jun 2009 09:45:52 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 31B108FC12 for ; Wed, 3 Jun 2009 09:45:51 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id D4D4B7E837; Wed, 3 Jun 2009 01:45:50 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Wed, 3 Jun 2009 11:45:48 +0200 User-Agent: KMail/1.11.3 (FreeBSD/8.0-CURRENT; KDE/4.2.3; i386; ; ) References: <4A25A415.5010502@smartt.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906031145.49209.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Wojciech Puchar , Chris St Denis 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: Wed, 03 Jun 2009 09:45:52 -0000 On Wednesday 03 June 2009 00:46:20 Wojciech Puchar wrote: > > 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. > - your network card produce problems (REALLY i have that case) > - the network/LAN named tries to sent UDP packet is somehow flooded. - the network card changes from UP to DOWN state at the time of the error See that a lot running local resolver on a wireless-g card and turning on the microwave. -- Mel