Closed nicezic closed 1 year ago
Can you send us the DEBUG debug.log file? There isn't enough information in the logs for us to see a problem
@wjblanke I uploaded the log file.
chia@chia-farmer:~/.chia/mainnet/log$ chia start farmer
Daemon not started yet
Starting daemon
chia_harvester: started
chia_farmer: started
chia_full_node: started
chia_wallet: started
chia@chia-farmer:~/.chia/mainnet/log$ chia wallet show
Wallet height: 4228115
Sync status: Not synced
Connections:
Type IP Ports NodeID Last Connect MiB Up|Dwn
FULL_NODE 127.0.0.1 8444/8444 06e5c2bc... Sep 14 14:36:35 0.0|0.0
-Height: No Info -Hash: No Info -Trusted: True
-rw-r--r-- 1 chia chia 8507392 9월 14 14:28 blockchain_wallet_v2_r1_mainnet_1149317241.sqlite
-rw-r--r-- 1 chia chia 32768 9월 14 14:37 blockchain_wallet_v2_r1_mainnet_1149317241.sqlite-shm
-rw-r--r-- 1 chia chia 119512 9월 14 14:37 blockchain_wallet_v2_r1_mainnet_1149317241.sqlite-wal
-rw-rw-r-- 1 chia chia 10 9월 14 14:36 last_used_fingerprint
I deleted a whole ~/.chia dir, and reinstalled. Now it's sycning.
not working again
Hey @nicezic , when the chia client is in farming mode the wallet will not be fully in sync until the full node is fully synced. Deleting the .chia directory would have also deleted the blockchain db which can take a few days to sync.
To speed up sync you can use the blockchain db torrent from here: https://www.chia.net/downloads/
If you are just wanting to sync a wallet you can do so in wallet-only mode :+1:
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.
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.
What happened?
full_node is syncing, well.
However wallet is not sync.
after deleted db dir.
still same. stucked here.
Version
chia 2.0.1
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output