Page 1 of 1

ping - connect: No buffer space available

Posted: 2015/11/25 04:07:05
by sfool3
Hello~

I'm having problem below in Centos server. Server installed PBX S/W.

[root@server1 ~]# ping 10.0.1.34
connect: No buffer space available

I re-installed CentOS and SW in server. Moreover it is re-installed to the VMWare to prevent an H/W error.
So problem with network interfaces unstable operations still occurs.

Thanks for any help.

-------------------------------------------------------
CentOS
version : 5.4
kernel : Linux scm_act 2.6.18-164.11.1.el5PAE
HW : 4G mem, 4 eth port, Dell server
-------------------------------------------------------

Re: ping - connect: No buffer space available

Posted: 2015/11/25 08:58:35
by TrevorH
Why why why would you install 5.4 on a fresh install?! 5.4 was released in 2009 so is now over 6 years old and has 6 years worth of security bugs in it. If you must use 5.x then at least use 5.11.

Re: ping - connect: No buffer space available

Posted: 2015/11/25 17:00:47
by aks
I don't know what SW is....
You don't say if it's wired, wireless or something like 3G etc...
I'd guess that there is not enough write buffer space to send (/proc/sys/net/core/wmem_max)
I'd suggest running an strace on your ping command....

Re: ping - connect: No buffer space available

Posted: 2015/12/03 11:30:52
by yogeshpujari
To fix this, I had to increase the ARP table space. To do this permanently:
Edit /etc/sysctl.conf and add the following lines:
net.ipv4.neigh.default.gc_thresh3 = 4096
net.ipv4.neigh.default.gc_thresh2 = 2048
net.ipv4.neigh.default.gc_thresh1 = 1024

# sysctl -p

For a temporary fix:
echo 1024 > /proc/sys/net/ipv4/neigh/default/gc_thresh1
echo 2048 > /proc/sys/net/ipv4/neigh/default/gc_thresh2
echo 4096 > /proc/sys/net/ipv4/neigh/default/gc_thresh3