example.com.ini:
[uwsgi]
uid = www-data
gid = www-data
master
master-as-root
no-orphans
chmod = 666
home = /var/www/%n
pythonpath = /var/www/%n
chdir = /var/www/%n/wallp
daemonize = /var/log/uwsgi/%n.log
pidfile =/var/run/uwsgi/%n.pid
socket = /var/run/uwsgi/%n.socket
processes = 2
env = DJANGO_SETTINGS_MODULE=app.settings
module = django.core.handlers.wsgi:WSGIHandler()
emperor log:
*** Starting uWSGI 0.9.7 (64bit) on [Sat Mar 19 10:28:46 2011] ***
compiled with version: 4.4.3 on 19 March 2011 10:27:48
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 memory page size is 4096 bytes
*** starting uWSGI Emperor ***
c_ui->ui_next = 0x1a23fb0
*** has_emperor mode detected (fd: 6) ***
[uWSGI] getting INI configuration from example.com.ini
c_ui->ui_next = 0x1a1bf80
removed uwsgi instance example.com.ini
*** has_emperor mode detected (fd: 6) ***
[uWSGI] getting INI configuration from example.com.ini
c_ui->ui_next = 0x1a1c0c0
removed uwsgi instance example.com.ini
*** has_emperor mode detected (fd: 6) ***
[uWSGI] getting INI configuration from example.com.ini
c_ui->ui_next = 0x1a1bf80
removed uwsgi instance example.com.ini
*** has_emperor mode detected (fd: 6) ***
[uWSGI] getting INI configuration from example.com.ini
vassal log:
*** Starting uWSGI 0.9.7 (64bit) on [Sat Mar 19 10:28:49 2011] ***
compiled with version: 4.4.3 on 19 March 2011 10:27:48
writing pidfile to /var/run/uwsgi/example.com.pid
your memory page size is 4096 bytes
uwsgi socket 0 bound to UNIX address /var/run/uwsgi/example.com.socket fd 8
Python version: 2.6.5 (r265:79063, Apr 16 2010, 14:15:55) [GCC 4.4.3]
Setting PythonHome to /var/www/example.com...
Python main interpreter initialized at 0xc72d20
your server socket listen backlog is limited to 100 connections
*** Operational MODE: preforking ***
added /var/www/example.com to pythonpath.
WSGI application 0 (SCRIPT_NAME=) ready on interpreter 0xc72d20 (default
app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 31510)
spawned uWSGI worker 1 (pid: 31512, cores: 1)
spawned uWSGI worker 2 (pid: 31513, cores: 1)
*** Starting uWSGI 0.9.7 (64bit) on [Sat Mar 19 10:28:52 2011] ***
compiled with version: 4.4.3 on 19 March 2011 10:27:48
writing pidfile to /var/run/uwsgi/example.com.pid
your memory page size is 4096 bytes
uwsgi socket 0 bound to UNIX address /var/run/uwsgi/example.com.socket fd 8
Python version: 2.6.5 (r265:79063, Apr 16 2010, 14:15:55) [GCC 4.4.3]
Setting PythonHome to /var/www/example.com
Python main interpreter initialized at 0x1d82d20
your server socket listen backlog is limited to 100 connections
*** Operational MODE: preforking ***
added /var/www/example.com to pythonpath
WSGI application 0 (SCRIPT_NAME=) ready on interpreter 0x1d82d20
(default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 31526)
spawned uWSGI worker 1 (pid: 31527, cores: 1)
spawned uWSGI worker 2 (pid: 31528, cores: 1)
*** Starting uWSGI 0.9.7 (64bit) on [Sat Mar 19 10:28:55 2011] ***
compiled with version: 4.4.3 on 19 March 2011 10:27:48
writing pidfile to /var/run/uwsgi/example.com.pid
your memory page size is 4096 bytes
uwsgi socket 0 bound to UNIX address /var/run/uwsgi/example.com.socket fd 8
Python version: 2.6.5 (r265:79063, Apr 16 2010, 14:15:55) [GCC 4.4.3]
Setting PythonHome to /var/www/example.com
Python main interpreter initialized at 0x2244d20
your server socket listen backlog is limited to 100 connections
*** Operational MODE: preforking ***
added /var/www/example.com to pythonpath.
WSGI application 0 (SCRIPT_NAME=) ready on interpreter 0x2244d20
(default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 31539)
spawned uWSGI worker 1 (pid: 31541, cores: 1)
spawned uWSGI worker 2 (pid: 31542, cores: 1)
lost connection with my emperor !!!
SIGINT/SIGQUIT received...killing workers
goodbye to uWSGI.
lost connection with my emperor !!!
SIGINT/SIGQUIT received...killing workers
goodbye to uWSGI.
lost connection with my emperor !!!
SIGINT/SIGQUIT received...killing workers
goodbye to uWSGI.
19.03.2011 08:28, Roberto De Ioris ?????:
> I have same problem with 0.9.7 version of uwsgi - emperor keeps
> restarting vassals with file sockets.
>
Hi, can you post all the configurations (vassal included) and the
loglines ?
Thanks a lot
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
