Changing pidfile to pidfile2 fixed the problem. But uwsgi writing pid twice still seems a little strange.
-- Zhiping Deng 邓智平 On Wed, Dec 11, 2013 at 2:46 PM, Zhiping Deng <[email protected]>wrote: > Hi, > > > I used the following command to start uwsgi: > > # ./virtualenv/bin/uwsgi etc/uwsgi.yaml > > uwsgi.yaml is: > > uwsgi: > master: 1 > procname-prefix: foo > processes: 2 > uid: foo > gid: foo > chdir: /tmp/foo > python-path: /tmp/foo/etc > wsgi: foo.app > need-app: 1 > pidfile: /tmp/foo/var/run/foo.pid > daemonize2: /tmp/foo/var/log/uwsgi.log > http-socket: 127.0.0.1:8000 > > But no uwsgi processes live after start.. > > The var/log/uwsig.log shows: > > writing pidfile to /tmp/foo/var/run/foo.pid > open("/tmp/foo/var/run/foo.pid"): Permission denied [core/utils.c line > 3518] > > > ls -hl var/run shows: > total 4.0K > -rw-r--r-- 1 root root 6 Dec 11 14:32 foo.pid > > > It seems that uwsgi first writing pid as master (root) , then worker try > to write pid again? > > > # ./virtualenv/bin/uwsgi --version > 1.9.20 > > -- > Zhiping Deng > >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
