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

Markets process cannot connect to running daemon #8129

Closed
10 of 18 tasks
masih opened this issue Feb 17, 2022 · 1 comment
Closed
10 of 18 tasks

Markets process cannot connect to running daemon #8129

masih opened this issue Feb 17, 2022 · 1 comment
Labels
kind/bug Kind: Bug

Comments

@masih
Copy link
Member

masih commented Feb 17, 2022

Checklist

  • This is not a security-related bug/issue. If it is, please follow please follow the security policy.
  • This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • This is not an enhancement request. If it is, please file a improvement suggestion instead.
  • I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
  • I did not make any code changes to lotus.

Lotus component

  • lotus daemon - chain sync
  • lotus miner - mining and block production
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt)
  • lotus miner/market - storage deal
  • lotus miner/market - retrieval deal
  • lotus miner/market - data transfer
  • lotus client
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

Lotus Version

master-spx.idxprov.rc-3

Describe the Bug

When markets process is started with some delay after the daemon process, lip2p connection from markets to daemon fail with read: connection reset by peer.

Adding the peer ID of the markets to the list of protected peers does not resolve this issue either.

But, when daemon is restarted, and markets connected to it as fast as possible (before other connections are established with daemon) the connection is successful.

Output from counting the number of connections:

$ lotus net peers | wc -l
409

Connection manager config:

   ConnMgrLow = 1000
   ConnMgrHigh = 1200
   ConnMgrGrace = "30s"
``

### Logging Information

```text
ERROR: connecting to full node (libp2p): failed to dial 12D3KooWNCcog7KWPsjWa1FmKyqeTeBxxc5cJf27X6vKBVqm1mW3:
  * [/ip4/192.168.20.40/tcp/10231] failed to negotiate security protocol: read tcp4 192.168.20.41:10241->192.168.20.40:10231: read: connection reset by peer
  * [/ip4/127.0.0.1/tcp/10231] dial tcp4 127.0.0.1:10231: connect: connection refused
  * [/ip4/78.31.252.253/tcp/10231] failed to negotiate security protocol: read tcp4 192.168.20.41:10241->78.31.252.253:10231: read: connection reset by peer
  * [/ip4/62.66.210.70/tcp/10231] dial tcp4 0.0.0.0:10241->62.66.210.70:10231: i/o timeout

2022-02-15T15:16:34.639+0100	ERROR	events	events/events_called.go:352	event diff fn failed: failed to get index 2709417 in root &{6 3 1711227 0xc0352e4510 0xc0359b56e0}: handler: websocket connection closed

Repo Steps

  1. Start Daemon, await for it to stat up.
  2. Await for connections to it to accumulate.
  3. Start markets process.
@masih masih changed the title Markets process cannot connect to running daemon when max connection is reached Markets process cannot connect to running daemon Feb 17, 2022
@rjan90
Copy link
Contributor

rjan90 commented Aug 10, 2022

Closing this issue, since this has been fixed on newer releases of Lotus.

@rjan90 rjan90 closed this as completed Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Kind: Bug
Projects
None yet
Development

No branches or pull requests

2 participants