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

Error 500 unpinning contents #3224

Closed
tmm360 opened this issue Aug 25, 2022 · 3 comments
Closed

Error 500 unpinning contents #3224

tmm360 opened this issue Aug 25, 2022 · 3 comments
Labels
bug Something isn't working issue

Comments

@tmm360
Copy link
Contributor

tmm360 commented Aug 25, 2022

Context

Running bee 1.7.0, where some resources have been pinned

Summary

Trying to delete an existing pin I get error 500 with generic {"message":"Internal Server Error","code":500}

Expected behavior

Pin should be removed without errors

Actual behavior

Internal server error

Steps to reproduce

Don't know

Possible solution

Don't know

@tmm360 tmm360 added the needs-triaging new issues that need triaging label Aug 25, 2022
@bee-runner bee-runner bot added the issue label Aug 25, 2022
@agazso
Copy link
Member

agazso commented Aug 29, 2022

After discussing with the team, most likely this is a result of another issue: #3037

The team is working on a fix, however this requires architectural changes to the localstore component and that means basically of a rewrite of the undelying data storage. The estimation currently is that it will be released somewhere in autumn. You can keep track of all related issues in this issue:
ethersphere/bee-backlog#41

@agazso agazso added bug Something isn't working and removed needs-triaging new issues that need triaging labels Aug 29, 2022
@ldeffenb
Copy link
Collaborator

I have seen this unpinning issue when one of the component chunks under the reference, or the reference itself, is unavailable locally and the traversal fails. This can happen when chunks are randomly, and incorrectly, unpinned by an over-zealous reserve purge. See also #3037

@aloknerurkar
Copy link
Contributor

Same for this one I guess. This whole mechanism has changed so better to file new issues for pinning/reserve interactions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working issue
Projects
None yet
Development

No branches or pull requests

4 participants