Unknown. Syncing Headers 501450 #15
Comments
|
same problem |
|
|
|
synced successfully with correct nodes |
|
@ilia2s Problem solved. Thank you! |
|
@ilia2s does not work for me... still not syncing |
|
@ilia2s @wanghaoqd Guys, how to use those codes? Please help me |
|
@alikazango Add the code to the bitcoin2x.conf file in wallet directory |
|
@sniperdelta Guy, please write me on my email. zangurashvilialeqsandre@gmail.com Please I need your help. Thank you very much |
|
how can we sync this. it stopped at 501450 also added nodes. addnode=46.4.116.70 |
|
@sniperdelta hi sniper i cant find that file theres no conf file in the app data for me, if i just create one and put that in there is that ok? |
|
Ok. I will wait friend
…On 6 Jan 2018 17:15, "adamhiggins1" ***@***.***> wrote:
@sniperdelta <https://github.com/sniperdelta> hi sniper i cant find that
file theres no conf file in the app data for me, if i just create one and
put that in there is that ok?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhbFgiE6qBJov7BjwFFvmQw0ewbyavnLks5tH3HfgaJpZM4RPiNI>
.
|
|
hello, dsl I rarely go to my mailbox, I think it's good, but I can not help
you anymore I'm sorry ... it's a computer friend who made me his because I
was too block at block 501450 ... I hope you find the solution, but you
have to integrate the code that you showed me, it's exactly his :) good
luck :)
2018-01-06 15:00 GMT+01:00 alikazango <notifications@github.com>:
… Ok. I will wait friend
On 6 Jan 2018 17:15, "adamhiggins1" ***@***.***> wrote:
> @sniperdelta <https://github.com/sniperdelta> hi sniper i cant find that
> file theres no conf file in the app data for me, if i just create one and
> put that in there is that ok?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#15 (comment)
>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AhbFgiE6qBJov7BjwFFvmQw0ewbyavnLks5tH3HfgaJpZM4RPiNI>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhbLpv1jkjjubj5CXe15B-3wixjrBMKFks5tH3xjgaJpZM4RPiNI>
.
|
|
|
1.
Open "Bitcoin2x Core - Wallet"
2.
Click Settings>Options>Open Configuration File
3.
Add the following lines:
addnode=46.4.116.70
addnode=136.243.111.195
addnode=138.201.122.203
addnode=46.4.116.70
addnode=46.28.207.57
addnode=89.163.216.76
4.
Save the file. You'll notice "bitcoin2x.conf" file created in your
wallet directory.
5.
Close the "Bitcoin2x Core - Wallet"
6.
Open the "Bitcoin2x Core - Wallet" again
7.
Let it synchronise again, it may take long time for syncing.
8.
Done ✅
2018-01-03 9:17 GMT+01:00 alikazango <notifications@github.com>:
… @sniperdelta <https://github.com/sniperdelta> Guy, please write me on my
email. ***@***.*** Please I need your help. Thank
you very much
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhbLpsYmE4aPigeUDOR21_tYhu4EQytGks5tGzejgaJpZM4RPiNI>
.
|
|
added those nodes to my bitcoin2x.config (which was empty before) but does not continue syncing. I hangs now at header 503449 (Dec 28, 13:00:28 2017) |
|
@shahzeb4u Thanks for the instructions. I'm still stuck syncing at Block 501450. I added/saved/restarted using your suggested nodes in the bitcoin2x.conf file. I opened the file with Notepad (Windows 10), wondering if I need a different editor, maybe that's why it didn't work? Those nodes not showing up in Peers. Also tried manually adding these nodes in Console. Ex: addnode 136.243.111.195 add (although I don't see this node connected in Peers) Debug Log: 2018-01-15 18:14:35 ERROR: invalid header received |
|
I had the same problem, but now i fixed it by changing "addnode" to "connect" and adding ip's from here: https://bitcointalk.org/index.php?topic=2595620.1340. connect=136.243.147.159 Later you should change back to addnode, otherwise you will connect exlusive to peers in list above! |
|
@AndyD87 thanks! I was able to connect to those nodes. Unfortunately I started a reindex before I saw your message, so I won't know if it worked for a day or two. Separate question: right now the reindex is happening - "Processing blocks on disk" NOT syncing to peers, I'm concerned since I'm using the same block data as before (when the error at 0000000000000000004b269ece007638e0992a83ac12210565a45d101544dae2 happened) then it will just happen again. Do I need to use invalidateblock 0000000000000000004b269ece007638e0992a83ac12210565a45d101544dae2 so that it syncs with the correct nodes at that point? |
|
@NoWay426 I don't know the details of Bitcoin2x, so this is what i suspect about this "bug": We stuck at Block 501450 because 501451 is the first Bitcoin2x block. If im right, than invalidate block does not help, because your client queries again for block 501451 and it will receive the wrong from Bitcoin peers again and not the right one from the Bitcoin2x peers. I hope, everything was understandable ;) |
|
@AndyD87 yes that all makes sense, thanks. Here's my question: right now I am reindexing from the block data that I already downloaded on my first try, when I was connected to both Bitcoin & B2X peers and received the wrong block 501451. Although I am now exclusively connected to B2X peers (from the list provided above by you!) I am NOT resyncing from scratch, simply processing blocks from the data that I already had. My concern is that the same error will occur at Block 501451, because it's drawing from the same block data on my disk, not pulling from peers. Can I prevent this from happening using invalidateblock or some other method? Or will B2X automatically solve this because I am now connected to the proper peers? Appreciate your replies! |
|
@NoWay426 It should correct it itself. The block was illegal for b2x, so it should not be saved on your blockchain on disk. One additional thing i did was to delete the "peers.dat", so the client does not know any old peers. |
|
thank, I found all this helpfull. |
|
@AndyD87 EDIT: restarted, and it's working! Thanks for you help. |
I wonder why this is stopped on header 501450
The text was updated successfully, but these errors were encountered: