7

I found my website unresponsive and I see a ton of

*** uWSGI listen queue of socket "0.0.0.0:5002" (fd: 3) full !!! (101/100) ***
*** uWSGI listen queue of socket "0.0.0.0:5002" (fd: 3) full !!! (101/100) ***
*** uWSGI listen queue of socket "0.0.0.0:5002" (fd: 3) full !!! (101/100) ***

Am I being ddosed? What is going on?

0

The application is currently busy processing 100 requests. It is rejecting further requests.

Maybe you're being DDoS, maybe the application is very slow or blocked, maybe there are too many users and too little hardware resources for the application. Can't tell which case this is without further information.

Look into this. I don't know what WSGI tools you are using to give you the exact settings for your environment.

Increase the number of workers/processes. Each worker can process one request at a time. Multiple workers will be able to process multiple requests in parallel, usually 1 worker per core.

Increase the listening queue to 500. A moderate amount of users could generate bursts of a hundred requests at times. It takes a bigger queue to handle that amount of traffic, assuming there is enough resources to process these requests shortly.

Check your application. Make sure it's working and efficient. There are a hundred requests pending, is this normal? The application might be slow, hanging or lacking resources.

-2

Add uwsgi config:

processes = 8
threads = 4
max-fd = 120000
listen = 1024
  • 6
    You should include an explanation of what this does. – kasperd Nov 16 '15 at 12:19
  • 1
    This is not a solution, simply a patch. The problem is likely to be in the application logic. – lorenzog Nov 25 '15 at 14:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.