You won’t be able to farm until your node is fully synced. Your node still has a long way to go, and it may be faster to delete your db and domains directories and start over using the --sync snap parameter. Make sure you’re using the latest apr-22 release, as snap sync was not available prior to today’s update. If you’re also running an operator, be sure to back up the keystore directory located inside domainsbefore deleting the domains directory, and restore it after your node is in sync.
Thank you, I will try new apr-22. Actualy because of high memory consumption before run apr-07 release I deleted my taurus c:\node\taurus folder and started sync from scratch (keystore was inside ). For the first couple days db grows fast until ~10GB and for the last 3 days size did’t changed thats why I decided that its fully synced. Can you please advise how i can understaned actualy sync progress (like 80%) and why db my size didn’t grow for 3 days? What now i need to do with operator, unregister and create new?
You should be able to recreate the private key as long as you backed up the seed phrase, using a command like ./subspace-node domain key insert --keystore-suri. You can get help with the parameters by running ./subspace-node domain key insert --help.
As for progress, using snap sync should be considerably faster. It will “snap” to the latest finalized block and only needs to sync from there. You’ll know you’re fully synced when best is equal to target.
There are some issues with syncing that still need to be addressed when doing a full sync, but snap sync should allow you to get back in sync quickly and should take up considerably less space in the process.
I have tried to continue with -sync full. For 2 hours sync successfully progressed from best block 320k->370k and then stuck (best block didn’t changed for several hours).
I deleted db and domains as recomended and started with -sync snap. After few minues it stoped with error.
Can you share the full log as a text? If using powershell, something like this should work. subspace-node run <parameters> | Tee-Object -FilePath "log.txt"
It appears I jumped the gun in recommending snap sync. There are still some issues with snap sync and setting up a domain node. While it works fine for consensus, it still doesn’t work for domains.
Your peer count seemed low from your screenshots. It should eventually sync, but in its current state, it could take around 5 to 7 days. Properly port forwarding your ports is crucial to ensure you’re connectable to more peers and to help the process move forward.
Make sure you set unique ports if you are also running a mainnet node on the same network.
I have 3 PC under my home router (2 for mainnet and 1 for testnet). I have checked on mainnet PCs number of peers are ~12-14 and on testnet ~1-2. It looks like your are right and problem is in low peers number for taurus.
So, as I understand now i need to delete db and network one more time and set unique node port before restart taurus sync full?
Yes, you will want to set --sync full and remove the db and domain directories first. Make sure you explicitly set the ports as shown in the example above to ensure your node can connect to peers on the network.
If you plan to farm with this node, it’s important to set a unique RPC port if there is more than one node running on the same machine. Use --rpc-listen-on 0.0.0.0:9955 for the node, and configure the farmer with --node-rpc-url ws://127.0.0.1:9955.
). For the first couple days db grows fast until ~10GB and for the last 3 days size did’t changed thats why I decided that its fully synced. Can you please advise how i can understaned actualy sync progress (like 80%) and why db my size didn’t grow for 3 days? What now i need to do with operator, unregister and create new?