[Question] Stuck at 2623809/2623809/2623809

[kanliyong]

Hi !

my local node stuck at 2623809/2623809/2623809 two days.

• I have restart the node ,not works.

• I have delete peers.dat then restart the node ,not works .

please help !!

[Joter271]

Same issue here.

Height: 2623809/2623809/2623809, Nodes: 10

Neo-cli version 2.8.0

[bitcodernull]

I have met the same problem
i have deleted all data and use chain.acs to restart the chain, but i still stop at 2623809

[skinderis]

Same problem. I see they have some download MainNet (CDN77 > Deadblock Fix) - 8/16/2018 (MD5: 06ea9760c317b3693c758bbc07b0ad96)

The name is Deadblock Fix, maybe it fixes the issue. Gotta try

[RyanHubs]

Maybe this method can help. Try it.

NEO network working well now. If anyone has syncing problem(suck with 2623809), please delete old blockchain data and download latest offline blockchain data package(https://neo.org/client/chain.zip)(MD5 of this chain.zip is 06ea9760c317b3693c758bbc07b0ad96). Resync the blockchain will solve this problem. Also, 2 things have been done to make syncing data more easily.
1.NGD run 10 new seed nodes which have been synced to the latest height to help community node maintainers to connect with.
http://seed1.ngd.nework/
...
http://seed10.ngd.network/

Please check this instruction for reference.(http://docs.neo.org/zh-cn/node/clo/seedlist.html/

2. We add a new web page(http://sync.ndg.network/)for people to download offline packages which can be used to boost the syncing process. Later we'll change it to https and add MD5 hash.

[Joter271]

Where was this published? Might be useful for future issues...

[arrix]

I was advised to delete chain folder and peers.dat and resync with bootstrap: http://1713188625.rsc.cdn77.org/chain/chain.zip

The chain bootstrap link is published on awesome-neo too.

Hope the dev team can give more information about the issue. What's the technical cause? When will a fix arrive?

[arrix]

I delete the chain folder and peers.dat and rsynced with bootstrap from http://1713188625.rsc.cdn77.org/chain/chain.zip

Now I'm stuck at block Height: 0/2558442/2558443, Nodes: 0. show node gives nothing.
Updated peer list in protocol.json but it didn't help.

Restarting neo-cli didn't help.

Finally I made it continue by removing --log from the command line.

[Joter271]

How do you know if it is importing from bootstrap file? There is no output in neo-cli...

[Joter271]

Hope the dev team can give more information about the issue. What's the technical cause? When will a fix arrive?

[kanliyong]

How to resync with chain.acc file ?
@arrix

I have find the method
Synchronizing the blockchain faster

[metachris]

Delete the Chain folder, put chain.acc in the same directory as neo-cli.dll, and then start neo-cli. It will sync up from chain.acc

[skinderis]

@metachris Do you know why when I run with chain.acc the rpc connections are closed? I can't access my wallet via RPC

[metachris]

Probably because it's just using up all resources for syncing from chain.acc. I'd recommend to let it sync back up and after show state shows the current block height only then move on to testing RPC

[skinderis]

@metachris when I fully sync using chain.acc, can I remove the file after? Or I have to keep it?

[ramisra]

After syncing with chain.acc the node is stuck on 2629182 block number @metachris @skinderis can you help me with this?

[skinderis]

I synced fully, but when I shut down container, it gets stuck again. Now I am at the 2,640,291 block and it is not moving. How to solve the problem, guys??

[wuyudian1]

Me tooooooooo, there are nearly 20% issues talking about this PROBLEM, why not fix it thoroughly ?

[vladicoin]

Same issue here, on 2.7.6 and on 2.8.0 cli versions

[wuyudian1]

I deleted the old chain data, and used the latest Full Offline Package chain.cc.zip, but things got more terrible: it was stucked at 1945082/1945082/1945082, Nodes: 0

[ramisra]

Any development on this?

[fabwa]

Please use https://github.com/neo-project/neo-cli/releases/tag/v2.7.6.1 for now.
Bootstrap with this for Chain: https://cozboot.s3-us-west-2.amazonaws.com/chain-2640xxx.tar.gz
and this for notifications: https://cozboot.s3-us-west-2.amazonaws.com/notif-2640xxx.tar.gz
Please update protocol.json and replace seeds with:

seed1.ngd.nework:10333
...
seed10.ngd.network:10333

That should work..

[vladicoin]

cli 2.7.6.1 works
2.7.6 is stuck
and 2.8.0 is also stuck

[fabwa]

@vladicoin you cannot generalize like this. I have all those versions running and sync up to current block height. Please follow instruction above for 2.7.6 / 2.8.0 if you need those.

[vladicoin]

to be clear:
I ran all those versions from fresh installation and the above was the result.
@fabwa notifications are the result of "--log" ?

[fabwa]

Correct @vladicoin - did you run them with bootstrap beyond the dead block? Just by chance it might have been picked up from a p2p node.

[vladicoin]

actually no,
ver 2.7.6.1 just worked from the getgo ( github release )

[fabwa]

Then you were lucky

[ramisra]

@fabwa thanks it worked.

For the guys in this thread I would strictly recommend to upgrade the neo-cli to 2.7.6.1 or + and for doing so follow these steps:

1. Backup your wallets.db3 file.

2. Download the neo-cli from https://github.com/neo-project/neo-cli/releases/tag/v2.7.6.1 for now.

3. Download the chain folder from https://cozboot.s3-us-west-2.amazonaws.com/chain-2640xxx.tar.gz

4. If you are using notification functionality while starting the neo-cli do download https://cozboot.s3-us-west-2.amazonaws.com/notif-2640xxx.tar.gz

5. After step (3) and (4) extract the compressed files and place them inside the neo-cli extracted from step (1).

6. Update the protocol.json with peers
   "SeedList": [
   "seed1.ngd.nework:10333",
   "seed2.ngd.nework:10333",
   "seed3.ngd.nework:10333",
   "seed4.ngd.nework:10333",
   "seed5.ngd.nework:10333",
   "seed6.ngd.nework:10333",
   "seed7.ngd.nework:10333",
   "seed1.aphelion-neo.com:10333",
   "seed4.aphelion-neo.com:10333",
   "seed2.redpulse.com:10333"
   ],
   or use http://monitor.cityofzion.io/ to find the peers for the specific version of neo-cli you are using.

7. Rename extracted Chain folder to Chain_00746E41.

8. Start the neo-cli from ./neo-cli (Recommended to run using screen as deamon)

[fabwa]

In step 5. rename extracted Chain folder to Chain_00746E41 - then you can skip 8 and 9.

[bboyHan]

After syncing with chain.acc the node is stuck on 2629182 block number @metachris @skinderis
can you help me with this?

[anyouuu]

After syncing with chain.acc the node is stuck on 2560977 block number @metachris @skinderis
can you help me with this?

[penlite]

are you both still stuck @bboyHan and @anyouuu ?

[metachris]

@ratikesh9 small correction re your point 4

If you are using --logs while starting the neo-cli do download https://cozboot.s3-us-west-2.amazonaws.com/notif-2640xxx.tar.gz

This download is not for neo-cli with --logs but only works with the notification server

[ramisra]

@metachris noted

[bboyHan]

@penlite I downloaded the client（2.7.1.0）, reinstalled, and deleted all the data before running properly.
It is unfriendly to wastes a lot of time for me.

[EdgeDLT]

Same issue, now stuck at #3122384.

[jsolman]

@Edgegasm
It appears the issue is due to getting a block that seems valid (at least in the case if 3122384, it contains the exact same transactions as the valid block but in a different order and validates correctly) but is really an orphaned block. An example of this occurred on MainNet at height 3122384.

Neoscan actually has the wrong block hash for this height also which is quite interesting. I was able to get a node stuck syncing at this height with the wrong hash. Interestingly, the transactions in the block look identical though to the correct block.

Incorrect hash shown on neoscan for block 3122384:
0xc01f377f76c95a165635c251fe36b346de5c32a246645c334d3325a425fc025c
https://neoscan.io/block/C01F377F76C95A165635C251FE36B346DE5C32A246645C334D3325A425FC025C

Correct hash from another one of my nodes for block 3122384:
0x5c445c2bf6855df7ea9b86a21db84b432611a17c48ba4466fa005e8739524e4e

I will try to look into it more later, as I believe this is happening a lot on TestNet also and causing nodes to get stuck syncing. I restored from a saved copy of the Chain folder on the node that was stuck about 100 blocks back from the point it got stuck and it synced a second time normally without getting the bad block. (It probably goes without saying that getting the bad block is dependant on randomly having got blocks or headers from the bad node and accepted the bad hash -- such bad nodes usually stay around serving up their bad blocks for a long time since they will forever be stuck).

I thought of a ways to avoid persisting this bad block while syncing, but the issue that allows it to create such a valid bad block with a different hash but same transactions will need to be addressed.

[EdgeDLT]

Thanks for the info @jsolman. Interesting to see an orphan block with the same transactions as the correct block. Wonder how that happened.

I'm currently resyncing with the latest NGD chain zip, which is past the problem block (height 3125968). I'm guessing this won't be an issue anymore after the #422 changes are implemented.

[vncoelho]

Different nonce while transactions did not arrive meanwhile.

[vncoelho]

Sorry, miss click.
Christmas celebrations started early...aehauheauea some will understand...aehauheauea
Our beer smart contract fund, @Edgegasm. aehuahueaea

[jsolman]

@Edgegasm Yeah consensus improvements in progress should fix it.

[vncoelho]

This has been probably solved by avoiding the expose of CN signatures when crashing or after network delays that could cause view to change.

Commit neo-project/neo@f88c427 probably solved that. Fell free to open it again for further investigation or discussion.

[mm999222]

I apologize I am not knowledgeable enough to follow the above suggestions. I have the same issue:
My NEO wallet (ver 2.6.6596.21976) won't update past block 2623809. I am wondering if I simply use the wallet "Rebuild Index" feature will that solve the problem? Any advice is greatly appreciated :)

[EdgeDLT]

@mm999222 There's no need for normal users to bother maintaining a full node anymore.

If you want to maintain a full copy of the blockchain, you'll need to delete your current chain folder then download a synchronization package to get past the dead block. Instructions for that are here.

If you would prefer not to deal with synchronization, you can simply use a light wallet client such as Neon wallet.

[mm999222]

Thanks for replying! If I switch to NEON wallet how do I transfer my NEO, Gas and ONT to the new NEON wallet?

[EdgeDLT]

@mm999222 You don't need to transfer anything, your funds are on the blockchain and not actually "in" a wallet. You can just log into NEON with the same private key you have from neo-gui.

Also, ONT moved to its own MainNet a while ago and the swap closed quite a while ago. I recommend sending them to Binance as I have heard they are still honouring ONT token swaps. Once you have the MainNet ONT tokens, you'd need to store them in an Ontology wallet.

You can use O3 wallet instead of Neon, it supports both the NEO and Ontology blockchains.

[mm999222]

Tk u that worked! Everything is there :) However, I was trying to encrypt my private key in my NEON wallet so I don't have to use my private key to log in but I have this issue...

On the "Encrypt a Key screen" when I put my private key onto the private key box (and set my pass phrase) the button "Generate Encrypted Key" becomes inactive. If I leave my pass phrase in but remove my private key that button becomes active. I don't want to get locked out. I can't find any info on line about this.

[EdgeDLT]

@mm999222 An encrypted key is just your private key encrypted by the password. As long as you have the private key, you will not get locked out of anything.

Encrypted keys are just an extra safety step. Make sure you typed the passphrase in both the 'create' step and the 'confirm' step. That should make the box light up again.

[mm999222]

Yes I did put my pass phrase in both boxes and I pasted my private key in the private key box. But the "create" button becomes inactive. I am wondering if this is happening because the private key has already been used to open the wallet? And therefore you can't encrypt it maybe? I appreciate all the help

[EdgeDLT]

That's more likely to be a bug with Neon rather than anything to do with the private key. Technically you can encrypt a key as many times as you like with as many different passwords.

Have you ensured that the private key is copied correctly with no spaces? I just tried to encrypt a key and it worked for me.

[mm999222]

Yes, I used the same key (copy/paste) that I used to log into the wallet

[mm999222]

What if I create a new private key (in my NEON wallet) and encrypt it with a pass phrase? Will I have the same access to my NEO tokens and the other tokens that show in the NEON wallet?

[EdgeDLT]

You can make a new private key, which would be paired with a new public address. So you'd need to send your funds from the current address to the new one. But yes, that should be a good workaround for you since you can encrypt the new key during creation.