Databases
StackOverflow2013
Postsdbo
PODjango Broken pipe in Debug mode
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango Broken pipe in Debug mode
    primarykey
    data
    text
    <p>I have django 1.3 on the remote server behind Nginx. </p> <p>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.</p> <p>If I run django own development server, I get errors with stacktrace in console only when DEBUG = False. In DEBUG mode console outputs</p> <pre><code>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 </code></pre> <p>I want to figure out why? Why does django just output unnamed Exception? Why does it depend on DEBUG variable.</p> <p>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.</p> <p>UPDATE. I noticed if I request to django server directly I never get Broken pipe. So may the issue occur while Nginx proxy django? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSan4ez
    1. USSan4ez
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango Broken pipe in Debug mode
      1. USHedde van der Heide
      1. VTFavorite
    2. VO
      singulars
      1. PODjango Broken pipe in Debug mode
      1. USthnee
      1. VTFavorite
    3. VO
      singulars
      1. PODjango Broken pipe in Debug mode
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI haven't had this issue on a live server, however it occurs from time to time on the django dev server on my local computer.. I haven't been able to resolve this either
      singulars
      1. PODjango Broken pipe in Debug mode
      1. USHedde van der Heide
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload