Date: Wed, 3 Jun 2009 00:46:20 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Chris St Denis <chris@smartt.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: named: error sending response: not enough free resources Message-ID: <alpine.BSF.2.00.0906030041470.45551@wojtek.tensor.gdynia.pl> In-Reply-To: <4A25A415.5010502@smartt.com> References: <4A25A415.5010502@smartt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. - your network card produce problems (REALLY i have that case) - the network/LAN named tries to sent UDP packet is somehow flooded. 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..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0906030041470.45551>