Cannot sync #3263
Comments
|
Hi @quake in this case we can find the following log is repeating The best known block stuck at Is it caused by the network connection? |
|
Your attention is appreciated. I have not been able to determine if the network connection is the cause. Any guidance, suggestion, or otherwise, will be promptly deployed. |
This comment was marked as spam.
This comment was marked as spam.
|
Tony, are you part of the ckb team? |
This comment was marked as spam.
This comment was marked as spam.
Hi, @syncprob, don't connect with Tony-ptech. He is not a team support |
it looks like it's running a old version ckb (0.117.0) from log, could you upgrade to latest one (0.119.0) and restart it for running a longer time (around 1 hour) again? |
Specific steps for this
Keep it running for 1 hour Hope it helps @syncprob |
|
SOLVED: Here is what I did to get my Neuron Wallet syncing to 100% and working again. I make sure I had my 12 word seed ready. I completely uninstalled the Neuron program using the Windows Uninstall control panel app. Then I deleted both "Neuron" Folders; one folder was in the "Program files" and the other folder in the "C:\Users\username\AppData\Roaming". You have to show the "Hidden" files in order to see the "AppData" folder. Then I reinstalled the "Neuron Wallet" with the latest release from this github page. https://github.com/nervosnetwork/neuron/releases The current version when I wrote this was 0.117.0 (2024-08-12). I scrolled down on the page and selected the package with the "EXE" version for my Windows 64 bit machine. I ran the installer, during install, I allowed the Firewall rule change. I chose the "Import Wallet Seeds" option, then I copied and pasted my seeds. You can now select all 12 seeds and then paste them into first seed box and it will populated all twelve seeds. Whoever made this feature "Way to go!", big time saver on getting the seeds into the boxes. Once I had the wallet opened, it started syncing. I went to Settings" option and selected the "Light Client Mainnet", it started syncing again. I followed the steps shown in the video below to speed up the synch process. It shows you how to set a starting block for the sync. This video could use some narration on what is going on in the video. I had to watch it many times to see what they were doing. There was a section on the video where they changed the block address from #,###,### to #,##0,000. I suppose that made the starting block to sync begin on a block start, before the actual block they copied? https://www.youtube.com/watch?v=Vl2LGRNqnvk Even with it starting at a higher block, the sync still took over quite a while to fully sync, however, it kept syncing away to it finished. I have a fast Dell desktop with 16GB of RAM, i7 CPU, 1 TB SSD drive and a fast fiber internet. I never got a reply back on why I was getting the "SQLITE_BUSY: database is locked" messages. During the Client sync it got a couple of theses messages and I had to keep monitoring the sync process and clear them when it popped up. I never was able to sync the full node. and gave that up after several days of trying and did the above using the Light Client to get my wallet back working. Very happy to have my Neuron Wallet back up and syncing 100% ---------------- Original Post ---------------------- |
|
Hi, PS C:\Users\carver> cd .\Downloads\ckb_v0.119.0_x86_64-pc-windows-msvc
PS C:\Users\carver\Downloads\ckb_v0.119.0_x86_64-pc-windows-msvc> |
Hi, where do you unzip the |
|
I believe the ckb_v0.119.0_x86_64-pc-windows-msvc directory was unzipped at C:\Users\carver\Downloads. Please see below:
|
Hi @syncprob please type Especially check if |
|
Your efforts thus far are appreciated. Here is the result: |
Hi @syncprob Please run "cd ./ckb_v0.119.0_x86_64-pc-windows-msvc" one more time before running "./ckb init --chain mainnet" We can run "ls" before running "./ckb" to check if PwerShell is in the correct folder |
|
Currently running:
|
Is the [email protected] working properly or does it also halt on a specific block number? If it works well, we can sync Neuron with [email protected] by the following steps:
|
|
Keith-Cy, and others, thank you. The last thing I did was to start "./ckb init --chain mainnet". Still trying to access Neuron Wallet, I opened it and a dialogue box appears "Detected External Node" I have used Neuron for years on multiple devices without issue. I have attempted to access my wallet on 3 different machines. What can I do to access the contents of my Neuron wallet? Thanks |
Hi @syncprob But stuck at 3,400,000 block number is not an exceptional case. That means both the built-in and external nodes cannot reach the latest block. Could you paste the latest 200 lines of the PowerShell here so we can check why the sync is halted? |
|
I apologize for poorly communicating. "./ckb init --chain mainnet" continues to run slowly but surely. To be clear, it is not stuck. Does that mean that I can't open the wallet until it completes in 10 days or so? |
You can keep Neuron on while the outside Node is working. Neuron will always catch up with the latest block of the outside Node. But only when the outside Node reaches the global latest block( |
|
So do I "Ignore external mode" or "Add Network"? If add network is selected, can you please point me to the instructions. |
|
correction: "Ignore external [n]ode" |
Hi @syncprob There are roughly 2 steps to connect to the external node, as illustrated at #3263 (comment), while details are as follows,
Then Neuron is expected to connect to the external node. add.new.network.mov |
|
Still waiting to view and access Neuron Wallet contents. I have successfully synced Neuron wallet with the chain many times on a number of different devices. That is starting fresh. The longest it has taken in the past was roughly 7-8 hours. Approaching 4 days now and it is approx 4,100,000 blocks. |
It's usually determined by the network quality but shouldn't be slow as this. Now the external node is still working but the block number grew so slowly that it only reached 4,100,000, am I right? If so, please share the last 200 line of the PowerShell then we can see if there is any problem with the external node. |
Topic Type
Cannot Synchronize
Detail of the issue
Have tried everything multiple times. Never a problem for more than a year. Have attempted sync with three different machines. Logs below. Please help. Thanks
neuron_debug_1730964241742.zip
bundled-ckb.log
No response
bundled-ckb-light-mainnet.log
No response
main.log
No response
status.log
No response
The text was updated successfully, but these errors were encountered: