Start it manually was just to test the configuration of uwsgi. If that manual test works then you know the problem isn't with uwsgi.
On Fri, May 18, 2012 at 10:46 AM, Lewis <lewis_le...@hotmail.com> wrote: > Guys, let me say thanks first. > > Everything I have was working fine under apache2 and mod_wsgi. I even had > parallel access to php and static files. I wanted to switch to nginx to > make ssl config easier. > > could there be any holdover somewhere from the apache/mod_wsgi config? > > Because everything once worked I don't think the problem is on the python > or web2py side. (I verified all permissions though...) > > The nginx error log shows two kinds of problems (depends on which > experiment I was doing with a config): > >> >> 2012/05/18 10:41:11 [error] 26348#0: *11 upstream timed out (110: >> Connection timed out) while reading response header from upstream, client: >> 76.22.75.122, server: lewlin1, request: "GET / HTTP/1.1", upstream: >> "uwsgi://127.0.0.1:9001", host: "www.lewcl.com" >> 2012/05/18 17:20:34 [error] 29959#0: *4 upstream timed out (110: >> Connection timed out) while reading response header from upstream, client: >> 66.249.68.103, server: lewlin1, request: "GET /robots.txt HTTP/1.1", >> upstream: "uwsgi://127.0.0.1:9001", host: "lewcl.com" > > > Bruce: I don't understand why I should be starting web2py manually. I > never did before on apache/mod_wsgi. It's wsgi's job to call python and > the handler's job to run the right application, as I understand the role of > the gateway. > > I am going to try the suggestion of running little bits of the stack using > command lines with fewer arguments to try to isolate the problem. > > > On Friday, May 18, 2012 9:39:31 AM UTC-7, pbreit wrote: >> >> Someone posted this pretty simple script today. Might work on older >> Ubuntu versions: >> https://groups.google.com/**forum/#!topic/web2py/**moZqFqZ8eHo<https://groups.google.com/forum/#!topic/web2py/moZqFqZ8eHo> >> >> Are you on a cloud server that you can rebuild? If so, I'd recommend a >> rebuild and start from scratch. >> >> If your server comes with Apache pre-installed that's probably a fine way >> to go. I was not experienced with either Apache or Nginx and found Nginx a >> *lot* easier to understand. And it seems pretty unanimous that Nginx is >> more performant across the board. >> > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.fittraineronline.com - Fitness Personal Trainers Online http://www.warplydesigned.com
