doveman
commented
3 years ago I moved the mainnet folder back to my C: drive and I still had the same errors in the log about: "Cannot connect to host 198.251.57.56:8444 ssl:<ssl.SSLContext object at 0x000002E03F85B1C0> [The semaphore timeout period has expired]"
and
"Loop exception in sync Was not able to add blocks 0-32. Traceback (most recent call last):"
but the blockchain has synced and the wallet is syncing. I'll put the original wallet files back to save time.
mariano54
emlowe
Chia is not syncing or updating files after moving mainnet folder to another drive and creating symbolic link or junction back to c:\users\x.chia
To Reproduce
Steps to reproduce the behavior:
I was running out of space on my C: drive, so I moved both my .chia and .flax folders to another drive and created symbolic links for each back to the original folders.
After doing this, Flax still works fine. I updated Chia to the latest version and when I ran it, it was just stuck on "Connecting" and the log showed a lot of "Cannot connect to host 127.0.0.1:8444 ssl:<ssl.SSLContext object at 0x0000023AF6FA8CC0> [The remote computer refused the network connection]" errors.
I shutdown Chia and renamed the wallet folder to wallet.bak, deleted the Symbolic Link and created a Junction instead, edited the config. yaml to set "enable_upnp: false" (I thought I'd already done that, as I created a manual port forward on my router ages ago). After this it didn't get stuck on "Connecting" but on the Full Node screen it was only showing the two 127.0.0.1 connections and the screen was just flickering at the bottom for some time. Currently it shows about 12 Full Nodes with Heights in the 856,7xxx range but my Peak Height isn't changing from 856,515.
The errors I'm seeing now are:
"full_node full_node_server : INFO Cannot connect to host 157.61.158.68:8444 ssl:<ssl.SSLContext object at 0x000001F5938351C0> [The semaphore timeout period has expired]"
and
"wallet chia.wallet.wallet_node : ERROR Loop exception in sync Was not able to add blocks 0-32. Traceback (most recent call last):"
I've pasted an extract from the log at the end of this post.
It's currently 07:32 and looking at the files, the wallet -shm and -wal files last updated at 07:08 and the .sqlite file at 07:01. With the blockchain files the -shm file last updated at 07:08, the -wal file at 07:31 and the .sqlite file at 06:10 and the times are about the same for the peer_table files. 07:08 was when I restarted Chia.
I wondered if the files might be somehow keyed to the original folder such that Chia can't access them if they're moved but that wouldn't explain why it's unable to update the new files that it created in the new wallet folder after I renamed the original one to wallet.bak.
I've just shutdown and restarted Chia and again the log is showing loads of: "2021-09-14T07:44:21.646 wallet wallet : INFO Reconnecting to peer {'host': '127.0.0.1', 'port': 8444} 2021-09-14T07:44:23.655 wallet wallet_server : INFO Cannot connect to host 127.0.0.1:8444 ssl:<ssl.SSLContext object at 0x000002A2FA1DE3C0> [The remote computer refused the network connection] 2021-09-14T07:44:24.471 farmer farmer : INFO Reconnecting to peer {'host': '127.0.0.1', 'port': 8444} 2021-09-14T07:44:26.482 farmer farmer_server : INFO Cannot connect to host 127.0.0.1:8444 ssl:<ssl.SSLContext object at 0x000001E50EF67340> [The remote computer refused the network connection] 2021-09-14T07:44:26.656 wallet wallet : INFO Reconnecting to peer {'host': '127.0.0.1', 'port': 8444}"
and the Full Node screen is just full of spinning circles.
Expected behavior Blockchain, blockchain_wallet and wallet_peers files should update
Screenshots
Desktop
Additional context