Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have uWSGI set up through supervisor on a ubuntu 12.04 box and lately I noticed that when trying to tail the logs (all the logs in that user account) I get message that too many files opened , uWSGI is running as a not root user, I changed the hard and soft limit for this user and rebooted the machine and that fixed the issue. This box has just uwsgi running and my code deployment process stop supervisor which sends a INT signal to the uwsgi process and then start it after performing some operations. I want to conform that sending INT does make uWSGI close the files it has opened over time?

If not what is a better way to stop uWSGI so that it takes care of its opened files?

uWSGI docs uWSGI Docs says that SIGHUP would reload the server and would close the files it has opened but my requirements are stopping and starting uwsgi.

supervisor-uwsgi section

command=uwsgi --ini abcd.ini --gevent 200

Any thoughts please?

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.