Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2004 13:12:23 -0600
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Brent Bailey <misterb@bmyster.com>
Cc:        questions@freebsd.org
Subject:   Re: UDP errors and syslog & BSD
Message-ID:  <20040120191223.GA362@dan.emsphone.com>
In-Reply-To: <1311.66.63.97.2.1074618159.squirrel@new.host.name>
References:  <1311.66.63.97.2.1074618159.squirrel@new.host.name>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 20), Brent Bailey said:
> Im using Frebsd as a syslog server at work. Everything seemed to be ok
> untill i decided to run
> "netstat -s -p udp"
> as part of my nitely reporting. there are 5 routers pointed at this syslog
> server so it seen ALOT of UDP traffic
> 
> ive noticed the following :
> UDP stats:
> 
> the errors im concerned about are
> 5775699 dropped due to full socket buffers

I think this means that a process isn't reading data fast enough from
its socket.  It's not a global buffer shortage (you'd get lots of
errros in /var/log/mesages in that case).  You can raise the buffer
size for a specific socket by calling setsockopt() with the SO_RCVBUF
option.  You can change the systemwide default with the
net.inet.udp.recvspace sysctl.
 
> and
>  319427 dropped due to no socket

This just counts the number of packets sent to UDP ports where there
was no listening process.  Say for example you had to stop and restart
syslogd, any syslog packets received while it was down would increment
that counter.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040120191223.GA362>