Code

Changes between Initial Version and Version 1 of Ticket #11015


Ignore:
Timestamp:
05/06/09 04:53:06 (5 years ago)
Author:
ramiro
Comment:

(wikified description)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11015

    • Property Needs documentation unset
    • Property Needs tests unset
    • Property Patch needs improvement unset
  • Ticket #11015 – Description

    initial v1  
    1 I am running django-1.0.2 by fastcgi with nginx-0.6.36. Now I found out this error message: Unhandled Exception 
     1I am running django-1.0.2 by fastcgi with nginx-0.6.36. Now I found out this error 
     2{{{ 
     3message: Unhandled Exception 
    24An unhandled exception was thrown by the application.  
     5}}} 
    36 
    47And in nginx's error log I found: 
     8 
     9{{{ 
    510-------------------------------------------- 
    6 2009/05/06 01:03:21 [error] 14785#0: *290 upstream timed out (60: Operation timed out) while reading response header from upstream, client 
    7 : 2.3.1.5, server: ui.zeuux.com, request: "POST /blog/user/qingran/post/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgi.sock:", host: "mydomain", referrer: "http://ui.zeuux.com/blog/user/qingran/post/" 
    8 sic/css/zeuux-com-component-editor.css HTTP/1.1", host: "mydomain", referrer: "http://mydomain/post/" 
     112009/05/06 01:03:21 [error] 14785#0: *290 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 2.3.1.5, server: ui.zeuux.com, request: "POST /blog/user/qingran/post/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgi.sock:", host: "mydomain", referrer: "http://ui.zeuux.com/blog/user/qingran/post/"sic/css/zeuux-com-component-editor.css HTTP/1.1", host: "mydomain", referrer: "http://mydomain/post/" 
     12 
    9132009/05/06 01:05:14 [error] 14785#0: *368 FastCGI sent in stderr: "Traceback (most recent call last): 
    1014  File "/usr/local/lib/python2.5/site-packages/flup-1.0.1-py2.5.egg/flup/server/fcgi_base.py", line 558, in run 
     
    2024  File "/usr/local/lib/python2.5/site-packages/django/db/backends/__init__.py", line 51, in close 
    2125    self.connection.close() 
    22 InterfaceError: connection already closed" while reading response header from upstream, client: 2.5.1.4, server: mydomain, reque 
    23 st: "POST /post/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgi.sock:", host: "mydomain", referrer: 
    24  "http://mydomain/post/" 
     26InterfaceError: connection already closed" while reading response header from upstream, client: 2.5.1.4, server: mydomain, request: "POST /post/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgi.sock:", host: "mydomain", referrer: "http://mydomain/post/" 
    2527-------------------------------------------- 
    26  
     28}}} 
    2729At the same time I found out that my database backend firstly closed the connection because of the network program. 
    2830 
    2931I think django should handle this exception by handler500, so I can give the vistor the error page. My enviorment is listed as follows: 
    30 OS: FreeBSD 6.2 release amd64 
    31 Python 2.5.2_2 
    32 Django 1.0.2 
    33 Database PostgreSQL 8.3.3 
    34 Webserver Nginx-0.6.36 
     32 * OS: FreeBSD 6.2 release amd64 
     33 * Python 2.5.2_2 
     34 * Django 1.0.2 
     35 * Database PostgreSQL 8.3.3 
     36 * Webserver Nginx-0.6.36