Skip to content
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.

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

Intermittent failure: failed to negotiate security protocol: error reading handshake message: noise: message is too short #7734

Closed
achingbrain opened this issue Oct 23, 2020 · 3 comments
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@achingbrain
Copy link
Member

Version information:

go-ipfs 0.7.0

Description:

I'm seeing an intermittent failure in the setup of the transfer a block between 3 peers interface test:

HTTPError: connect 12D3KooWDuMRjYxBhRFAoftyEDvZmHuycj1XAVikFW6pnD7pwXoG failure: failed to dial 12D3KooWDuMRjYxBhRFAoftyEDvZmHuycj1XAVikFW6pnD7pwXoG: all dials failed
* [/ip4/127.0.0.1/tcp/59690] failed to negotiate security protocol: error reading handshake message: noise: message is too short
    at Object.errorHandler [as handleError] (/Users/alex/Documents/Workspaces/ipfs/js-ipfs/packages/ipfs-http-client/src/lib/core.js:75:15)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Client.fetch (/Users/alex/Documents/Workspaces/ipfs/js-ipfs/node_modules/ipfs-utils/src/http.js:156:9)
    at async Object.connect (/Users/alex/Documents/Workspaces/ipfs/js-ipfs/packages/ipfs-http-client/src/swarm/connect.js:10:17)
    at async Context.<anonymous> (/Users/alex/Documents/Workspaces/ipfs/js-ipfs/packages/interface-ipfs-core/src/bitswap/transfer.js:57:9)

The test is running under node and the three go-IPFS nodes are orchestrated via the http api using the ipfs-http-client.

@achingbrain achingbrain added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Oct 23, 2020
@Stebalien
Copy link
Member

Maybe a handshake timeout in js or go?

@jacobheun
Copy link
Contributor

There is an existing issue in Noise around simultaneous connects, libp2p/go-libp2p-noise#70, since this is intermittent this could be the issue.

@Stebalien Stebalien removed the need/triage Needs initial labeling and prioritization label Mar 11, 2021
@Stebalien
Copy link
Member

The upstream issue has been closed. Comment if this is still an issue and I can reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

No branches or pull requests

3 participants