Mailing List Archive: Issue 881 in cherokee: uwsgi proccess not restarted

Issue 881 in cherokee: uwsgi proccess not restarted

May 21, 2010, 6:57 AM

Post #1 of 3 (1631 views)

Status: New
Owner: ----

New issue 881 by slav0n...@gmail.com: uwsgi proccess not restarted
http://code.google.com/p/cherokee/issues/detail?id=881

Cherokee Version 1.0.1 debian(sid x86), uWSGI 0.9.5-dev, python-2.6.5

Config section:
source!1!env_inherited = 1
source!1!host = /tmp/copz.sock
source!1!interpreter = /usr/bin/uwsgi -H /django/copz/venv -s
/tmp/copz.sock -t 10 -M -R 2000 -L -p 1 -C -x /django/copz/uwsgi.xml
source!1!nick = copz.ru_uwsgi
source!1!type = interpreter

After server restarted (-SIGHUP/init.d restart/restart from admin panel)
uwsgi process not die/restarted and remains started.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Re: Issue 881 in cherokee: uwsgi proccess not restarted [ In reply to ]

cherokee at googlecode

May 21, 2010, 4:04 PM

Post #2 of 3 (1592 views)

Permalink

Comment #1 on issue 881 by yann.malet: uwsgi proccess not restarted
http://code.google.com/p/cherokee/issues/detail?id=881

Hello,
Here it is a link to the page of the documentation that mention this
feature :
http://www.cherokee-project.com/doc/cookbook_uwsgi.html
In fact I have never seen this working but what you can do is send a signal
to uwsgi
itself as stated on this page :
http://projects.unbit.it/uwsgi/wiki/uWSGISignals

Regards,
--yml

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Re: Issue 881 in cherokee: uwsgi proccess not restarted [ In reply to ]

cherokee at googlecode

Jan 31, 2013, 2:40 PM

Post #3 of 3 (1275 views)

Permalink

Updates:
Status: Accepted
Owner: ste...@konink.de
Labels: Type-Defect Priority-High OpSys-All Component-Logic Usability

Comment #2 on issue 881 by ste...@konink.de: uwsgi proccess not restarted
http://code.google.com/p/cherokee/issues/detail?id=881

Really would like to see this issue fixed. My assumption is that this bug
is related to the uwsgi layer not reporting that the backend doesn't exist
anymore, for example the fastcgi layer works perfectly.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev