Still not getting past 2103808. This is 3rd try of deleting the entire .DNotes directory other than DNotes.conf.
debug.log has the following for every block after 2103808.
debug.log has the following for every block after 2103808.
Let me see if I can replicate the issue on my end. Checkpoints updated as well if you want to rebuild and try again. In the meantime, would you mind emailing me your full debug.log at [email protected]?
So far, I have been unable to replicate the issue, reset and downloaded from the beginning and it updated fine. The logs do not indicate any issues rebuilding the blockchain. As far as I can tell, everything else on the network seems to be running fine. I can upload the data files, and you may be able to send them to your server.
full log from 3rd erase/resync WITH updated checkpoints:
again stuck at 2103808
OS is Debian 9.2 with libboost 1.62
You might want to look at block 2103809 and think about why some nodes might think this block is invalid.
Right, I was looking at the same:
https://chainz.cryptoid.info/note/block.dws?5f6005b9bcb8b85afc122b5e20ce89c4cdb9619db6458736237fe616147daf84.htm
Followed the hashes in both directions about 20 blocks, and the data available. I'm not seeing a problem.
I will PM you the data files, if you want to go that route.
I use a couple different variations of ubuntu, so I don't think Debian would make a difference. I can't see how os would make a difference unless it couldn't compile properly.
Based on network activity over the past 24hrs, this node appears to be running an unauthentic version of DNotes:
addnode=23.94.48.23
These are the valid nodes running v 1.2:
addnode=100.34.15.63
addnode=148.74.101.211
addnode=162.243.225.90
addnode=179.158.92.153
addnode=35.169.69.183
addnode=38.66.210.199
addnode=50.39.204.123
addnode=73.241.9.60
addnode=73.26.177.243
addnode=77.58.52.185
Well, even if that node is misbehaving somehow, it doesn't appear to be altering the blockchain. My block 2103809 is identical to the one in the explorer.
