View Full Version : No buffer space available
I'm getting the error 'No buffer space available' in /var/log/messages when the server reaches ~980 connections.
Its running an irc server and a firewall.
I know its not the ircd because every tcp service stops accepting new connections till there is a drop in connections but i cant figure out what to change to allow more connections.
googled your problem and this is what i found.
"arp -a showed a lot of junk.. many many hostsnames associated to our router MAC addr.
/etc/sysconfic/network had a wrong gateway configuration. Fixed!"
maybe that will help?
hm arp -a doesnt show anything
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:125071 errors:0 dropped:0 overruns:0 frame:0
TX packets:125071 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7687655 (7.3 Mb) TX bytes:7687655 (7.3 Mb)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.0
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:6842482 errors:0 dropped:0 overruns:0 frame:0
TX packets:7115954 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:578685124 (551.8 Mb) TX bytes:1635031230 (1559.2 Mb)
thats probably not right either is it ?
the gateway is set to 191.255.255.1 but the inet ip is something really different. 208.53.170.x
this was the default setup which the server came with.
have your tried restarting named, or even the server (dont if you havent... id only recommend as last resort)
MQ-James
12-15-2004, 22:02
you have to remember for busy servers a VDS is not the correct option, to get best performance, spend a little bit more and get a cheap ass server.
just shut down named, giving it a go again
there isnt much running on the machine besides iptables and the ircd.
but 2 nic's with 127.0.0.1 as ip isnt a good thing is it ?
you have to remember for busy servers a VDS is not the correct option, to get best performance, spend a little bit more and get a cheap ass server.
wasent aware that he was on vds. kinda forgot about the forum topic :rolleyes:
however i do agree!
just shut down named, giving it a go again
there isnt much running on the machine besides iptables and the ircd.
but 2 nic's with 127.0.0.1 as ip isnt a good thing is it ?
thats just like localhost. i assume that they both have assigned ips (both internel and external of the net)
you have to remember for busy servers a VDS is not the correct option, to get best performance, spend a little bit more and get a cheap ass server.
yea i know but i wouldnt call this busy.
vnet0:0 is the nic with the actual inet ip on it, lo and vnet0 both have 127.0.0.1
mikron15
12-15-2004, 22:45
type df and paste output
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vzfs 20971520 940600 20030920 5% /
the thing isnt even 24 hours old ;)
MQ-James
12-15-2004, 22:49
the way the NICs work in the VDS is wierd, normally lo = 127.0.0.1 and eth0 is your ip (or vnet0 should be) it's wierd...
vBulletin® v3.7.3, Copyright ©2000-2009, Jelsoft Enterprises Ltd.