I am using postgres database with web2py on Linode. I have tried simulating the same volume of requests on a barebones hello world web2py app and the error does not show up so I am suspecting it has to do with the database or the interworkings between web2py and the database?
On Tuesday, August 12, 2014 11:09:56 AM UTC-7, Nail Hassairi wrote: > > I am getting errors like this: > > [Mon Aug 11 16:34:23 2014] [error] [client 54.200.16.41] mod_wsgi > (pid=23422): Exception occurred processing WSGI script > '/home/econ/utility/web2py/wsgihandler.py'. > [Mon Aug 11 16:34:23 2014] [error] [client 54.200.16.41] IOError: failed > to write data > [Mon Aug 11 16:37:44 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:37:49 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:37:55 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:00 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:05 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:10 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:15 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:21 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:26 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:31 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:36 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:41 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:46 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:52 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:38:57 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:39:02 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:39:07 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:39:12 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:39:18 2014] [error] [client 54.200.16.41] Script timed out > before returning headers: wsgihandler.py > [Mon Aug 11 16:39:23 2014] [error] [client 54.200.16.41] mod_wsgi > (pid=23422): Exception occurred processing WSGI script > '/home/econ/utility/web2py/wsgihandler.py'. > [Mon Aug 11 16:39:23 2014] [error] [client 54.200.16.41] IOError: failed > to write data > > When this happens apache freezes and the access.log reports HTTP 408 > errors: > > 193.174.89.19 - - [10/Aug/2014:07:38:03 +0000] "-" 408 0 > > The first time this happened the server was online and it was taken > offline. Later on I was trying to simulate traffic > for short periods of time and this error does seem to get bigger with the > volume of the traffic but sometimes > even large volume of traffic does not trigger it and sometimes smaller > amount of traffic triggers it. > > This seems to be demanding of the CPU resources but memory seems to be > largely idle (top): > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > > 2967 econ 20 0 142m 83m 16m S 60 2.1 > 41:34.55 apache2 > > > 3308 postgres 20 0 50036 35m 32m S 20 0.9 > 10:01.85 postgres > > $ free -m > > > total used free shared buffers cached > Mem: 4002 953 3049 0 31 662 > -/+ buffers/cache: 258 3743 > Swap: 511 0 511 > > But given that the server has 4 cores it appears unlikely to me that this > would simply be a hardware resource constraint. > > > <https://lh4.googleusercontent.com/-beXBtMAxZLQ/U-pYJ5We93I/AAAAAAAADmA/CQCf0aWt0C0/s1600/proportion_408_April21_experiment_file_subset.png> > The above picture shows the proportion of the HTTP 408 Timeout Error of > all HTTP requests. > Do you know what might be causing the problem? > > Thanks! > > > -- 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.
