This is my first post this list.  I am a fairly new uwsgi/nginx user and
want to replace apache with the nginx/uwsgi combination on my server.

On Debian I have

ii  uwsgi                      1.9.17.1-5
amd64        fast, self-healing application container server
ii  uwsgi-core               1.9.17.1-5
amd64        fast, self-healing application container server (core)
ii  uwsgi-emperor          1.9.17.1-5
amd64        fast, self-healing application container server (emperor
scripts)
ii  uwsgi-plugin-python   1.9.17.1-5
amd64        Python WSGI plugin for uWSGI
ii  nginx-common          1.4.3-2
all          small, powerful, scalable web/proxy server - common files
ii  nginx-full                  1.4.3-2
amd64        nginx web/proxy server (standard version)

Without emperor mode I have no problem and the system is working using the
following socket configuration in /etc/nginx/sites-enabled/web2py

uwsgi_pass      unix:///var/run/uwsgi/app/web2py/socket;

and with the following uwsgi-configuration:

<uwsgi>
    <socket>/var/run/uwsgi/app/web2py/socket</socket>
    <pythonpath>/home/www-data/web2py/</pythonpath>
    <plugins>python</plugins>
    <mount>/=wsgihandler:application</mount>
    <master/>
    <processes>4</processes>
    <harakiri>60</harakiri>
    <reload-mercy>8</reload-mercy>
    <cpu-affinity>1</cpu-affinity>
    <stats>/var/run/uwsgi/app/web2py/stats.socket</stats>
    <max-requests>2000</max-requests>
    <limit-as>512</limit-as>
    <reload-on-as>256</reload-on-as>
    <reload-on-rss>192</reload-on-rss>
    <uid>www-data</uid>
    <gid>www-data</gid>
    <no-orphans/>
</uwsgi>


Then I installed uwsgi-emperor and changed the default
/etc/uwsg-emperor/emperor.ini:

# vassals directory
#emperor = /etc/uwsgi-emperor/vassals
emperor = /etc/uwsgi/apps-enabled/
UWSGI_VASSAL_SOCKET=/var/run/uwsgi/app/%n/socket --emperor $emperor


In /var/log/uwsgi/emperor.log I see:

[uWSGI] parsing config file web2py.xml
*** Starting uWSGI 1.9.17.1-debian (64bit) on [Wed Nov 27 09:46:49 2013] ***
compiled with version: 4.8.1 on 26 September 2013 23:59:28
os: Linux-3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13)
nodename: artikel
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 4
current working directory: /etc/uwsgi/apps-enabled
detected binary path: /usr/bin/uwsgi-core
your processes number limit is 62280
limiting address space of processes...
your process address space limit is 536870912 bytes (512 MB)
your memory page size is 4096 bytes
 *** WARNING: you have enabled harakiri without post buffering. Slow upload
could be rejected on post-unbuffered $
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
bind(): No such file or directory [core/socket.c line 185]
Wed Nov 27 09:46:49 2013 - [emperor] removed uwsgi instance web2py.xml

and there are no sockets for nginx to connect to :(

So how do I get this working?

BTW I have search core/socket.c with apt-file and had now results.  From
which package is that supposed to come?

Regards
Johann


-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to