Topic: 0.6 bitcoin-qt stuck at block 176947 (Read 4082 times)
Get a bitcoin snapshot here: http://eu1.bitcoincharts.com/blockchain/
Are you mining?
Yes.Did you PM gmaxwell about this?
Yes, and I received no response.You could download the nightly snapshot and use this one to skip the block.
Does the nightly snapshot have a fix other than the one mentioned in gmaxwell's post? Because I tried that fix and it didn't help.Edit: Wait, do you mean a nightly blockchain snapshot? That could work.
Edit 2: It did, in fact, work. Hopefully it won't get stuck again...
No good - I've gotten stuck at the same block again.
I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
Did you PM gmaxwell about this?I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
You could download the nightly snapshot and use this one to skip the block.
No good - I've gotten stuck at the same block again.
I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
Are you mining? If not, perhaps you should consider switching to another, blockchain-less client?
I would suggest checking out Electrum and MultiBit, both are quite good and stable. To compare their features, you can use my chart, which is up to date: http://dre.tx0.org/compare.htm (There's Armory too, but it's still in alpha for now)
No good - I've gotten stuck at the same block again.
I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
I'm on the Satoshi QT client, version 0.6.0.6-beta.
At some point on 23 April 2012, the client crashed in boost library code (unfortunately I didn't save the error message) and since then the client has been unable to make progress in catching up to the network; it's stuck at block 176947. I tried -rescan with no success.
Does anyone know what might be causing this?
At some point on 23 April 2012, the client crashed in boost library code (unfortunately I didn't save the error message) and since then the client has been unable to make progress in catching up to the network; it's stuck at block 176947. I tried -rescan with no success.
Does anyone know what might be causing this?
Will the next person who gets stuck please get in touch with me via PM. Peter thinks he fixed a dangling get stuck bug (https://github.com/bitcoin/bitcoin/pull/1196), but unfortunately its hard to reproduce the problem. If you could cleanly shut down and make a copy of your bitcoin director then we could give you a fixed binary to test.
I'm going to go ahead and delete my copy of the blockchain now, in the hopes that I'll be able to make progress after the purge.
I'm stuck again. This time the block number is 181808.
Could I get a binary, or the command to pull+build a version of bitcoind with the fix?
Could I get a binary, or the command to pull+build a version of bitcoind with the fix?
I'm on the Satoshi QT client, version 0.6.0.6-beta.
At some point on 23 April 2012, the client crashed in boost library code (unfortunately I didn't save the error message) and since then the client has been unable to make progress in catching up to the network; it's stuck at block 176947. I tried -rescan with no success.
Does anyone know what might be causing this?
At some point on 23 April 2012, the client crashed in boost library code (unfortunately I didn't save the error message) and since then the client has been unable to make progress in catching up to the network; it's stuck at block 176947. I tried -rescan with no success.
Does anyone know what might be causing this?
Will the next person who gets stuck please get in touch with me via PM. Peter thinks he fixed a dangling get stuck bug (https://github.com/bitcoin/bitcoin/pull/1196), but unfortunately its hard to reproduce the problem. If you could cleanly shut down and make a copy of your bitcoin director then we could give you a fixed binary to test.
At least three.
I noticed that my old client (0.3.x) was stuck at 176947 too when I was waiting for an incoming transaction. A backup only updated to the same block too.
Bitcoin had been closed normally before, no crash or anything.
Downloading the nightly blockchain snapshot and running bitcoin with the rescan option fixed the problem and the client just finished updating the last few missing blocks.
Seems like that block somehow differs from all the others.
I noticed that my old client (0.3.x) was stuck at 176947 too when I was waiting for an incoming transaction. A backup only updated to the same block too.
Bitcoin had been closed normally before, no crash or anything.
Downloading the nightly blockchain snapshot and running bitcoin with the rescan option fixed the problem and the client just finished updating the last few missing blocks.
Seems like that block somehow differs from all the others.
I solved this by deleting the blockchain and copying it from a working client.
However, since this makes at least two people who have gotten stuck on this exact block, I suspect there's a deeper issue here that you guys might want to investigate independently.
However, since this makes at least two people who have gotten stuck on this exact block, I suspect there's a deeper issue here that you guys might want to investigate independently.
Can you post your debug.log file somewhere?
How long have you been stuck already?
About five hours.
How long have you been stuck already?
I'm on the Satoshi QT client, version 0.6.0.6-beta.
At some point on 23 April 2012, the client crashed in boost library code (unfortunately I didn't save the error message) and since then the client has been unable to make progress in catching up to the network; it's stuck at block 176947. I tried -rescan with no success.
Does anyone know what might be causing this?
At some point on 23 April 2012, the client crashed in boost library code (unfortunately I didn't save the error message) and since then the client has been unable to make progress in catching up to the network; it's stuck at block 176947. I tried -rescan with no success.
Does anyone know what might be causing this?
Jump to: