Chad I've seen this problem with nginx and it is due to the nginx and/or uwsgi timeout values being set too low. Do apache/mod_wsgi have similar parms you could adjust?
-Jim On Friday, February 12, 2016 at 4:01:40 PM UTC-6, cseb...@wisc.edu wrote: > > > Today our alert system notified us that the websites were not accessible. > I looked into the apache logs during the time of the website outage and I > observed a bunch of these errors: > > > [Fri Feb 12 00:58:05 2016] [error] [client 195.159.183.42] Script timed > out before returning headers: wsgihandler.py, referer: > https://www.google.no > > I see that this google group does have a thread opened previously about > this error, and it looks like the user made the switch from apache to > nginx, which is something I do not want to do. I've turned on logging in > the wsgihandler.py and looked in httpserver.log, and all I observe in there > is that it was no longer processing "GET" requests. When the apache service > was restarted, it started processing GET requests. Is there any way to get > more verbose information from this process? I've tried increasing the > number of processes from 1 to 3 for the WSGI daemon in the apache config > but I am still getting this problem. It has happened twice now in the past > month. > > Any insight would be helpful! > > Chad > -- 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.
