Replies: 4 comments
-
Changing the target_peer_count in config.yaml to 2 has resolved this issue on my machine. The issue seems to be related to the peers - not sure why. |
Beta Was this translation helpful? Give feedback.
-
this issue is back - any ideas why this is happening on 1.5.0? |
Beta Was this translation helpful? Give feedback.
-
Log info: File "chia/wallet/wallet_state_manager.py", line 876, in new_coin_state 2022-08-18T07:09:18.655 wallet chia.wallet.wallet_node : ERROR Exception while adding state: Not connected to the full node Traceback (most recent call last): 2022-08-18T07:20:30.805 wallet chia.wallet.wallet_node : WARNING Non-trusted peer {'host': '192.196.185.196', 'port': 8444} is not synced, disconnecting 2022-08-18T07:20:31.840 wallet chia.wallet.wallet_node : ERROR Exception while adding state: Traceback (most recent call last): 2022-08-18T07:20:32.223 wallet chia.wallet.wallet_node : WARNING Non-trusted peer {'host': '99.171.136.198', 'port': 8444} is not synced, disconnecting |
Beta Was this translation helpful? Give feedback.
-
Just to add to this. Its working again now, but I've set the target peer count to 1... this seems far from optimal and I think there might be a memleak issue in 1.5.0. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have a vps with chia running on it, its not a full node, just has the wallet is running / syncing and there are very few other processes. From 7 August onwards, the cpu, ram, and network usage has ramped up alot and its causing issues with syncing. Are there any issues with 1.5.0 that could explain this? Previous versions of chia have worked fine with no issues. When I look at CPU usage etc, I see that chia is using alot of processes - any ideas what could have caused this sudden spike?
The config of the server is:
CPU:2 vCore
RAM:2 GB
SSD:80 GB
Beta Was this translation helpful? Give feedback.
All reactions