Fix – Siege aborted due to excessive socket failure

Published by shyam jos on

I was benchmarking a web app using Siege, When I increased the concurrency to 300 RPS Siege started throwing an error.


[error] socket: -1331792128 address is unavailable.: Cannot assign requested address
[error] socket: -1306614016 address is unavailable.: Cannot assign requested address
[error] socket: -1289828608 address is unavailable.: Cannot assign requested address
[error] socket: -1298221312 address is unavailable.: Cannot assign requested address
[error] socket: -1231079680 address is unavailable.: Cannot assign requested address
done.
siege aborted due to excessive socket failure; you
can change the failure threshold in $HOME/.siegerc

After some digging on google, I have found that this error is due to the low value set in a Linux parameter called SOMAXCONN( socket’s listen queue). The default value is 128 which is very low for a high traffic server.

How to increase SOMAXCONN Value

open /etc/sysctl.conf and add below line

  net.core.somaxconn=1024   

Enter below command to take effect new changes

  sysctl -p   
Categories: Tutorials

shyam jos

My name is Shyam Jos, I am a passionate Linux system administrator from Kochi, India. I am a strong advocate of using Linux and Open-Source software.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.