[Twisted-Python] Can't identify protocol

Matilda Bernard serah4291 at gmail.com
Wed Mar 9 00:24:13 MST 2016


   "I've never seen this, personally, and my understanding of Twisted's
transport mechanism is that it would be impossible unless the reactor were
completely frozen for a very long period of time (4+ minutes, at least)."

How can I detect that state?

We're using OEL 6.5 and PyPy 2.6.0

Regards
Matilda

On Tue, Mar 8, 2016 at 6:23 PM, Glyph Lefkowitz <glyph at twistedmatrix.com>
wrote:

>
> On Mar 8, 2016, at 2:52 PM, Matilda Bernard <serah4291 at gmail.com> wrote:
>
> 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"
>
>
> My *guess* would be that that means the file descriptor is open, but not
> connected to anything; which would mean that it's been left open so long
> that the OS has cleaned up the underlying network resources (perhaps via
> shutdown(2)?).
>
> I've never seen this, personally, and my understanding of Twisted's
> transport mechanism is that it would be impossible unless the reactor were
> completely frozen for a very long period of time (4+ minutes, at least).
> What operating system and version are you running?
>
> -glyph
>
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
>


-- 
http://matildabernard.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20160308/27fa80a1/attachment-0002.html>


More information about the Twisted-Python mailing list