-
Notifications
You must be signed in to change notification settings - Fork 165
Block stuck at 2,000,190 won't sync #212
Comments
same issue here |
Jdog88, i've resolved my issue by starting again... Deleted Neo Gui folder It quickly synced to latest block hight |
solution here (I haven't tested it, but looks legit) |
@Johnydog @Jdog88 @jrsikors Some of nodes have this problem recently, just resync your blockchain will be fine. You can use this offline blockchain data package(http://static.neo.org/client/chain.acc.zip) to make it faster. |
@PeterLinX ... it seems like some people are having the problem even with the chain.acc.zip ... unless there is a newer chain.acc.zip that gets you past the 2000190 block. It actually looks like CoZ removed the non chain.acc.zip bootstrap ... judging on some of these comments ... i wonder if it wasn't fixing it and causing more problems. |
@PeterLinX @jrsikors I used Peter's Link above and resync the blocks and it reached over 2000190. |
WTF ? How can this happen ? What's the point of having a block chain, if you have to download its contents from one single centralized location in order to be able to work with it ? |
I can't tell if your comment is meant to be funny @vidov1 😄 You can always start from 0/0/0 and download the blockchain the way it was originally intended to be done... which is downloading blocks 1 at a time. |
@Johnydog @PeterLinX .. so i noticed in Johnnydogs, instructions you actually UNZIP the chain.acc.zip .. that wouldn't be what the instructions at http://docs.neo.org/en-us/node/gui.html say to do. Are the instructions on the site wrong? Do you actually need to unzip the chain.acc.zip ? |
@erikzhang as well .. see my previous post |
No, we needn't unzip it. |
Thanks @erikzhang -- you can close this one -- @Jdog88 , who originally posted the issue, said he was good to go. Anyone else still having similar or different problems should create a new issue. |
Anyone else have this problem? Block stuck at 2,000,190 and won't add any more blocks to it. Everything just stuck there for days.
The text was updated successfully, but these errors were encountered: