Issue
I have django 1.3 on the remote server behind Nginx.
If I run django with apache + mod_wsgi, I can watch errors in apache log files. It's ok but I'd like to have in console.
If I run django own development server, I get errors with stacktrace in console only when DEBUG = False. In DEBUG mode console outputs
Exception happened during processing of request from (..., ...)
Traceback (most recent call last):
File "/usr/local/python/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock
self.process_request(request, client_address)
File "/usr/local/python/lib/python2.7/SocketServer.py", line 310, in process_request
self.finish_request(request, client_address)
File "/usr/local/python/lib/python2.7/SocketServer.py", line 323, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/local/python/lib/python2.7/site-packages/django/core/servers/basehttp.py", line 570, in __init__
BaseHTTPRequestHandler.__init__(self, *args, **kwargs)
File "/usr/local/python/lib/python2.7/SocketServer.py", line 641, in __init__
self.finish()
File "/usr/local/python/lib/python2.7/SocketServer.py", line 694, in finish
self.wfile.flush()
File "/usr/local/python/lib/python2.7/socket.py", line 301, in flush
self._sock.sendall(view[write_offset:write_offset+buffer_size])
error: [Errno 32] Broken pipe
I want to figure out why? Why does django just output unnamed Exception? Why does it depend on DEBUG variable.
This errors occurs mostly outside views when I have no access to request object. So I can't catch it in middleware or using logging handler.
UPDATE. I noticed if I request to django server directly I never get Broken pipe. So may the issue occur while Nginx proxy django?
Solution
Nginx directive proxy_intercept_errors off;
(disabled by default) is what I needed
Answered By - San4ez
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.