broken-pipe

问题 I'm running the Django 1.2 development server and I get these Broken Pipe error messages whenever I load a page from it with Chrome or Safari. My co-worker is getting the error as well when he loads a page from his dev server. We don't have these errors when using Opera or Firefox. Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/django/core/servers/basehttp.py", line 281, in run self.finish_response() File "/Library

问题 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

问题 I know that broken pipe error is thrown when the socket on the peer side is closed. But, in my test I have noted that an immediate 'send' call on this side when the peer side is closed doesn't always lead to a broken pipe error. E.g.: After closing the socket on peer side (I have tried clean closing by calling close and also abnormal closing by killing the peer), if I try to send 40 bytes, then I don't get a broken pipe, but, if I try to send 40000 bytes then it immediately gives broken pipe

问题 I know that broken pipe error is thrown when the socket on the peer side is closed. But, in my test I have noted that an immediate 'send' call on this side when the peer side is closed doesn't always lead to a broken pipe error. E.g.: After closing the socket on peer side (I have tried clean closing by calling close and also abnormal closing by killing the peer), if I try to send 40 bytes, then I don't get a broken pipe, but, if I try to send 40000 bytes then it immediately gives broken pipe

问题 Currently I am using an app built in python. When I run it in personal computer, it works without problems. However, when I move it into a production server. It keeps showing me the error attached as below:. I've done some research and I got the reason that the end user browser stops the connection while the server is still busy sending data. I wonder why did it happen and what is the root cause that prevents it from running properly in production server, while it works on my personal

问题 This question already has answers here : Closed 7 years ago . Possible Duplicate: TCP client-server SIGPIPE I would like know what does this error mean? 回答1: You are using sockets and Http protocol. It simply means your TCP connection has been closed by the other end or broken due to some other reason. By broken it means a 3 way handshake is required again before starting data transfer. As mentioned in the comments, being on listening end i.e. server, you normally cannot initiate the

问题 I'm taking in a bunch of scripts, and creating a wrapper for them in python. I didn't create the scripts that were given to me. Currently I'm working with python 2.2, and the shell I'm using is a csh shell. When I run the script in the following manner: >> setenv some_var '/some/path/' >> <some more setenv> >> ./script -flag >& log.txt < /dev/null & It run's perfectly fine. The issue arises when I use a bash wrapper to call my python wrapper. My bash script (analysis.sh) is as follows: #!/bin

问题 I am new to socket programming, I am trying to send some packets to server using the send() function in C++, but I am always getting a 'Broken pipe' error while sending packets to the server. Could you please help me for the below points? When the send() function returns the "Broken pipe" errors? What are the causes for "Broken pipe" errors in socket programming? What will be the solution for "Broken pipe" error from the send() function? Note: I am using named socket to communicate between

问题 I keep running into this error MemCacheError (Broken pipe): Broken pipe on my Rails app and I can't figure out why. When I access memcached via Rails.cache in my controller, the first 1 or 2 read/writes always seems to throw the broken pipe error. But when I access memcached by creating a new object, ActiveSupport::Cache::MemCacheStore.new , I don't seem to get this error. I also access memcached in another ruby process, and the first read always has this error regardless of the way I access

问题 I use flask and peewee. Sometimes peewee throws this error MySQL server has gone away (error(32, 'Broken pipe')) Peewee database connection db = PooledMySQLDatabase(database,**{ "passwd": password, "user": user, "max_connections":None,"stale_timeout":None, "threadlocals" : True }) @app.before_request def before_request(): db.connect() @app.teardown_request def teardown_request(exception): db.close() After mysql error that "MySQL server has gone away (error(32, 'Broken pipe'))", select queries