- Mar 14, 2016
- 2
- 4
As title says, earlier today I noticed one of my nodes got stuck on block 467470.
It was still printing stuff like this in debug.log:
But not followed by UpdateTip, after a restart the node catched up fine again.
I grabbed a snapshot from the bitnodes api, and it seems a handful of ofter, mostly BU nodes, also seem to be stuck at this block. Not sure if this means anything, I just found this very strange.
Here is the 7 nodes that seem stuck at that same blockheight: https://pastebin.com/6aVk8Mqb (Data is from bitnodes api snapshot at height 46753) notice one is core 0.14 UASF, rest are BU nodes. I also checked already a few hours ago and the same nodes are still at the same blockheight, so I am pretty sure they are stuck and not doing initial sync.
Someone an idea what could cause something like this, or how it can be debugged
Greetings
It was still printing stuff like this in debug.log:
Code:
2017-05-21 22:29:46 Acceptable block: ver:20000000 time:1495405757 size: 998067 Tx:2753 Sig:5168
2017-05-21 22:29:46 BLOCK_DOWNLOAD_WINDOW is 8 MAX_BLOCKS_IN_TRANSIT_PER_PEER is 1I grabbed a snapshot from the bitnodes api, and it seems a handful of ofter, mostly BU nodes, also seem to be stuck at this block. Not sure if this means anything, I just found this very strange.
Here is the 7 nodes that seem stuck at that same blockheight: https://pastebin.com/6aVk8Mqb (Data is from bitnodes api snapshot at height 46753) notice one is core 0.14 UASF, rest are BU nodes. I also checked already a few hours ago and the same nodes are still at the same blockheight, so I am pretty sure they are stuck and not doing initial sync.
Someone an idea what could cause something like this, or how it can be debugged
Greetings
