linux - Siege aborted due to excessive socket failure -


i have encountered problem whilst trying run off following cmd siege on mac os x 10.8.3.

siege -d1 -c 20 -t2m -i -f -r10 urls.txt 

the output siege following:

** siege 2.74 ** preparing 20 concurrent users battle. server under siege... done. siege aborted due excessive socket failure; can change failure threshold in $home/.siegerc  transactions:                  0 hits availability:               0.00 % elapsed time:              27.04 secs data transferred:           0.00 mb response time:              0.00 secs transaction rate:           0.00 trans/sec throughput:             0.00 mb/sec concurrency:                0.00 successful transactions:           0 failed transactions:            1043 longest transaction:            0.00 shortest transaction:           0.00  file: /usr/local/var/siege.log can disable annoying message editing .siegerc file in home directory; change directive 'show-logfile' false. 

the problem may run out of ephemeral ports. remedy that, either expand number of ports use, or reduce duration ports stay in time_wait, or both.

expand usable ports:

check current setting:

$ sudo sysctl net.inet.ip.portrange.hifirst

net.inet.ip.portrange.hifirst: 49152

set lower expand window:

$ sudo sysctl -w net.inet.ip.portrange.hifirst=32768

net.inet.ip.portrange.hifirst: 49152 -> 32768

(hilast should @ max, 65536)

reduce maximum segment lifetime

$ sudo sysctl -w net.inet.tcp.msl=1000

net.inet.tcp.msl: 15000 -> 1000


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -