> CONSOLE 1: > > vint@vgreck:/var/data/work/mainroot/cross-ads$ uwsgi --master --protocol > http --socket :8000 --module=util.transact.publisher > --callable=ControlRequest --spooler run/web/spool/ --show-config > > ;uWSGI instance configuration > [uwsgi] > master = true > protocol = http > socket = :8000 > module = util.transact.publisher > callable = ControlRequest > spooler = run/web/spool/ > show-config = 1 > ;end of configuration > > > [uwsgi] > master = true > protocol = http > socket = :8000 > module = util.transact.publisher > callable = ControlRequest > spooler = run/web/spool/ > show-config = 1 > ;end of configuration > > *** Starting uWSGI 0.9.8.3 (32bit) on [Wed Aug 24 12:01:27 2011] *** > compiled with version: 4.5.2 on 19 August 2011 15:13:24 > your memory page size is 4096 bytes > uwsgi socket 0 inherited INET address :8000 fd 3 > Python version: 2.7.1+ (r271:86832, Apr 11 2011, 18:30:20) [GCC 4.5.2] > Python main interpreter initialized at 0x9d73098 > your server socket listen backlog is limited to 100 connections > *** Operational MODE: single process *** > WSGI application 0 (SCRIPT_NAME=) ready on interpreter 0x9d73098 pid: 6697 > (default app) > *** uWSGI is running in multiple interpreter mode *** > gracefully (RE)spawned uWSGI master process (pid: 6697) > spawned the uWSGI spooler on dir > /var/data/work/mainroot/cross-ads/run/web/spool with pid 6762 > spawned uWSGI worker 1 (pid: 6763, cores: 1) > SIGINT/SIGQUIT received...killing workers... > killed the spooler with pid 6762 > subprocess 6762 exited by signal 9 > goodbye to uWSGI. > > vint@vgreck:/var/data/work/mainroot/cross-ads$ ps -fA | grep uwsgi > vint 6710 1 33 12:00 pts/3 00:00:21 uwsgi --master --protocol > http --socket :8000 --module=util.transact.publisher > --callable=ControlRequest --spooler run/web/spool/ --show-config > vint 6768 3996 0 12:01 pts/3 00:00:00 grep --color=auto uwsgi > vint@vgreck:/var/data/work/mainroot/cross-ads$ ps -fA | grep uwsgi > vint 6710 1 73 12:00 pts/3 00:02:01 uwsgi --master --protocol > http --socket :8000 --module=util.transact.publisher > --callable=ControlRequest --spooler run/web/spool/ --show-config > vint 6803 3996 0 12:03 pts/3 00:00:00 grep --color=auto uwsgi > > CONSOLE 2: > > $ kill -TERM 6697 > $ kill -HUP 6697 > $ kill -INT 6697 > > Is this behaviour expected? (pid 6710 consumes all CPU after wsgi master > has terminated and can only be killed within KILL signal) > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
I do not see task enqueued in the spooled in your logs. Can you post the enqueuer function/functions and the spooler callable used to manage tasks ? Thanks -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
