Silencing broken pipe errors (`[Errno 32] Broken pipe`) in python with WSGI+Pyramid -

-

i have rather simple, naive python/wsgi/pyramid web-server.

it's run using wsgiref.simple_server.make_server(), on server built using pyramid.config.configurator().make_wsgi_app(). server works fine.

however, application it's serving has lot of javascript image mouseover popups. if run mouse across page, can generate 20+ image requests. fine (it's internal thing, not lot of users).

however, doing causes server emit half dozen error tracebacks: 

10.1.1.4 - - [25/apr/2014 01:56:42] "get /*snip* 500 59 ---------------------------------------- exception happened during processing of request ('10.1.1.4', 18338) traceback (most recent call last):   file "/usr/lib/python3.4/wsgiref/handlers.py", line 138, in run     self.finish_response()   file "/usr/lib/python3.4/wsgiref/handlers.py", line 180, in finish_response     self.write(data)   file "/usr/lib/python3.4/wsgiref/handlers.py", line 274, in write     self.send_headers()   file "/usr/lib/python3.4/wsgiref/handlers.py", line 333, in send_headers     self._write(bytes(self.headers))   file "/usr/lib/python3.4/wsgiref/handlers.py", line 453, in _write     self.stdout.write(data)   file "/usr/lib/python3.4/socket.py", line 391, in write     return self._sock.send(b) brokenpipeerror: [errno 32] broken pipe  during handling of above exception, exception occurred:  traceback (most recent call last):   file "/usr/lib/python3.4/wsgiref/handlers.py", line 141, in run     self.handle_error()   file "/usr/lib/python3.4/wsgiref/handlers.py", line 368, in handle_error     self.finish_response()   file "/usr/lib/python3.4/wsgiref/handlers.py", line 180, in finish_response     self.write(data)   file "/usr/lib/python3.4/wsgiref/handlers.py", line 274, in write     self.send_headers()   file "/usr/lib/python3.4/wsgiref/handlers.py", line 331, in send_headers     if not self.origin_server or self.client_is_modern():   file "/usr/lib/python3.4/wsgiref/handlers.py", line 344, in client_is_modern     return self.environ['server_protocol'].upper() != 'http/0.9' typeerror: 'nonetype' object not subscriptable  during handling of above exception, exception occurred:  traceback (most recent call last):   file "/usr/lib/python3.4/socketserver.py", line 306, in _handle_request_noblock     self.process_request(request, client_address)   file "/usr/lib/python3.4/socketserver.py", line 332, in process_request     self.finish_request(request, client_address)   file "/usr/lib/python3.4/socketserver.py", line 345, in finish_request     self.requesthandlerclass(request, client_address, self)   file "/usr/lib/python3.4/socketserver.py", line 666, in __init__     self.handle()   file "/usr/lib/python3.4/wsgiref/simple_server.py", line 126, in handle     handler.run(self.server.get_app())   file "/usr/lib/python3.4/wsgiref/handlers.py", line 144, in run     self.close()   file "/usr/lib/python3.4/wsgiref/simple_server.py", line 35, in close     self.status.split(' ',1)[0], self.bytes_sent attributeerror: 'nonetype' object has no attribute 'split'

i understand why i'm getting broken pipe errors (the request image canceled before image has transfered, because mouseover popup has closed), , seems harmless.

however, have no idea how silence traceback. there thousands of them in logs, , makes debugging actual errors nightmare. don't care i'm getting broken pipe errors, how can catch them , swallow them silently?

it seems wsgiref.simple_server.make_server() installs internal handler catches brokenpipeerror: [errno 32] broken pipe, prints traceback, , swallows error. i've tried wrapping run_server() call in try-except clause, , doesn't have effect.

i wound switching using cherrypy wsgi server. doesn't suffer broken pipe log issues, , far more robust well.

it uses threadpool, it's more performant (multiple requests aren't blocking!).


Comments

Post a Comment

Popular posts from this blog

How to access named pipes using JavaScript in Firefox add-on? -

-
i'm trying access named pipe in firefox add-on. code, based on solution 2 this codeproject question, is: var file = components.classes["@mozilla.org/file/local;1"].createinstance(components.interfaces.nsilocalfile); file.initwithpath("\\\\.\\pipe\\test"); var text = "some text written"; var writer = components.classes["@mozilla.org/network/file-output-stream;1"].createinstance(components.interfaces.nsifileoutputstream); // open file read/write access, , create if not exist. writer.init (file, 0x04 | 0x08, -1, 0); writer.write (text, text.length); writer.flush (); writer.close (); when run firefox scratchpad, get: /* exception: component returned failure code: 0x80520012 (ns_error_file_not_found) [nsifileoutputstream.init] @6 */ line 6 line call writer.init. i've played passing different flags writer.init, no luck. i'm able write normal file path code, not named pipe path. i've been searching more information of da...
Read more

multithreading - OPAL (Open Phone Abstraction Library) Transport not terminated when reattaching thread? -

-
i in process of writing application using opal makes h323 calls. have looked online number of working examples , have managed put resembles should like, @ present able call external ip via application when accept call craps out , dies. leaving me with: 0:12.949 setupcall:8752 sert.cxx(259) assertion fail: transport not terminated when reattaching thread , file d:\voip\software\opal\src\opal\transports.cxx, line 1021 passertfunc(0xde3f88, 0xffffffffd228226f, 0, 0) + 0x82 passertfunc(0x10d6e5f8, 0x3fd, 0, 0x10d6eb98) + 0x15b opaltransport::attachthread(0xde5870, 0xffffffffd22fc76b, 0, 0) + 0x96 h323connection::setupconnection(0xffffffffd22fc713, 0, 0, 0xde6ea8) + 0x196 asynchcallsetup(0x10d3572c, 0, 0, 0xdd0108) + 0x7c pthread1arg<psafeptr<opalconnection,psafeptrbase> >::main(0xffffffffd2282faf from have deduced, perhaps incorrectly if there thread lock issue caused (possibly arising fact application sending expected h323 call, throwing in c...
Read more

node.js - req param returns an empty array -

-
i using node.js , mongodb geolocation app , req param returns empty array exports.findpressure = function(req, res) { var queryobject = req.param('q'); console.log(queryobject); db.collection('pressure', function(err, collection) { collection.find( { loc: { $near :[ req.param('q') ] , $maxdistance : 5 }},{"value" : 1, _id : 0}) .sort({_id : -1}).limit(1).toarray(function(err, items) { res.send(items); }); }); }; the longitude , latitude values displayed in console listening on port 3000... connected 'weather' database 8.9068256,52.019347499999995 /pressure?q=8.9068256,52.019347499999995 200 27ms - 2b the url follows http://localhost:3000/pressure?q=8.9068256,52.019347499999995 if use values 8.9068256,52.019347499999995 getting value database if use req.param('q') returning empty array you seem passing values part of query string. req.query.q should contain comma-s...
Read more