Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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'm trying to monitor uSWGI via Nagios, but according to uWSGI I have specified an invalid socket.

The socket path I got from the JSON config file which also says chmod-socket: 666 so I have a hunch that the problem is permission based. The socket file is owned by www-data who I don't want to tinker with, so any other ways?

uwsgi --socket=/tmp/app.sock --nagios
detected binary path: /usr/local/bin/uwsgi
UWSGI UNKNOWN: you have specified an invalid socket

ls -l /tmp/app.sock
srw-rw-rw- 1 www-data www-data 0 2012-10-26 17:00 /tmp/app.sock
share|improve this question
up vote 0 down vote accepted

which uWSGI version ? the "detected binary path" message should not appear, so you may be using some older release with some kind of bug.

share|improve this answer
uwsgi --version says uWSGI 1.0.4. apt-cache show uwsgi says Version: on this Ubuntu 11.10. I guess I should upgrade manually. – webjay Oct 28 '12 at 10:10
After I upgraded to Ubuntu 12.04.1 LTS it doesn't show detected binary path – webjay Nov 5 '12 at 12:38

Your Answer


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

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