Author

Topic: Block chain stuck at 143,288 blocks (Read 1961 times)

hero member
Activity: 756
Merit: 500
October 20, 2011, 06:51:17 AM
#8
I had a similar problem, but it just recovered after running long enough.

The delays between program start and its window appearing as well as the one between having node connections and continuing the block chain download are excessive. Many users will not have that kind of patience. This must be fixed.

If I start Bitcoin, I have to walk away from the computer for a while, since its window will appear at an arbitrary moment, possibly taking whatever command I input that moment. So apart from requiring a dedicated PC for security, I can't even browse on it while Bitcoin is starting!

Same for me here, sometimes I have to click a few times before Bitcoin appear.
legendary
Activity: 1036
Merit: 1002
October 20, 2011, 06:46:50 AM
#7
I had a similar problem, but it just recovered after running long enough.

The delays between program start and its window appearing as well as the one between having node connections and continuing the block chain download are excessive. Many users will not have that kind of patience. This must be fixed.

If I start Bitcoin, I have to walk away from the computer for a while, since its window will appear at an arbitrary moment, possibly taking whatever command I input that moment. So apart from requiring a dedicated PC for security, I can't even browse on it while Bitcoin is starting!
hero member
Activity: 2086
Merit: 501
★Bitvest.io★ Play Plinko or Invest!
October 11, 2011, 07:17:22 PM
#6
Rebooting the router didn't work

Can you check if all the port mapping and NAT sessions are sensible?

Say what?
legendary
Activity: 2128
Merit: 1073
October 11, 2011, 02:40:44 PM
#5
db.log is empty
This is most important. It means that none of the databases got corrupted, most importantly wallet.dat.
Code:
************************
UNKNOWN EXCEPTION       
bitcoin in CMyApp::OnUnhandledException() 
Now this I something I'm completely unfamiliar. Otherwise the log file looks pretty much like normal exit out of bitcoin.

Since you running your Ubuntu behind some consumer-grade UPnP router, that would be the next item to investigate. Can you check if all the port mapping and NAT sessions are sensible? Or just reboot the router without investigating. It is a known cure for many networking problems with the cheap hardware.
hero member
Activity: 2086
Merit: 501
★Bitvest.io★ Play Plinko or Invest!
October 11, 2011, 01:46:27 PM
#4
Never mind, I found it. Here are the last few lines before, and the error itself in the log:

Code:
ProcessBlock: ACCEPTED
received block 000000000000093b2023
trying connection 65.96.60.92:8333 lastseen=-15.0hrs lasttry=-5.4hrs
connect() failed after select(): Connection refused
SetBestChain: new best=000000000000093b2023  height=143287  work=98749290925043259760
MainFrameRepaint
ProcessBlock: ACCEPTED
received block 0000000000000887a8f6
trying connection 186.221.171.192:8333 lastseen=-15.2hrs lasttry=-5.5hrs
connect() failed after select(): Connection refused
DBFlush(false)
addr.dat refcount=0
ThreadSocketHandler exiting
ThreadOpenConnections exiting
ThreadIRCSeed exiting
SetBestChain: new best=0000000000000887a8f6  height=143288  work=98756926524813125646
UPNP_DeletePortMapping() returned : 0
ThreadMapPort exiting
addr.dat flush
blkindex.dat refcount=1
StopNode()
ProcessBlock: ACCEPTED
ThreadMessageHandler exiting
DBFlush(true)
blkindex.dat refcount=0
blkindex.dat flush
Bitcoin exiting



************************
UNKNOWN EXCEPTION       
bitcoin in CMyApp::OnUnhandledException() 
hero member
Activity: 2086
Merit: 501
★Bitvest.io★ Play Plinko or Invest!
October 11, 2011, 01:39:03 PM
#3
Maybe you could start by fishing the "strange errors" out of the "debug.log", "db.log"

db.log is empty

debug.log is over 36,000 lines long. I have no idea where to begin looking  Undecided

maybe a scrollback buffer of your console?

not sure what this means
legendary
Activity: 2128
Merit: 1073
October 11, 2011, 01:25:01 PM
#2
Maybe you could start by fishing the "strange errors" out of the "debug.log", "db.log" and maybe a scrollback buffer of your console?
hero member
Activity: 2086
Merit: 501
★Bitvest.io★ Play Plinko or Invest!
October 11, 2011, 12:25:12 PM
#1
Hello,

I am using Ubuntu 10.04 & bitcoin 0.4

Yesterday I was recovering an old wallet.dat so I copied it over to the .bitcoin directory and I started bitcoin with the rescan option from terminal. After about 10hrs I was up to block number 143,288 and all my old coins were showing up (hooray!) but I had to shutdown so I closed the bitcoin window and I got some strange error from the terminal window where I had started it. I shutdown as normal and today when I started the bitcoin client it's stuck on block 143,288 with 0 connections. Its been open for 3hrs now and nothing. Should I do the rescan thing again? Will it start all the way from the beginning? What the hell happened and how can I prevent it from happening again?

Thank you
Jump to: