[tahoe-dev] Troubleshooting node connectivity

[Zooko O'Whielacronx]

 On Tue, Sep 8, 2009 at 6:27 AM, Shawn Willden<shawn at willden.org> wrote:
> Any idea what the problem might be?  What can I do to get more visibility into
> what connections Tahoe is attempting to make (and failing)?

I'll try to address your second question.  :-)  Wireshark is an
excellent tool, and not too hard to learn to use (if you aren't
already familiar with it).  Using it can give you "traffic analysis"
information about the connection pattern -- who sends which TCP setup
packets to whom, timing of retries, etc..  I think wireshark might
also be able to do a MITM attack on your SSL connections for you (if
you provide it with the private key), but I'm not sure, and in any
case that would be overkill for this purpose.

At the same time, turn on logging:

http://allmydata.org/trac/tahoe/browser/docs/logging.txt

Hm I wonder what the status of this comment is: "[TODO: not yet true,
requires foolscap-0.3.1 and a change to allmydata.node]".
Nonetheless, most of the content of logging.txt should help you.
flogtool tail in particular will make all loggable events visible to
you, so you can correlate those with things like which nodes are
connecting to each other and when.

Oh, and I guess the very first thing to do would be to look in your
incidents directory and examine any incident files you find therein.
They are (as far as I know) clean of secrets so you can attach them to
a ticket and ask others to look at them too.

Regards,

Zooko