If the problem is on nginx side, you can raise the timeout value using uwsgi_read_timeout. That should be tuned accordingly to the "harakiri" parameter of uwsgi, which is by default 60 seconds.
That being said, letting a request to occupy a "web resource" for MORE than 60 seconds, IMHO SCREAMS for the need of an out-of-band processing logic ASAP. On Saturday, November 21, 2015 at 3:53:52 PM UTC+1, Mark Billion wrote: > > It takes a while to process certain pdf creation requests and the Nginx > server is throwing a 504 error. Its atop ubuntu 14.04 w web2py -- it was > set up using the included w2p scripts. > > I am sure that this is a simple question, but my searching has only > located answers about some PHP function..... > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
