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

Boost RPCConnectionError #1765

Closed
7 of 12 tasks
cryptowhizzard opened this issue Oct 19, 2023 · 2 comments
Closed
7 of 12 tasks

Boost RPCConnectionError #1765

cryptowhizzard opened this issue Oct 19, 2023 · 2 comments
Assignees
Labels
support Support Ticket

Comments

@cryptowhizzard
Copy link
Contributor

Checklist

  • This is not a question or a support request. If you have any boost related questions, please ask in the discussion 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 discussion 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 boost.

Boost component

  • boost daemon - storage providers
  • boost client
  • boost UI
  • boost data-transfer
  • boost index-provider
  • Other

Boost Version

boost version 2.1.0-rc1+mainnet+git.ca4f6b5.dirty

Describe the Bug

Seems that somewhere connections get's closed occasionally leading to:

deal paused because of recoverable error {"id": "dece796b-80f5-468d-8869-496c830d782c", "err": "failed to verify CommP: failed to generate CommP: performing remote commp: making remote API call to calculate commp: RPCConnectionError", "checkpoint": "Accepted", "retry": "manual"}

2023-10-19T13:36:20.331+0200 INFO boost-storage-deal logs/log.go:40 deal execution in progress {"id": "b6b6e542-5bc1-4d5b-bfe6-e68090145fd6"}
2023-10-19T13:36:20.890+0200 DEBUG boost-net lp2pimpl/net.go:226 new deal proposal request {"reqlog-uuid": "efa4d6cb-8684-44eb-81cd-6aaab67a2bd1", "client-peer": "12D3KooWKnDj8qencX3iXAtbChf8UNzsL8GASbR8xgymg4QawEt3"}
2023-10-19T13:36:21.232+0200 INFO boost-net lp2pimpl/net.go:249 received deal proposal {"reqlog-uuid": "efa4d6cb-8684-44eb-81cd-6aaab67a2bd1", "client-peer": "12D3KooWKnDj8qencX3iXAtbChf8UNzsL8GASbR8xgymg4QawEt3", "id": "98f96324-cce6-4563-ae2e-50b9fa194aac"}
2023-10-19T13:36:21.233+0200 INFO boost-storage-deal logs/log.go:40 executing deal proposal received from network {"id": "98f96324-cce6-4563-ae2e-50b9fa194aac", "peer": "12D3KooWKnDj8qencX3iXAtbChf8UNzsL8GASbR8xgymg4QawEt3"}
2023-10-19T13:37:32.965+0200 ERROR rpc [email protected]/websocket.go:846 Connection timeout {"remote": "10.0.23.91:2345", "lastAction": ""}
2023-10-19T13:37:32.967+0200 ERROR rpc [email protected]/websocket.go:908 setting read deadlineset tcp 10.0.23.91:53256: use of closed network connection
2023-10-19T13:37:32.967+0200 ERROR rpc [email protected]/websocket.go:846 Connection timeout {"remote": "10.0.23.91:2345", "lastAction": ""}
2023-10-19T13:37:32.968+0200 ERROR rpc [email protected]/websocket.go:908 setting read deadlineset tcp 10.0.23.91:53244: use of closed network connection
2023-10-19T13:37:33.004+0200 ERROR rpc [email protected]/websocket.go:846 Connection timeout {"remote": "10.0.23.91:2345", "lastAction": ""}
2023-10-19T13:37:33.005+0200 ERROR rpc [email protected]/websocket.go:908 setting read deadlineset tcp 10.0.23.91:53230: use of closed network connection
2023-10-19T13:37:33.004+0200 ERROR rpc [email protected]/websocket.go:846 Connection timeout {"remote": "10.0.17.11:1235", "lastAction": ""}
2023-10-19T13:37:33.006+0200 ERROR rpc [email protected]/websocket.go:816 sendReqest failed (Handle me): write tcp 10.0.23.91:40864->10.0.17.11:1235: use of closed network connection
2023-10-19T13:37:33.006+0200 ERROR rpc [email protected]/websocket.go:816 sendReqest failed (Handle me): write tcp 10.0.23.91:40864->10.0.17.11:1235: use of closed network connection
2023-10-19T13:37:33.007+0200 ERROR rpcenc rpcenc/reader.go:177 sending reader param: Post "http://10.0.17.22:3591/rpc/streams/v0/push/7ae517c9-a35d-4316-9d5c-538baa62ad2b": mmap: closed
2023-10-19T13:37:33.007+0200 ERROR rpcenc rpcenc/reader.go:177 sending reader param: Post "http://10.0.17.20:3591/rpc/streams/v0/push/08ecf40e-4b13-4f97-8db8-94e57475085d": mmap: closed
2023-10-19T13:37:33.007+0200 ERROR rpcenc rpcenc/reader.go:177 sending reader param: Post "http://10.0.17.22:3591/rpc/streams/v0/push/ce50364c-e93c-4b23-866d-b53ded3f84d8": mmap: closed
2023-10-19T13:37:33.007+0200 ERROR rpcenc rpcenc/reader.go:177 sending reader param: Post "http://10.0.17.20:3591/rpc/streams/v0/push/80f4ebcc-18d9-4ee1-8fa4-07b4dd21e548": mmap: closed
2023-10-19T13:37:33.007+0200 ERROR rpcenc rpcenc/reader.go:177 sending reader param: Post "http://10.0.17.22:3591/rpc/streams/v0/push/d111c879-07e6-4bfd-b44b-a05b4adbe1f5": mmap: closed
2023-10-19T13:37:33.109+0200 ERROR rpc [email protected]/websocket.go:816 sendReqest failed (Handle me): write tcp 10.0.23.91:40864->10.0.17.11:1235: use of closed network connection
2023-10-19T13:37:33.109+0200 ERROR rpc [email protected]/websocket.go:816 sendReqest failed (Handle me): write tcp 10.0.23.91:40864->10.0.17.11:1235: use of closed network connection
2023-10-19T13:37:34.068+0200 INFO boost-storage-deal logs/log.go:40 deal queued for transfer {"id": "b6b6e542-5bc1-4d5b-bfe6-e68090145fd6", "transfer client id": ""}
2023-10-19T13:37:35.054+0200 INFO boost-storage-deal logs/log.go:40 deal paused because of recoverable error {"id": "dece796b-80f5-468d-8869-496c830d782c", "err": "failed to verify CommP: failed to generate CommP: performing remote commp: making remote API call to calculate commp: RPCConnectionError", "checkpoint": "Accepted", "retry": "manual"}

Logging Information

See above

Repo Steps

No response

@LexLuthr LexLuthr added this to the Boost v2 stability milestone Oct 24, 2023
@LexLuthr LexLuthr self-assigned this Oct 30, 2023
@LexLuthr LexLuthr added support Support Ticket and removed kind/bug Kind: Bug need/triage labels Oct 30, 2023
@LexLuthr
Copy link
Collaborator

@cryptowhizzard Are you still hitting this problem? Do we have any specifics on situation when we hit the issue? Are you seeing this around the huge index deals?

@cryptowhizzard
Copy link
Contributor Author

This problem is solved upgrading to the latest RC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Support Ticket
Projects
Status: Done
Development

No branches or pull requests

2 participants