Author

Topic: Lagging bitcoin 0.10.1 node (Read 588 times)

sr. member
Activity: 278
Merit: 251
May 04, 2015, 11:50:00 PM
#3
Thanks.  Email sent.

staff
Activity: 4172
Merit: 8419
May 04, 2015, 08:11:33 PM
#2
Can you email me the debug.log? [email protected]


Your description is a bit unclear.   So you have node A. Node A's debug.log said it say the block at 17:05? What log message are you referring to?  Then getinfo didn't show it until later?


One reason there can be a delay is that if the party you requested the block from is super slow or unresponsive, the block may not transfer until that node times out.
sr. member
Activity: 278
Merit: 251
May 04, 2015, 03:11:40 PM
#1
I'm running 0.10.1.

Block 354944 first arrived (in my debug.log) today at 17:05 but my node did not report having this block (with getinfo) until much later, around the time when block 354946 was issued, over 30 minutes later. This might just be a problem with the neighbor nodes, but a number of them were running 0.10.0 or 0.10.1, both inbound and outbound connections.  The missing block should have been made available from one of the neighbors, but wasn't.  Eventually, the arrival of block 354946 resulted in my node catching up.

I have the debug.log file for the entire 3 hour operation of the server. If anyone is interested in looking at this file, please send me a private message.


Jump to: