Error Sending Response Not Enough Free Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] I occasionally get named errors like these in my messages log. I've done a 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 System isn't particularly heavily loaded. Load averages around 0.5, cpu averages about 90% idle, not swapping much. Other messages on this subject suggest a shortage of mbuffs of an issue with the nic driver (the item I read was complaining about fxp, but I have em) so here is the related info. eureka# uname -a FreeBSD eureka 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #1: Mon Feb 25 08:17:08 PST 2008 cstdenis at eureka:/usr/obj/usr/src/sys/EUREKA i386 eureka# named -v BIND 9.3.4-P1 eureka# ifconfig em1 em1: flags=8843 mtu 1500 options=1b *IPs removed* ether 00:30:48:94:0a:31 media: Ethernet 10baseT/UTP status: active eureka# netstat -m 1240/2165/3405 mbufs in use (current/cache/total) 1216/1290/2506/25600 mbuf clusters in use (current/cache/total/max) 1216/150 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) 2742K/3121K/5863K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 8/430/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 999635 requests for I/O initiated by sendfile 276104 calls to protocol drain routines How do I fix this? -- Chris St Denis Programmer SmarttNet (www.smartt.com) Ph: 604-473-9700 Ext. 200 ------------------------------------------- "Smart Internet Solutions For Businesses" Previous message: Flamewar ( was: Sponsoring FreeBSD) Next message: named: error sending response: not enough free resource
question Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Merlin wrote: > I'm not real close up on the config file syntax for 9.2.0, but believe I may > need to set the > size_spec > option. I'm finding the system is running out of resources, and perhaps I > may need to increase? decrease ? the cache size > Mar 16 07:48:03 nanguo named[69]: client 207.173.86.2#53: error sending > response: not enough free resources There is more resources then MBUF's ( which you don't see, to lack. How about the "limit's" for named ? I get : > limit cputime unlimited filesize unlimited datasize 524288 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited descriptors 957 memorylocked unlimited maxproc 478 On https://lists.freebsd.org/pipermail/freebsd-questions/2009-June/199818.html a 4.4 : FreeBSD zap.manet.nu 4.4-STABLE FreeBSD 4.4-STABLE #1: Thu Jan 17 21:27:09 CET 2002 root at zap.manet.nu:/usr/src/sys/compile/ZAP i386 which is funny since my login.conf specifically uses "umlimited' ... A datasize limit of 524288 would stop a nameserver after a while. Sorry about not beeing able to solve your problem, but this is a road to follow. Try : limit datasize unlimited before starting named and see if named can grow above the size it has now. If so then the default https://lists.isc.org/pipermail/bind-users/2002-March/037347.html limits should be changed. ( if you run named as user named, go for an entry for "named" in /etc/login.conf ) /etc/login.conf seems to be a hashed database, cap_mkdb seems to be used to rebuild the database. ( in 4.3 i don't see a hached database at all ) peter h > Perhaps I need the max-cache-size or recurse-clients option, but can't seem > to find out how to set them... > ============================== > This is not caused by lack of MBUFS. > $ netstat -m > 6/400/256000 mbufs in use (current/peak/max): > 6 mbufs allocated to data > 1/200/64000 mbuf clusters in use (current/peak/max) > 500 Kbytes allocated to network (0% of mb_map in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > I'm using FreeBSD 4.5, 512MB RAM, 1Gb CPU. > datasize > The maximum amount of data memory the server may use. The default is > default. This is a hard limit on server memory usage. If the server attempts > to allocate memory in excess of this limit, the allocation will fail, which > may in turn leave the server unable to perform DNS service. Therefore, this > option is rarely useful as a way of limiting the amount of memory used by > the server, but it can be used to raise an operating system data size limit > that is too small by default. If yo
Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ named "error sending response: not enough free resources" NOTE: Please reply off-list as well as I am not subscribed My server (7.2-STABLE) suffered at http://freebsd.1045724.x6.nabble.com/named-quot-error-sending-response-not-enough-free-resources-quot-td3832695.html least two outages Sunday through yesterday after having been up since July (it is a rented dedicated server with my FSBD install). The first time, I was able to log in via remotely, saw a ton of spam apparently abusing a php mail form script (more on that later) filling the /var partition. I purged it, but it still required a reboot as CPU was through the roof. Yesterday morning, error sending I was unable to get into the server at all...pings were very high. I called the provider and got in via KVM over IP. CPU was fine and there wre no full partitions. As I had to catch a flight, I just rebooted it and it was fine. After getting home, I looked in the syslog and see thousands of these: Jan 26 21:50:32 host named[667]: client #57938: error sending error sending response response: not enough free resources Jan 26 21:50:32 host named[667]: client #59830: error sending response: not enough free resources Some googling on this error found a reference to a possible queue limiting problem in pf/qlimit, but the only firewalling I do is a very basic ipfw setup strictly for bruteblock. I am not even sure if this error caused the outage(s) or was caused by them, let alone a fix or workaround. Appreciate any and all clues, especially if you are familiar with this. TIA! James Smallacombe PlantageNet, Inc. CEO and Janitor [hidden email] http://3.am========================================================================= _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[hidden email]" Charles Swiger Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: named "error sending response: not enough free resources" On Jan 27, 2010, at 10:24 AM, James Smallacombe wrote: > NOTE: Please reply off-list as well as I am not subscribed OK. In return, please don't cross-post or multi-post the same question to multiple FreeBSD lists. > My server (7.2-STABLE) suffered at least two outages Sunday through yesterday after having been up since July (it is a rented dedicated server with my FSBD install). The first tim