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] wallet_node: ERROR Traceback - Exception: weight proof response was none #16816

Open
wallentx opened this issue Nov 13, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@wallentx
Copy link
Contributor

What happened?

Fresh Arch Linux - feeling fresh.
Fresh Chia install - nice new SSD.
Synced DB from 0 - took a few days.
Started wallet and let it sync - nice all my XCH is still there.
Stopped all, and edited config.yaml for GPU harvesting - there should be a chia harvester [OPTIONS] command for this 🤔.
chia start farmer and check my logs - gotta make sure there were no errors.
Found error - better make a weird GH issue.

Version

31b60e5

What platform are you using?

Linux

What ui mode are you using?

CLI

Relevant log output

2023-11-12T23:44:14.220 wallet chia.wallet.wallet_node    : ERROR    Error syncing to PeerInfo(_ip=IPv4Address('91.126.229.143'), _port=8444)
Traceback (most recent call last):
  File "chia-blockchain/chia/wallet/wallet_node.py", line 1158, in new_peak_from_untrusted
    await self.long_sync_from_untrusted(syncing, new_peak_hb, peer)
  File "chia-blockchain/chia/wallet/wallet_node.py", line 1167, in long_sync_from_untrusted
    fork_point_weight_proof = await self.fetch_and_update_weight_proof(peer, new_peak_hb)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "chia-blockchain/chia/wallet/wallet_node.py", line 1291, in fetch_and_update_weight_proof
    raise Exception("weight proof response was none")
Exception: weight proof response was none
@wallentx wallentx added the bug Something isn't working label Nov 13, 2023
@wjblanke
Copy link
Contributor

wjblanke commented Nov 15, 2023

This could be from a slow node that couldn't return a weight proof in time. Or it may have just been started up and not had one available. Arch for the win! We will let Almog look at this. I don't suppose you have the logs from the untrusted node?

@wallentx
Copy link
Contributor Author

Nay, the untrusted node was not me.

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

No branches or pull requests

3 participants