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

PIN_ERROR: expected to find the pin in the response #809

Closed
bonedaddy opened this issue Jun 5, 2019 · 1 comment
Closed

PIN_ERROR: expected to find the pin in the response #809

bonedaddy opened this issue Jun 5, 2019 · 1 comment
Assignees
Labels
kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up

Comments

@bonedaddy
Copy link

bonedaddy commented Jun 5, 2019

Additional information:

  • OS: [Ubuntu Server 18.04 LTS]
  • IPFS Cluster version: [0.10.1]
  • IPFS Version [0.4.21]
  • Installation method: [dist.ipfs.io]

Describe the bug:

If running IPFS 0.4.21 and IPFS Cluster 0.10.1, due to the dependencies being used by IPFS Cluster 0.10.1, any pin requests will generally display the following error when running ipfs-cluster-ctl status

PIN_ERROR: expected to find the pin in the response 

This issue appears to be happening because go-ipfs is handling IPFS CID's in base32, while IPFS Cluster is handling CID's in base58. So far it doesn't appear that this issue is leading to any data loss, just a lot of noise.

Additionally it also looks like in certain cases, the following error may also be displayed:

PIN_ERROR: the item is unexpectedly not pinned on IPFS 

However this is not actually the case, as said CID is pinned across all the nodes in my cluster. This appears to be due to the same issue mentioned previously.

@bonedaddy bonedaddy added kind/bug A bug in existing code (including security flaws) need/review Needs a review labels Jun 5, 2019
@hsanjuan
Copy link
Collaborator

hsanjuan commented Jun 5, 2019

This is either fixed by downgrading ipfs, or by using cluster from master, or by applying the fix in #808

@hsanjuan hsanjuan added P1 High: Likely tackled by core team if no one steps up and removed need/review Needs a review labels Jun 5, 2019
@hsanjuan hsanjuan self-assigned this Jun 5, 2019
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) P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

No branches or pull requests

2 participants