Bug #2055
closed
ipfw-classifyd: unable to write to divert socket: No buffer space available
0%
Description
I've seen other tickets mentioning this error in the log which were closed. I am still getting these in the logs with current version.
Other tickets mention this is from L7 limiter, which i am using to help block bittorrent traffic.
Please let me know what info you'll require to understand the setup better if you wish. thanks!
verison: 2.0-RELEASE (amd64) built on Tue Sep 13 17:05:32 EDT 2011
enabled l7 bittorrent limiter:- cat /tmp/bittorrentL7limit.l7
bittorrent = action block
- grep "No buffer space" /var/log/system.log | wc -l
4399 << from today.
last pid: 46088; load averages: 0.18, 0.17, 0.09 up 10+23:34:58 11:34:32
85 processes: 1 running, 84 sleeping
Mem: 3981M Active, 2816M Inact, 670M Wired, 21M Cache, 826M Buf, 404M Free
Swap: 16G Total, 120K Used, 16G Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
28056 root 5 44 0 131M 120M nanslp 0 822:56 10.60% ipfw-classifyd
56905 proxy 1 44 0 3668M 3653M kqread 0 120:07 0.78% squid
23176 root 1 44 0 28200K 8356K select 3 24:55 0.00% bsnmpd
Updated by Chris Buechler over 12 years ago
- Target version deleted (
2.0.1)
that's what happens when you push too much traffic through it. Where "too much" varies depending on CPU speed. We would like to see it more scalable at some point.
Updated by Greg Whynott over 12 years ago
interesting. Thanks Chris.
should it be of interest, it is a x3430 @2.4GHz Xeon with 4 gigs in a dell R310.
take care and thanks again.
Updated by Chris Buechler over 8 years ago
- Status changed from New to Closed
the functionality in question doesn't work at all in 2.2.x. Closing this in favor of #4276