Bitcoin Forum
May 08, 2024, 09:15:51 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Lagging bitcoin 0.10.1 node  (Read 588 times)
tl121 (OP)
Sr. Member
****
Offline Offline

Activity: 278
Merit: 252


View Profile
May 04, 2015, 07: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.


1715159751
Hero Member
*
Offline Offline

Posts: 1715159751

View Profile Personal Message (Offline)

Ignore
1715159751
Reply with quote  #2

1715159751
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715159751
Hero Member
*
Offline Offline

Posts: 1715159751

View Profile Personal Message (Offline)

Ignore
1715159751
Reply with quote  #2

1715159751
Report to moderator
1715159751
Hero Member
*
Offline Offline

Posts: 1715159751

View Profile Personal Message (Offline)

Ignore
1715159751
Reply with quote  #2

1715159751
Report to moderator
gmaxwell
Moderator
Legendary
*
expert
Online Online

Activity: 4172
Merit: 8412



View Profile WWW
May 05, 2015, 12:11:33 AM
 #2

Can you email me the debug.log? greg@xiph.org


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.
tl121 (OP)
Sr. Member
****
Offline Offline

Activity: 278
Merit: 252


View Profile
May 05, 2015, 03:50:00 AM
 #3

Thanks.  Email sent.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!