Skip to content

swarm dialer hides actual errors #1046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
whyrusleeping opened this issue Apr 9, 2015 · 1 comment
Closed

swarm dialer hides actual errors #1046

whyrusleeping opened this issue Apr 9, 2015 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws) topic/libp2p Topic libp2p

Comments

@whyrusleeping
Copy link
Member

I was having issues connecting to mars earlier,(could netcat to it, but ipfs failed to dial) and the only errors i got back were 'dial attempt failed' which is rather unhelpful when the actual error was i/o timeout. It would be nice if that error also embedded the actual failure so the user can have a slightly better idea of whats going on.
@whyrusleeping whyrusleeping added kind/bug A bug in existing code (including security flaws) topic/libp2p Topic libp2p labels Apr 9, 2015
@whyrusleeping
Copy link
Member Author

update on the issue, it appears the problem i was having is due to something on the listener end, mars was in an 'unhealthy' state, where connecting to it failed, but the node was still 'up'. A really quick way to check if a node is in this state is if you use netcat to connect to the node and receive no data from it. A healthy node should immediately send you a handshake blob.

possibly related: jbenet/go-peerstream#4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug in existing code (including security flaws) topic/libp2p Topic libp2p
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@whyrusleeping