On May 26, 3:26 pm, Richard <richar...@gmail.com> wrote: > Occasionally after heavily using my web2py app I get: > > """ > Proxy Error > > The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request GET /. > > Reason: Error reading from remote server > """
What is generating that? If you are using Apache/mod_wsgi the proxy module isn't involved. Is that error from a front end proxy server. > The apache server is still running but the app won't work until I > reset apache. > These are the common errors from the Apache log: > > server reached MaxClients setting, consider raising the MaxClients > setting Which means Apache and/or mod_wsgi daemon mode isn't configured with enough processes/threads to handle the concurrent load you are getting. > mod_wsgi (pid=20021): Exception occurred processing WSGI script '/ > apachewsgi/web2py/wsgihandler.py'. > > IOError: client connection closed Means that client connection got dropped. This can occur when impatient user pressed reload on page before it returns response, or leaves page via link before returns response. > Any ideas? > Not sure if the problem is with web2py or Apache configuration. Not really enough information as don't know what MPM you are using, how you configured the MPM, how you are using mod_wsgi, how you configured it etc etc. If a restart is required, could be that your Python code isn't multithread safe and you are experiencing thread deadlocks thereby using up threads and locking out new requests. Graham
