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

[Bug] Stale partials when importing and deleting an old key with unused plotNFT #17780

Closed
farmerdiamonds opened this issue Mar 26, 2024 · 5 comments
Labels
bug Something isn't working stale-issue flagged as stale and will be closed in 7 days if not updated

Comments

@farmerdiamonds
Copy link

What happened?

After importing an old key, used to farm with plotNFT plots a while back, and deleting the key after syncing I got a lot of stale partials on my farm.
My guess is that is related to the fact that I am farming with many PlotNFTs/Keys (36) simultaneously. After deleting the corresponding entries for the pooling keys in config.yaml the issue with the stale partials was no longer present.

Version

2.2.1

What platform are you using?

Linux

What ui mode are you using?

CLI

Relevant log output

2024-03-26T14:14:43.940 farmer chia.farmer.farmer         : ERROR    Could not find authentication sk for 9862aef3032f86e2f56af28c7ae91a1a3348eb4319212af2b6803f655cbe10be
2024-03-26T14:14:57.723 farmer chia.farmer.farmer         : ERROR    Could not find authentication sk for 3aa5afcd434df17c1162b4e59ca3f5e174b7dea10b8d4a1200dbea984a7622b5
2024-03-26T14:15:11.505 farmer chia.farmer.farmer         : ERROR    Could not find authentication sk for a89e85d7491b6f542f0aee7c2dec7fd3c01d6c499e7b8ac1e9a857ea56d026c1
2024-03-26T14:15:25.344 farmer chia.farmer.farmer         : ERROR    Could not find authentication sk for b8676b8bb3a4efcee9452e4a3f6f3630bdde2f33e5d8e19cd2d35805a8162d27
2024-03-26T14:15:39.142 farmer chia.farmer.farmer         : ERROR    Could not find authentication sk for d413a14a67a1253f7d3217966c7ff8107737447ae3fb9c8743ac52a6103fba5e
2024-03-26T14:15:47.820 farmer chia.farmer.farmer         : ERROR    Error in pooling: (2, 'Received partial in 48.97726130485535. Make sure your proof of space lookups are fast, and network connectivity is good.Response must happen in less than 25 seconds. NAS or network farming can be an issue')
2024-03-26T14:15:47.825 farmer chia.farmer.farmer         : ERROR    Error in pooling: (2, 'Received partial in 48.97726130485535. Make sure your proof of space lookups are fast, and network connectivity is good.Response must happen in less than 25 seconds. NAS or network farming can be an issue')
@farmerdiamonds farmerdiamonds added the bug Something isn't working label Mar 26, 2024
@farmerdiamonds farmerdiamonds changed the title [Bug] Stale partials when importing and delteing an old key with unused plotNFT [Bug] Stale partials when importing and deleteing an old key with unused plotNFT Mar 26, 2024
@farmerdiamonds farmerdiamonds changed the title [Bug] Stale partials when importing and deleteing an old key with unused plotNFT [Bug] Stale partials when importing and deleting an old key with unused plotNFT Mar 26, 2024
@farmerdiamonds
Copy link
Author

There are a few cascaded loops involved when the authentication_sk is not found.

As I am not familiar with python I will not try to fix this by myself.

My start to fix this would be to leave the loops as they are and start by fixing the root cause and add the functionality of cleaning up the config.yaml file when deleting a key either straight at cmds/keys_funcs.py def delete(fingerprint) or add the functionality to remove_property into util/config.py

@wjblanke
Copy link
Contributor

Thanks for the report. We will take a look at how to improve the performance and how to clean up after key deletion.

You could delete config.yaml and wallet DB to resync the plotNFTs. That would be a workaround that should get rid of the extraneous plotNFTs from deleted keys.

Copy link
Contributor

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

@github-actions github-actions bot added stale-issue flagged as stale and will be closed in 7 days if not updated and removed stale-issue flagged as stale and will be closed in 7 days if not updated labels Apr 11, 2024
Copy link
Contributor

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

@github-actions github-actions bot added the stale-issue flagged as stale and will be closed in 7 days if not updated label Apr 27, 2024
Copy link
Contributor

github-actions bot commented May 5, 2024

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale-issue flagged as stale and will be closed in 7 days if not updated
Projects
None yet
Development

No branches or pull requests

2 participants