A while ago I had trouble binding to a socket with the --http option where the permissions weren't set. I think that was the reason you put in the --chdir2 option. I'm now upgrading my servers to the latest build and I'm now having trouble with the --socket option. Basically if I remove the --uid option and run the process as root it works. If I add the --uid back in it is not happy.
Even with the -C option in there it seems to be having trouble binding. Any advice for me? $ uwsgi --version uWSGI 0.9.7.1 $ python --version Python 2.6.4 My command line is this: DAEMON_ARGS="-d $LOGFILE -s $SOCKET --vacuum -p 3 -C -M -t 10 -x $BASEDIR/uwsgi.xml --chdir2 $BASEDIR -H $BASEDIR --uid www-data --gid www-data" ...where $SOCKET is /var/run/uwsgi.sock here is the error output I get: *** Starting uWSGI 0.9.7.1 (64bit) on [Tue Apr 5 15:41:12 2011] *** compiled with version: 4.4.1 on 05 April 2011 14:13:42 uWSGI running as root, you can use --uid/--gid/--chroot options setgid() to 33 setuid() to 33 your memory page size is 4096 bytes *** WARNING: you have enabled harakiri without post buffering. Slow upload could be rejected on post-unbuffered webservers *** unlink(): Permission denied [socket.c line 30] bind(): Address already in use [socket.c line 46] ^C _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
