Roberto, I am looking a bit at the process running when I start and stop the emperor. I am wondering why the emperor is letting 2 uwsgi processes behind.
yml@toulouse:emperor-test$ ps -ef | grep uwsgi yml 8832 1 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 yml 8833 8832 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 yml 8834 8832 0 14:03 ? 00:00:00 uwsgi --xml ./vassal-sites/site1/site1.xml yml 8835 8832 0 14:03 ? 00:00:00 uwsgi --xml ./vassal-sites/site2/site2.xml yml 8836 8833 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 yml 8837 8834 0 14:03 ? 00:00:00 uwsgi --xml ./vassal-sites/site1/site1.xml yml 8838 8835 0 14:03 ? 00:00:00 uwsgi --xml ./vassal-sites/site2/site2.xml yml 8872 13864 0 14:03 pts/6 00:00:00 tail -f uwsgi.log yml 9224 13866 0 15:03 pts/7 00:00:00 grep --color=auto uwsgi yml@toulouse:emperor-test$ cat uwsgi.pid 8832 yml@toulouse:emperor-test$ kill -9 `cat uwsgi.pid` yml@toulouse:emperor-test$ ps -ef | grep uwsgi yml 8833 1 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 yml 8836 8833 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 yml 8872 13864 0 14:03 pts/6 00:00:00 tail -f uwsgi.log yml 9252 13866 0 15:06 pts/7 00:00:00 grep --color=auto uwsgi yml@toulouse:emperor-test$ Regards, --yml On Thu, Feb 3, 2011 at 2:07 PM, Yann Malet <[email protected]> wrote: > Thanks Roberto, > The emperor finally started dance with all its vassal. Now I can inspect > analyse and prepare a blog post about this :-) > > --yml > > > On Thu, Feb 3, 2011 at 2:01 PM, Yann Malet <[email protected]> wrote: > >> Yes I did :-) also following your advise >> >> >> On Thu, Feb 3, 2011 at 1:59 PM, Roberto De Ioris <[email protected]>wrote: >> >>> >>> > That was the problem, this took me one step further: >>> > >>> > (uwsgi-tip)yml@toulouse:emperor-test$ ./start-uwsgi.sh >>> > . >>> > /opt/webapps/emperor-test/uwsgi-tip/bin/uwsgi >>> > (uwsgi-tip)yml@toulouse:emperor-test$ tail -f uwsgi.log >>> > *** uWSGI is running in multiple interpreter mode *** >>> > gracefully (RE)spawned uWSGI master process (pid: 8684) >>> > spawned uWSGI worker 1 (pid: 8687, cores: 1) >>> > adding 6 to signal poll >>> > ImportError: No module named xml >>> >>> >>> %s = filename.xml >>> %n = filename >>> >>> I bet you have set %s in <module> >>> >>> >>> -- >>> Roberto De Ioris >>> http://unbit.it >>> _______________________________________________ >>> uWSGI mailing list >>> [email protected] >>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >>> >> >> >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
