I'm trying to ping a remote host, but I get an error.
# ping 192.168.80.1 PING 192.168.80.1 (192.168.80.1): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ^C --- 192.168.80.1 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss
It works for other hosts:
# ping 192.168.16.1 PING 192.168.16.1 (192.168.16.1): 56 data bytes 64 bytes from 192.168.16.1: icmp_seq=0 ttl=254 time=0.442 ms 64 bytes from 192.168.16.1: icmp_seq=1 ttl=254 time=0.402 ms ^C --- 192.168.16.1 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.402/0.422/0.442/0.020 ms #
The message "No buffer space available" seems to indicate some sort of memory error. And indeed, when I check with Netstat, the "mbuf clusters" number looks VERY wrong:
# netstat -m 11780 mbufs in use 4294966716/32768 mbuf clusters in use (current/max) 0/3/6656 sfbufs in use (current/peak/max) 1785 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines
What is going on here? Is there away to fix this without downtime, or do I need to reboot the host or restart the network interface?