<p>Try Do <code>invalidateblock</code> then <code>reconsiderblock</code> .</p>

CC BY-SA 3.0
2015-07-06T21:38:38.770Z
It is not clear to me what you are suggesting? These are not command-line options for [bitcoin core](https://en.bitcoin.it/wiki/Running_Bitcoin).
Jonathan Cross
CC BY-SA 3.0
2015-07-01T09:10:37.087Z
2015-07-01T09:10:37.087Z
Kranio23
<p>The message <code>ERROR: AcceptToMemoryPool</code> is to do with your node accepting new transactions from the network and doesn't have anything to do with your local sync state. It just means that someone made a transaction and broadcast it to you which does not respect the rules of your current software version. </p>

<p>It should really be "INFO" rather than error, or simply just not logged at all. </p>

CC BY-SA 3.0
2015-08-21T04:00:39.387Z
2015-11-20T22:25:18.917Z
2015-11-20T22:25:18.917Z
Claris
<p>I just upgraded from Bitcoin Core 0.9 to 0.10.1 on Ubuntu 14.4 after being gone for a few months (blockchain data is from February).  When I loaded up bitcoin-qt, it seemed to be working fine and began correctly syncing the missing blocks.  I then quit bitcoin-qt and later restarted the system and it now refuses to get blocks after February 28th, 2015.</p>

<p>I get the following error repeatedly:</p>

<pre><code>ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
</code></pre>

<p>I am now attempting a <code>-reindex -rescan</code>, but it looks like this will take a <del>day</del> week or so on my old system due to its older CPU.</p>

<p>Any other suggestions?</p>

<p>Additional notes:</p>

<ul>
<li>I confirmed that port 8333 was open and node was visible on bitnodes.io with multiple incoming connections.</li>
</ul>

CC BY-SA 3.0
2015-06-28T12:08:42.603Z
That message is just to do with accepting transactions on the network, it won't affect your block syncing progress at all. It's not really an error, really.
Claris
CC BY-SA 3.0
2015-06-28T13:54:53.820Z
Okay, good to know.  Do any of these ount as *real* errors:
 `ERROR: ConnectBlock() : inputs missing/spent`
 `ERROR: ConnectTip() : ConnectBlock 00000000000000000875efe0903a717e0b487df5d6aacceec390e341e101db94 failed`
 `ERROR: AcceptToMemoryPool : inputs already spent`
Jonathan Cross
CC BY-SA 3.0
2015-06-29T00:10:11.540Z
ConnectBlock() not passing is a major failure and would stop you syncing. It suggests you have some sort of major corruption of your state (that block is valid and does not spend already spent outputs), reindexing should resolve that but it is worrying it happened in the first place.
Claris
CC BY-SA 3.0
2015-06-30T06:35:14.487Z
maybe you should post that on github issues. Even if it can theorically happen by bad luck, it is very unlikely.
Nicolas Dorier
CC BY-SA 3.0
2015-08-20T11:03:16.443Z
This question could be improved by highlighting the "ConnectBlock error" and @Bitcoin then posting his comment as an answer instead.
Murch
CC BY-SA 3.0
2015-11-15T01:42:30.657Z
**Update:** I finally gave up on the old system -- seems faster hardware is needed with newer versions of Bitcoin Core (RAM and Internet bandwidth are not enough).  Have not seen this issue again since.
Jonathan Cross
<bitcoin-core><synchronization><ubuntu><error>
bitcoin core 0.10.1 upgrade stuck syncing
Jonathan Cross
# bitcoin core 0.10.1 upgrade stuck syncing

(Asked by: username_0 on 2015-06-28)

I just upgraded from Bitcoin Core 0.9 to 0.10.1 on Ubuntu 14.4 after being gone for a few months (blockchain data is from February). When I loaded up bitcoin-qt, it seemed to be working fine and began correctly syncing the missing blocks. I then quit bitcoin-qt and later restarted the system and it now refuses to get blocks after February 28th, 2015.

I get the following error repeatedly:

```
ERROR: AcceptToMemoryPool : nonstandard transaction: non-final

```

I am now attempting a `-reindex -rescan`, but it looks like this will take a ~~day~~ week or so on my old system due to its older CPU.

Any other suggestions?

Additional notes:

* I confirmed that port 8333 was open and node was visible on bitnodes.io with multiple incoming connections.

**Tags:** bitcoin-core, synchronization, ubuntu, error

> **Comments:**
> **username_1**: That message is just to do with accepting transactions on the network, it won't affect your block syncing progress at all. It's not really an error, really.  
> **username_0**: Okay, good to know.  Do any of these ount as *real* errors:  `ERROR: ConnectBlock() : inputs missing/spent`  `ERROR: ConnectTip() : ConnectBlock 00000000000000000875efe0903a717e0b487df5d6aacceec390e341e101db94 failed`  `ERROR: AcceptToMemoryPool : inputs already spent`  
> **username_1**: ConnectBlock() not passing is a major failure and would stop you syncing. It suggests you have some sort of major corruption of your state (that block is valid and does not spend already spent outputs), reindexing should resolve that but it is worrying it happened in the first place.  
> **username_2**: maybe you should post that on github issues. Even if it can theorically happen by bad luck, it is very unlikely.  
> **username_3**: This question could be improved by highlighting the "ConnectBlock error" and @Bitcoin then posting his comment as an answer instead.  
> **username_0**: **Update:** I finally gave up on the old system -- seems faster hardware is needed with newer versions of Bitcoin Core (RAM and Internet bandwidth are not enough).  Have not seen this issue again since.  

---

## 2 answers

### Answer by username_1 on 2015-08-21. Score: 4 | Accepted answer

The message `ERROR: AcceptToMemoryPool` is to do with your node accepting new transactions from the network and doesn't have anything to do with your local sync state. It just means that someone made a transaction and broadcast it to you which does not respect the rules of your current software version.

It should really be "INFO" rather than error, or simply just not logged at all.


---

### Answer by username_4 on 2015-07-01. Score: -3

Try Do `invalidateblock` then `reconsiderblock` .

> **Comments:**
> **username_0**: It is not clear to me what you are suggesting? These are not command-line options for [bitcoin core](https://en.bitcoin.it/wiki/Running_Bitcoin).  

---

