Networking: netstat -su: packet receive errors, receive buffer errors — UDP datagrams dropped by a full socket buffer
UDP packets arrive faster than the application reads them, so the kernel throws the extras away.
packet receive errors UDPreceive buffer errorsUDP packets dropped RcvbufErrorsUdp: InErrors Meaning
UDP has no flow control: when the socket buffer is full, RcvbufErrors rises and data is lost (logs, metrics, VoIP, DNS, syslog). Read faster or in more threads, increase net.core.rmem_max and the socket's SO_RCVBUF, and reduce the sender's rate.
Common causes
- Receiver slower than the sender
- Small
rmem_default/rmem_max - Burst traffic (syslog, StatsD, video)
- Single-threaded reader
- CPU starvation
⚡ Quick fix
- Check counters:
nstat -az UdpRcvbufErrors - Raise
net.core.rmem_maxand set SO_RCVBUF - Add reader threads or slow the sender
Detailed fix by platform
Linux
- bash
nstat -az UdpInErrors UdpRcvbufErrors sudo sysctl -w net.core.rmem_max=26214400 net.core.rmem_default=26214400
How to diagnose
- RcvbufErrors — Rising?
- Buffer — Large enough?
- Reader — Fast enough?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- arp -a shows (incomplete) Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
- High TCP retransmissions / packet loss Networking: netstat -s: segments retransmitted / Wireshark: TCP Retransmission, TCP Dup ACK — packet loss on the path
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026