Re: [Twisted-Python] Can't identify protocol

2016-03-09 Thread Matilda Bernard
Will do. On Wednesday, March 9, 2016, Glyph Lefkowitz wrote: > On Mar 9, 2016, at 3:34 PM, Matilda Bernard > wrote: > > Thanks Glyph for the possible causes of this problem. > > > I'm definitely curious if you manage to reach a resolution; please follow > up with

Re: [Twisted-Python] Can't identify protocol

2016-03-09 Thread Matilda Bernard
Thanks Glyph for the possible causes of this problem. On Wed, Mar 9, 2016 at 12:07 PM, Glyph Lefkowitz wrote: > > On Mar 8, 2016, at 11:24 PM, Matilda Bernard wrote: > >"I've never seen this, personally, and my understanding of Twisted's > transport

Re: [Twisted-Python] Can't identify protocol

2016-03-08 Thread Matilda Bernard
5 and PyPy 2.6.0 Regards Matilda On Tue, Mar 8, 2016 at 6:23 PM, Glyph Lefkowitz wrote: > > On Mar 8, 2016, at 2:52 PM, Matilda Bernard wrote: > > So netstat doesn't show them but lsof does and our allocated file > descriptors keep increasing and the FDs have the descriptio

Re: [Twisted-Python] Can't identify protocol

2016-03-08 Thread Matilda Bernard
So netstat doesn't show them but lsof does and our allocated file descriptors keep increasing and the FDs have the description "can't identify protocol" On Tue, Mar 8, 2016 at 11:43 AM, Glyph Lefkowitz wrote: > > > On Mar 8, 2016, at 11:10 AM, Matilda Bernard >

[Twisted-Python] Can't identify protocol

2016-03-08 Thread Matilda Bernard
Hi, I am using Twisted 15.2.1 have been seeing a lot of half open TCP/IP connections (lsof can't identify protocol) when I get a lot of traffic . Is this something you have seen with twisted? I'm not really dealing with socket connections at my code level so thought I'd ask if there is a known iss