On Friday, September 22, 2017 at 11:50:15 PM UTC-7, Dave S wrote: > > > > On Friday, September 1, 2017 at 4:07:33 PM UTC-7, Dave S wrote: >> >> [...] >> > > >> (This is the same system that isn't fully happy with uploading large >> files from a Windows inet client ... but that doesn't go comatose; it >> eventually times out and has a stack trace in logs/web2py.log; the uploaded >> file is properly saved at that point. I think it responds to other >> requests between the client thinking it's done and the timeout appears.) >> >>> >>>> > In working to get this client working with nginx-uwsgi, I discovered I > needed to add a call to HttpEndRequest(). This doesn't solve the Rocket > issue, but it changes it somewhat. The client now gets a timeout during > that call, it still takes 10 minutes for the request to show up in either > httpserver.log or logs/web2py.log, but it now claims a 200 status, and > there is no traceback. > > This upload, btw, was 5,933,947 bytes. A linux client,where I get to use libcurl, did 11,721,087 bytes with no delay symptoms.
> BTW, when uwsgi calls web2py, it seems to be starting a new > logs/web2py.log (rotating the old ones). Is there a way to have it > continue to use the currently open one? I'm not yet using --emperor; is > that part of the issue? > > > /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
