<p>I just downloaded version 4.4.1.1 to try to reproduce your problem, but couldn't.  Here's the beginning, and relevant mid-section of the debug.log file when I ran it on a machine which I hadn't used for a month or so:</p>

<pre><code>Bitcoin version 0.4.1.1-beta
Default data directory /home/user/.bitcoin
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=/home/user/.bitcoin/database strErrorFile=/home/user/.bitcoin/db.log
Loaded 19026 addresses
 addresses              1337ms
Loading block index...
LoadBlockIndex(): hashBestChain=000000000000052e27b6  height=173760
 block index           13603ms
Loading wallet...
[...]
SetBestChain: new best=0000000000000959beb5  height=176945  work=302325188992488282894
SetBestChain: new best=000000000000011c616f  height=176946  work=302331966182716897933
SetBestChain: new best=000000000000052c233f  height=176947  work=302338743372945512972
SetBestChain: new best=00000000000002c5eaa8  height=176948  work=302345520563174128011
SetBestChain: new best=000000000000089bf6dd  height=176949  work=302352297753402743050
</code></pre>

<p>Maybe you could show us yours?  I tend to agree with Stephen that it's likely a disk space problem.</p>

CC BY-SA 3.0
2012-04-25T15:30:24.277Z
Yes... good idea. Why didn't I start with logging myself. Unfortunately I got logs shoved away. Let me try to reproduce it now, and I will share logs. I'm pretty certain it will lock up on that block, it was happening yesterday all day from multiple workstations. It's definitely not a space problem, but no idea how could I not think of examining log
galets
CC BY-SA 3.0
2012-04-26T06:57:14.813Z
It looks very stupid, but I cannot reproduce the problem anymore. Thanks for idea to look @ log, I guess this is as much as it gets at this point
galets
CC BY-SA 3.0
2012-04-25T11:20:26.087Z
2012-04-25T11:20:26.087Z
Chris Moore
<p>The blockchain chews up well over a gigabyte of disk space.  Are you running out of disk space?</p>

CC BY-SA 3.0
2015-08-22T04:02:58.187Z
'Well over a gigabyte' sounds like the understatement of the year, lol.
Jannes
CC BY-SA 3.0
2012-04-24T18:53:53.007Z
2012-04-24T18:53:53.007Z
Stephen Gornick
<p>Bitcoin client stuck. Tried to rebuild whole blockchain, but it went up to that number and got stuck again. </p>

<p>Here's a screenshot: <a href="http://vvcap.net/db/2IR75OWyJj5AsUW7eo_i.htp" rel="nofollow">http://vvcap.net/db/2IR75OWyJj5AsUW7eo_i.htp</a></p>

<p>Any suggestions?</p>

CC BY-SA 3.0
2015-08-20T10:52:59.003Z
possible duplicate: [What can I do when the blockchain synchronization is stuck at a specific block?](http://bitcoin.stackexchange.com/q/2979/5406)
Murch
<blockchain><synchronization>
Bitcoin client 0.4.1.1 stuck at block 176947
galets
# Bitcoin client 0.4.1.1 stuck at block 176947

(Asked by: username_0 on 2012-04-24)

Bitcoin client stuck. Tried to rebuild whole blockchain, but it went up to that number and got stuck again.

Here's a screenshot: <http://vvcap.net/db/2IR75OWyJj5AsUW7eo_i.htp>

Any suggestions?

**Tags:** blockchain, synchronization

> **Comments:**
> **username_1**: possible duplicate: [What can I do when the blockchain synchronization is stuck at a specific block?](http://bitcoin.stackexchange.com/q/2979/5406)  

---

## 2 answers

### Answer by username_2 on 2012-04-25. Score: 1 | Accepted answer

I just downloaded version 4.4.1.1 to try to reproduce your problem, but couldn't.  Here's the beginning, and relevant mid-section of the debug.log file when I ran it on a machine which I hadn't used for a month or so:
Bitcoin version 0.4.1.1-beta
Default data directory /home/user/.bitcoin
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=/home/user/.bitcoin/database strErrorFile=/home/user/.bitcoin/db.log
Loaded 19026 addresses
 addresses              1337ms
Loading block index...
LoadBlockIndex(): hashBestChain=000000000000052e27b6  height=173760
 block index           13603ms
Loading wallet...
[...]
SetBestChain: new best=0000000000000959beb5  height=176945  work=302325188992488282894
SetBestChain: new best=000000000000011c616f  height=176946  work=302331966182716897933
SetBestChain: new best=000000000000052c233f  height=176947  work=302338743372945512972
SetBestChain: new best=00000000000002c5eaa8  height=176948  work=302345520563174128011
SetBestChain: new best=000000000000089bf6dd  height=176949  work=302352297753402743050

Maybe you could show us yours?  I tend to agree with Stephen that it's likely a disk space problem.

> **Comments:**
> **username_0**: Yes... good idea. Why didn't I start with logging myself. Unfortunately I got logs shoved away. Let me try to reproduce it now, and I will share logs. I'm pretty certain it will lock up on that block, it was happening yesterday all day from multiple workstations. It's definitely not a space problem, but no idea how could I not think of examining log  
> **username_0**: It looks very stupid, but I cannot reproduce the problem anymore. Thanks for idea to look @ log, I guess this is as much as it gets at this point  

---

### Answer by username_3 on 2012-04-24. Score: 0

The blockchain chews up well over a gigabyte of disk space. Are you running out of disk space?

> **Comments:**
> **username_4**: 'Well over a gigabyte' sounds like the understatement of the year, lol.  

---

