Creating upstart jobs is very simple, just create /etc/init/uwsgi.conf config file, with content below:
=== /etc/init/uwsgi.conf === # uWSGI - manage uWSGI application server # description "uWSGI" start on runlevel [2345] stop on runlevel [!2345] respawn limit nofile 200000 200000 exec /usr/local/bin/uwsgi --emperor /etc/uwsgi/vassals --uid www-data --gid www-data === end of /etc/init/uwsgi.conf === Then: #> cd /etc/init.d #> ls -lh /lib/init/upstart-job uwsgi #> update-rc.d uwsgi defaults It should be enough. You could also add "--logger syslog:uWSGI" to uwsgi command line options (exec line) so that uWSGI will log to local syslog and You will be able to read error messages if for some reason uWSGI would fail to start. But first check if You have "syslog" logger compiled in (uwsgi --logger-list). 2013/1/20 Ashwin Kumar <[email protected]> > hi, > > first of all i want to thank you for uWSGI and the very very nice tutorial > https://github.com/unbit/uwsgi-docs/blob/master/tutorials/Django_and_nginx.rst > > i struck in the last part while starting the emperor on syster boot with > rc.local as mentioned in the tutorial. its not working on ubuntu 12.10 on > amazon. i never tried it anywhere else. i created servers more than 30 > times to see where did i go wrong. but nothing happened. > > its fine if i run this command in terminal > > > /usr/local/bin/uwsgi --emperor /etc/uwsgi/vassals --uid www-data --gid > www-data > > > but its nothing happening when i tried with rc.local > > i think we need to write one more upstart job/script on ubuntu to make it > run automatically. i searched for 2 days and found no decent documentation > on this subject. > > help me. > > -Ashwin. > +91-9959166266 > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
