Opened 13 years ago

Closed 13 years ago

#187 closed defect (invalid)

failure to connect while a certain entry is present in a furl

Reported by: Zooko Owned by:
Priority: major Milestone: undecided
Component: unknown Version: 0.6.1
Keywords: Cc:

Description

Kevin Reid and I independently observed a problem where a tahoe-lafs client would fail to connect to the introducer, and removing non-working entries from the furl fixed this problem. In Kevin's case, he also observed that it connected to the introducer but then subsequently disconnected. This was also fixed by removing the non-working entries from the furl.

Change History (1)

comment:1 Changed 13 years ago by Zooko

Resolution: invalid
Status: newclosed

Kevin's problem was tracked down to multiple nodes having the same private key. Mine was long ago and I don't remember it too clearly. Closing this as presumed invalid.

Note: See TracTickets for help on using tickets.