Could you solve it? I'm having the same issue. The controller/function hangs until nginx closes the socket.
The problem is with one particular controller/function that access one only record of the database and renders a view. More specifically, the problem appears only with specific db records, not all of them. However, they are all pretty much the same (its a posts table, with title, date and description, really simple). Don't know why, with some articles, it hangs until 504 gateway error. Is there a way to se "what's web2py doing?"? I don't have any postgresql errors, not any other kind of error. El jueves, 1 de octubre de 2015, 21:13:24 (UTC-3), Calvin escribió: > > I have an error handler within web2py that provides the error trace. > > One hypothesis offered was that nginx is closing the socket as uwsgi is > taking too long to serve data. I've increased the keepalive_timeout > parameter from 60 to 600 but this does not help. Where else could the > problem be? > > On Friday, 2 October 2015 03:27:33 UTC+8, Niphlod wrote: >> >> where does this error pop up ? >> >> >> -- 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.
