FC6 - ping: sendmsg - no more space in buffer

[rylan76]

I'm getting random loss of connectivity from my box - FC6 with 2.6.18.1 kernel version. I set up a constant ping and at the tims when my connection goes down I see the above message in the ping sequence.

64 bytes from 85.10.213.103: icmp_seq=360 ttl=242 time=1072 ms
64 bytes from 85.10.213.103: icmp_seq=361 ttl=242 time=1170 ms
64 bytes from 85.10.213.103: icmp_seq=362 ttl=242 time=1078 ms
64 bytes from 85.10.213.103: icmp_seq=363 ttl=242 time=958 ms
64 bytes from 85.10.213.103: icmp_seq=364 ttl=242 time=1125 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

I've already done this to attempt to increase by buffer space:

echo 98886080 > /proc/sys/net/core/wmem_max
echo 98886080 > /proc/sys/net/core/rmem_max
echo 98886080 > /proc/sys/net/core/wmem_default
echo 98886080 > /proc/sys/net/core/rmem_default

This seems to sometimes make the time between failures increase, other times it seems to have no effect at all.

How can I fix this

ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

issue? IS it fixable at all? I've been googling this for several days, but nobody seems to be able to solve this once it crops up - several posts about it just deadend.

Which buffer is being referred to? How can I make this buffer bigger? Is it something else wrong somewhere (i. e. the buffer is not flushing when it should?)

ANY help appreciated!

Thanks
__________________
Stefan Viljoen

[rylan76]

Hi guys

Just thought I'd report that it seems I've got this mitigated further or maybe licked in total!

It seems the buffer overflows I was experiencing was caused by a too long transmission queue length. I've changed the transmission queue length to 500 instead of the default 1000 by doing:

/sbin/ifconfig eth0 169.254.255.20 netmask 255.255.255.0 broadcast 169.254.255.255 txqueuelen 500 up

Now, if I run ifconfig I no longer have dropped packets:

eth0 Link encap:Ethernet HWaddr 00:16:E6:5D:F3:65
inet addr:169.254.255.20 Bcast:169.254.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1701246 errors:0 dropped:0 overruns:0 frame:0
TX packets:1135670 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:2447542857 (2.2 GiB) TX bytes:100667936 (96.0 MiB)
Interrupt:177 Base address:0x9000

Previously I had dropped packets indicated with a queue length of 1000. For the record, this is on a Gigabyte GA945PL-S3 motherboard with FC6 with a custom compiled 2.6.18.1 kernel with the

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)

NIC as indicated by lspci. I'm running the RealTek Linux driver for this card.

I further also massively increased certain buffersizes that were autotuned by the kernel. I've not tested if the queue length was the deciding factor (it works, so I want to leave it as it is!) but I also did this:

echo 98886080 > /proc/sys/net/core/wmem_max
echo 98886080 > /proc/sys/net/core/rmem_max
echo 98886080 > /proc/sys/net/core/wmem_default
echo 98886080 > /proc/sys/net/core/rmem_default
echo 32767 > /proc/sys/net/core/optmem_max
echo 256 > /proc/sys/net/core/somaxconn
echo 2000 > /proc/sys/net/core/netdev_max_backlog

echo 0 > /proc/sys/net/ipv4/tcp_timestamps
echo 1 > /proc/sys/net/ipv4/tcp_sack
echo 1 > /proc/sys/net/ipv4/tcp_window_scaling

echo 26244 786432 1048576 > /proc/sys/net/ipv4/tcp_mem
echo 43960 4194304 8194304 > /proc/sys/net/ipv4/tcp_rmem
echo 43960 4194304 8194304 > /proc/sys/net/ipv4/tcp_wmem

Hope this helps somebody else?

[rylan76]

NOT Solved

Its doing it again...

Getting desperate. Anyhow...

[stevea]

Please post your problem to a single thread.

[bob]

Thread Closed - Please don't double post