<p>Have you updated to the latest client in the 0.8.x series? At a wild guess, it sounds like you're on 0.7.x.</p>

CC BY-SA 3.0
2013-09-17T02:47:40.557Z
I am on f**ing 0.3.24, as I just came to realize. I am running Ubuntu Precise LTS and installed simply from sources. Apparently that was a bad idea. http://packages.ubuntu.com/precise/bitcoind
Konstantin Schubert
CC BY-SA 3.0
2013-09-17T03:31:31.273Z
@Konstantin Wow, that's pretty ridiculous. What's the point of calling it LTS if they're not actually going to support it? Bitcoin releases are themselves generally supported for a long time. (I think 0.4.x is still supported by Luke-Jr in bitcoind-stable, for example.)
theymos
CC BY-SA 3.0
2013-09-17T04:15:23.870Z
@theymos I am curious about that too. Maybe Ubuntu only keeps the OS updated?
Konstantin Schubert
CC BY-SA 3.0
2013-09-17T15:45:29.540Z
Well, I think it is more of an obligation of the developers to push updates to Ubuntu instead of the Ubuntu team running after every single package to see if it got updated. I don't know what the procedure exactly is, but I've seen quite a few different packages lagging severely behind in Ubuntu comparing to their latest releases.
Murch
CC BY-SA 3.0
2013-09-17T02:43:30.097Z
2013-09-17T02:43:30.097Z
Anonymous
<p>My bitcoind daemon stopped updating the blockchain at block 258354.</p>

<p>db.log says:</p>

<pre><code>Lock table is out of available lock entries
Lock table is out of available lock entries
etc...
</code></pre>

<p>Here is an excerpt from debug.log:</p>

<pre><code>ERROR: ConnectInputs() : 5915fee0a9 mapTransactions prev not found 66283c57ab
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5915fee0a9
storing orphan tx 5915fee0a9
received: inv (37 bytes)
got inventory: tx 09920def2c50d6b07081  new
askfor tx 09920def2c50d6b07081   0
sending getdata: tx 09920def2c50d6b07081
sending: getdata (37 bytes) 
received: inv (37 bytes)
got inventory: tx 09920def2c50d6b07081  new
askfor tx 09920def2c50d6b07081   1379380242000000
received: inv (253 bytes)
</code></pre>

<p>Any ideas what I should do?</p>

<p>I just spent a week downloading the blockchain. Please not again.</p>

<blockchain><bitcoind>
Bitcoind stuck: Lock table is out of available lock entries
Konstantin Schubert
# Bitcoind stuck: Lock table is out of available lock entries

(Asked by: username_0 on 2013-09-17)

My bitcoind daemon stopped updating the blockchain at block 258354.
db.log says:
Lock table is out of available lock entries
Lock table is out of available lock entries
etc...

Here is an excerpt from debug.log:
ERROR: ConnectInputs() : 5915fee0a9 mapTransactions prev not found 66283c57ab
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5915fee0a9
storing orphan tx 5915fee0a9
received: inv (37 bytes)
got inventory: tx 09920def2c50d6b07081  new
askfor tx 09920def2c50d6b07081   0
sending getdata: tx 09920def2c50d6b07081
sending: getdata (37 bytes) 
received: inv (37 bytes)
got inventory: tx 09920def2c50d6b07081  new
askfor tx 09920def2c50d6b07081   1379380242000000
received: inv (253 bytes)

Any ideas what I should do?
I just spent a week downloading the blockchain. Please not again.

**Tags:** blockchain, bitcoind


---

## 1 answers

### Answer by username_1 on 2013-09-17. Score: 1 | Accepted answer

Have you updated to the latest client in the 0.8.x series? At a wild guess, it sounds like you're on 0.7.x.

> **Comments:**
> **username_0**: I am on f**ing 0.3.24, as I just came to realize. I am running Ubuntu Precise LTS and installed simply from sources. Apparently that was a bad idea. http://packages.ubuntu.com/precise/bitcoind  
> **username_2**: @Konstantin Wow, that's pretty ridiculous. What's the point of calling it LTS if they're not actually going to support it? Bitcoin releases are themselves generally supported for a long time. (I think 0.4.x is still supported by Luke-Jr in bitcoind-stable, for example.)  
> **username_0**: @username_2 I am curious about that too. Maybe Ubuntu only keeps the OS updated?  
> **username_3**: Well, I think it is more of an obligation of the developers to push updates to Ubuntu instead of the Ubuntu team running after every single package to see if it got updated. I don't know what the procedure exactly is, but I've seen quite a few different packages lagging severely behind in Ubuntu comparing to their latest releases.  

---

