On 24 February 2012 15:46, Roberto De Ioris <[email protected]> wrote:
> > This is a quick sequence you can run on debian too: > > wget http://projects.unbit.it/downloads/uwsgi-1.0.4.tar.gz > tar zxvf uwsgi-1.0.4.tar.gz > cd uwsgi-1.0.4 > make > > if all goes well run uWSGI > > ./uwsgi --http-socket :8080 --chdir <path_to_webp2y> --module wsgihandler > > point your browser to port 8080 on localhost and you should see your app > > For webfaction substitute :8080 with the assigned port > Thanks for your reply. Webfaction is not my problem as you saw in my original message. Your advice worked. But as soon as I tried a tcp-socket like '-s 192.168.0.1:8080' I get an error message: "The connection was reset" and on the console: $ uwsgi -x web2py.xml [uWSGI] parsing config file web2py.xml *** Starting uWSGI 1.0.4 (64bit) on [Fri Feb 24 16:24:10 2012] *** compiled with version: 4.6.2 on 24 February 2012 16:11:08 current working directory: /etc/uwsgi/apps-enabled detected binary path: /usr/local/bin/uwsgi *** WARNING: you are running uWSGI without its master process manager *** your memory page size is 4096 bytes uwsgi socket 0 bound to TCP address 192.168.0.1:8080 fd 5 Python version: 2.7.2+ (default, Nov 30 2011, 22:33:30) [GCC 4.6.2] Python main interpreter initialized at 0x1cf11b0 your server socket listen backlog is limited to 100 connections *** Operational MODE: single process *** added /home/www-data/web2py/ to pythonpath. WSGI application 0 (mountpoint='/') ready on interpreter 0x1cf11b0 pid: 16706 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI worker 1 (and the only) (pid: 16706, cores: 1) invalid request block size: 21573 (max 4096)...skip Fri Feb 24 16:24:26 2012 - error parsing request I suspect that nginx would be play the role of the 'master process manager'. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
