Date: Wed, 3 Jun 2009 12:13:39 +0200 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Cc: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>, Chris St Denis <chris@smartt.com> Subject: Re: named: error sending response: not enough free resources Message-ID: <200906031213.39911.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <alpine.BSF.2.00.0906031147460.50769@wojtek.tensor.gdynia.pl> References: <4A25A415.5010502@smartt.com> <200906031145.49209.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <alpine.BSF.2.00.0906031147460.50769@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 03 June 2009 11:48:48 Wojciech Puchar wrote: > >> 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. > > this is extreme case. Not really. The point is that at the time the network card goes from up to down, named spits out this error. If you log named to a different log file then /var/log/messages, you will not see the relation. The reason for changing UP to DOWN can be from a device operating at the 2.4Ghz band when using wireless-g to someone bumping his elbow into the colo's network cable, driver problems to switch failures, etc etc. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906031213.39911.mel.flynn%2Bfbsd.questions>