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

[Support Ticket]: failed to verify CommP: #1840

Open
2 of 10 tasks
narkissos opened this issue Dec 7, 2023 · 1 comment
Open
2 of 10 tasks

[Support Ticket]: failed to verify CommP: #1840

narkissos opened this issue Dec 7, 2023 · 1 comment
Labels
support Support Ticket

Comments

@narkissos
Copy link

narkissos commented Dec 7, 2023

Boost component

  • boost daemon - storage providers
  • boost client
  • boost UI
  • boost data-transfer
  • boost index-provider
  • booster-http
  • booster-bitswap
  • LID Database - Yugabyte/LevelDB
  • boostd-data
  • Other

Boost Version

boostd version 2.1.1+mainnet+git.e9d18ac
boost version 2.1.1+mainnet+git.e9d18ac

Describe the problem

after upgrade from 2.0.0 to 2.1.1 ( same issue with 2.1.0), every deal shows error log like "Error: failed to verify CommP: commP expected=baga6ea4seaqeqwiu4dhjewohbhenftvqcfd4yaqlzsl5dfqkrh6phhravmp3ooq, actual=baga6ea4seaqkfdp7gbugzzvipottvnnzivg5zjrtvnrb5fupgstofbwuvjy62oi: commp mismatch'
1

Logging Information

Repo Steps

  1. Run '...'
  2. Do '...'
  3. See error '...'
    ...
@narkissos narkissos added the support Support Ticket label Dec 7, 2023
@LexLuthr
Copy link
Collaborator

@narkissos The most likely culprit of commP mismatch would be a bad deal or data. Please check with your client.

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

No branches or pull requests

2 participants