E
E
Eugene2015-10-31 02:56:48
Django
Eugene, 2015-10-31 02:56:48

How to fix uWSGI bug in virtual environment?

Good afternoon. Please help me understand what is the problem. I'm learning django and decided to figure out how to upload to the production server. acted according to this manual habrahabr.ru/post/226419 . At the stage nginx + uWSGI + test.py failed. The site does not want to work.
What did you do. Reinstalled uWSGI, installed libpcre3. Tried to smoke forums, but found nothing worthwhile.

(site.com)[email protected]:/var/www/admin/www/site.com/drago# uwsgi --socket drago.sock --module drago.wsgi --chmod-socket=664
*** Starting uWSGI 2.0.11.2 (64bit) on [Sat Oct 31 02:55:07 2015] ***
compiled with version: 4.7.2 on 31 October 2015 02:00:39
os: Linux-2.6.32-042stab111.11 #1 SMP Tue Sep 1 18:19:12 MSK 2015
nodename: servs
machine: x86_64
clock source: unix
detected number of CPU cores: 1
current working directory: /var/www/admin/www/site.com/drago
detected binary path: /var/www/admin/www/site.com/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
*** WARNING: you are running uWSGI without its master process manager ***
your processes number limit is 3093581
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address drago.sock fd 3
Python version: 2.7.3 (default, Mar 13 2014, 11:26:58)  [GCC 4.7.2]
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x1ab4ca0
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 72768 bytes (71 KB) for 1 cores
*** Operational MODE: single process ***
WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x1ab4ca0 pid: 5940 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI worker 1 (and the only) (pid: 5940, cores: 1)

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
alpy, 2015-11-02
@alpy

in the manual
and you
those. You acted completely according to the manual. Check settings and logs. Also check the owner and groups of the processes, because with such permissions on the socket it is not a fact that nginx can write to it.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question