ERROR: AcceptToMemoryPool: non-final #6518

issue Drakonadrgora opened this issue on August 5, 2015
  1. Drakonadrgora commented at 2:50 AM on August 5, 2015: none

    while trying to sync with the network and after it gets about 6-8 weeks sync'd it crashes and says there was an internal failure check debug log. when I do the only error it ever shows is that. It shows nothing else but I have to close client and restart. and then it happens again around the same amount of time syncing. It has been taking me several days just to get from the start down to just 2 years 48 weeks left because of this.

    I have the latest bitcoin client installed. 0.11.0 64 bit version on my windows 7 64 bit laptop.

  2. laanwj added the label Windows on Aug 5, 2015
  3. laanwj commented at 10:59 AM on August 5, 2015: member

    Usually these kind of issues are CPU overheating issues. Can you try specifying par=1 in your bitcoin.conf?

    (ERROR: AcceptToMemoryPool: non-final is a harmless message, by the way, certainly not the cause of this crash, see #5794)

  4. Drakonadrgora commented at 3:11 AM on August 6, 2015: none

    Hmm.. I do have a laptop cooling pad so did not think it would be overheating. I will try the suggestion as asked and see how it works at that point.

  5. rickycrand commented at 3:32 PM on August 22, 2015: none

    Please excuse me, I'm a complete newcommer to Bitcoin and also to this forum. Looks like I have a similar problem. Installed Bitcoin core earlier today and it immediately started to download the block chain. When I returned to my computer a couple of hours later the program appeared to have crashed and would not restart until I restarted windows. It starts fine now but there is no longer and progress. The log shows pages of: 2015-08-22 15:28:32 ERROR: AcceptToMemoryPool: non-final 2015-08-22 15:28:39 ERROR: AcceptToMemoryPool: non-final 2015-08-22 15:28:41 ERROR: AcceptToMemoryPool: non-final every few seconds and there is minimal network traffic. I'm running Core v0.11.0 and Windows 7. Any advice will be welcome

  6. dcousens commented at 12:17 AM on August 24, 2015: contributor

    2015-08-22 15:28:32 ERROR: AcceptToMemoryPool: non-final @rickycrand this just translates to:

    Error, there was a transaction attempting to add itself to the memory pool that was non-final. (It was not signed, had an nLockTime constraint etc).

    It it is by no means an issue, and is typical. The crash is certainly from something else. As pointed out by @laanwj, see #5794.

  7. rickycrand commented at 2:34 PM on August 24, 2015: none

    Dear Daniel

    Thank you for the reply but I really think there is a problem either with bitcoin-qt or my computer. (Having said that my computer has been/is generally working very well.)

    I have now run bitcoin-qt 4 times and installed it twice (including clearing the data directory), but the problem persists (see attached).

    Are there any know issues with this version of bitcoin-qt on windows 7 (64bit).

    Is it worth me trying the 32bit version of bitcoin-qt?

    Looks like some kind of lock issue to me (just guessing)? If that could be possible how might I go about clearing any locks?

    Any other suggestion or further information please let me know.

    Regards Ricky Rand

    ----- Original Message ----- From: Daniel Cousens To: bitcoin/bitcoin Cc: rickycrand Sent: Monday, August 24, 2015 1:17 AM Subject: Re: [bitcoin] ERROR: AcceptToMemoryPool: non-final (#6518)

    2015-08-22 15:28:32 ERROR: AcceptToMemoryPool: non-final
``` [@rickycrand](/bitcoin-bitcoin/contributor/rickycrand/) this just translates to:

    Error, there was a transaction attempting to add itself to the memory pool that was non-final. (It was not signed, had an nLockTime constraint etc).

    
  It it is by no means an issue, and is typical.

  —
  Reply to this email directly or view it on GitHub.

I am running Windows 7 Professional
Version 6.1 (Build 7601: Service Pack1)
64Bit OS

i7-3770 CPU @ 3.4GHz 3.9GHz
32 GB RAM

# 

Bitcoin core runs at startup for up-to an hour while downloading
initially at the rate of about 2MB/s

The blocks directory has reached 7.65GB

The network activity showed that no more data was being received and
the following message was displayed.

Assertion failed!

Program: C:\Program Files\Bitcoin\bitcoin-qt.eve
File: main.cpp, Line 1789

Expression: hashPrevBlock == view.getBestBlock()

I choose to ignore the error and the program closed.

When the program was restated the startup dialog said Activating best chain...
but just stopped at that point.

Clicking the close icon displayed the application was not responding.

The last entries in the debug.log were:
2015-08-24 12:36:12 Corruption: block checksum mismatch
2015-08-24 12:36:12 **\* System error while flushing: Database corrupted
2015-08-24 12:36:26 scheduler thread interrupt
2015-08-24 12:36:26 Shutdown: In progress...
2015-08-24 12:36:26 StopNode()
2015-08-24 12:36:26 Corruption: block checksum mismatch
2015-08-24 12:36:26 **\* System error while flushing: Database corrupted

After Windows restart the log showed:

2015-08-24 12:47:35 AppInit2: parameter interaction: -listen=0 -> setting -discover=0
2015-08-24 12:47:35 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 

Followed by:

2015-08-24 12:47:37 Bitcoin version v0.11.0 (2015-07-10 19:23:55 +0200)
2015-08-24 12:47:37 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-08-24 12:47:37 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-08-24 12:47:37 Default data directory C:\Users\Ricky\AppData\Roaming\Bitcoin
2015-08-24 12:47:37 Using data directory C:\Users\Ricky\AppData\Roaming\Bitcoin
2015-08-24 12:47:37 Using config file C:\Users\Ricky\AppData\Roaming\Bitcoin\bitcoin.conf
2015-08-24 12:47:37 Using at most 125 connections (2048 file descriptors available)
2015-08-24 12:47:37 Using 8 threads for script verification
2015-08-24 12:47:37 Using wallet wallet.dat
2015-08-24 12:47:37 scheduler thread start
2015-08-24 12:47:37 init message: Verifying wallet...
2015-08-24 12:47:37 CDBEnv::Open: LogDir=C:\Users\Ricky\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Ricky\AppData\Roaming\Bitcoin\db.log
2015-08-24 12:47:37 Cache configuration:
2015-08-24 12:47:37 \* Using 2.0MiB for block index database
2015-08-24 12:47:37 \* Using 32.5MiB for chain state database
2015-08-24 12:47:37 \* Using 65.5MiB for in-memory UTXO set
2015-08-24 12:47:37 init message: Loading block index...
2015-08-24 12:47:37 Opening LevelDB in C:\Users\Ricky\AppData\Roaming\Bitcoin\blocks\index
2015-08-24 12:47:37 Opened LevelDB successfully
2015-08-24 12:47:37 Opening LevelDB in C:\Users\Ricky\AppData\Roaming\Bitcoin\chainstate
2015-08-24 12:47:37 Opened LevelDB successfully
2015-08-24 12:47:42 LoadBlockIndexDB: last block file = 53
2015-08-24 12:47:42 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=611, size=112957999, heights=230139...231054, time=2013-04-07...2013-04-12)
2015-08-24 12:47:42 Checking all blk files are present...
2015-08-24 12:47:42 LoadBlockIndexDB: transaction index disabled
2015-08-24 12:47:42 LoadBlockIndexDB: hashBestChain=0000000000000161548d26fa8c3ae05bdf2a471f3fac9b6b550f84db4b73cdf8 height=230569 date=2013-04-10 04:00:08 progress=0.084806
2015-08-24 12:47:42 init message: Verifying blocks...
2015-08-24 12:47:42 Verifying last 288 blocks at level 3
2015-08-24 12:47:48 No coin database inconsistencies in last 61 blocks (27656 transactions)
2015-08-24 12:47:48  block index           11353ms
2015-08-24 12:47:48 init message: Loading wallet...
2015-08-24 12:47:48 nFileVersion = 110000
2015-08-24 12:47:48 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total
2015-08-24 12:47:48  wallet                   10ms
2015-08-24 12:47:48 init message: Activating best chain...
2015-08-24 12:47:48 UpdateTip: new best=000000000000000642d15d3b45cbc65732cf8c61d050a885872eae09bcc3dce5  height=230570  log2_work=69.738618  tx=15861858  date=2013-04-10 04:14:58 progress=0.084808  cache=4.5MiB(1374tx)
2015-08-24 12:47:48 UpdateTip: new best=0000000000000226f80a21af2a88b46c71b21c71a29a98098e8813a935c03646  height=230571  log2_work=69.738666  tx=15861883  date=2013-04-10 04:15:55 progress=0.084808  cache=4.5MiB(1422tx)
2015-08-24 12:47:48 UpdateTip: new best=00000000000001064c5f6f63f3041b8cbdbfad6b76147db158b295e0e8e7b46c  height=230572  log2_work=69.738714  tx=15861952  date=2013-04-10 04:18:24 progress=0.084809  cache=4.6MiB(1569tx)
2015-08-24 12:47:48 UpdateTip: new best=0000000000000124eb9e44079a500969de3b96ec6d670e495237b5c7feeee1e7  height=230573  log2_work=69.738763  tx=15862036  date=2013-04-10 04:21:11 progress=0.084809  cache=4.7MiB(1744tx)
2015-08-24 12:47:48 UpdateTip: new best=0000000000000073b67af9d52d64d264655b74d2d00c24c0e4e6fa5c845004d3  height=230574  log2_work=69.738811  tx=15862038  date=2013-04-10 04:23:36 progress=0.084809  cache=4.8MiB(1747tx)
.....
2015-08-24 12:47:52 mapBlockIndex.size() = 371306
2015-08-24 12:47:52 nBestHeight = 230652
2015-08-24 12:47:52 setKeyPool.size() = 100
2015-08-24 12:47:52 mapWallet.size() = 0
2015-08-24 12:47:52 mapAddressBook.size() = 1
2015-08-24 12:47:52 init message: Loading addresses...
2015-08-24 12:47:52 Loaded 133 addresses from peers.dat  0ms
2015-08-24 12:47:52 dnsseed thread start
2015-08-24 12:47:52 upnp thread start
2015-08-24 12:47:52 opencon thread start
2015-08-24 12:47:52 addcon thread start
2015-08-24 12:47:52 net thread start
2015-08-24 12:47:52 msghand thread start
2015-08-24 12:47:52 init message: Done loading
2015-08-24 12:47:52 GUI: PaymentServer::LoadRootCAs: Loaded  36  root certificates 
2015-08-24 12:47:53 receive version message: /Satoshi:0.11.0/: version 70002, blocks=371308, us=151.228.126.203:49169, peer=1
2015-08-24 12:47:53 Added time data, samples 2, offset +0 (+0 minutes)
2015-08-24 12:47:54 receive version message: /Satoshi:0.8.6/: version 70001, blocks=371308, us=151.228.126.203:49170, peer=2
2015-08-24 12:47:54 Added time data, samples 3, offset +0 (+0 minutes)
2015-08-24 12:47:54 receive version message: /Bitcoin XT:0.11.0/: version 70010, blocks=371308, us=151.228.126.203:49171, peer=3
2015-08-24 12:47:54 Added time data, samples 4, offset +0 (+0 minutes)
2015-08-24 12:47:55 UPnP Port Mapping successful.
2015-08-24 12:48:00 receive version message: /Satoshi:0.10.2/: version 70002, blocks=371308, us=151.228.126.203:49177, peer=4
2015-08-24 12:48:00 Added time data, samples 5, offset +0 (+0 minutes)
2015-08-24 12:48:00 nTimeOffset = +0  (+0 minutes)
2015-08-24 12:48:01 receive version message: /Satoshi:0.9.3/: version 70002, blocks=371308, us=151.228.126.203:49178, peer=5
2015-08-24 12:48:01 Added time data, samples 6, offset +6 (+0 minutes)
2015-08-24 12:48:02 receive version message: /Satoshi:0.10.2/: version 70002, blocks=371307, us=151.228.126.203:49179, peer=6
2015-08-24 12:48:02 Added time data, samples 7, offset -2 (+0 minutes)
2015-08-24 12:48:02 nTimeOffset = +0  (+0 minutes)
2015-08-24 12:48:02 receive version message: /Satoshi:0.9.3/: version 70002, blocks=371308, us=151.228.126.203:49180, peer=7
2015-08-24 12:48:02 Added time data, samples 8, offset -11 (+0 minutes)
2015-08-24 12:48:03 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:03 P2P peers available. Skipped DNS seeding.
2015-08-24 12:48:03 dnsseed thread exit
2015-08-24 12:48:04 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:05 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:05 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:06 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:14 receive version message: /Bitcoin XT:0.11.0/: version 70010, blocks=371308, us=151.228.126.203:49190, peer=8
2015-08-24 12:48:14 Added time data, samples 9, offset +0 (+0 minutes)
2015-08-24 12:48:14 nTimeOffset = +0  (+0 minutes)
2015-08-24 12:48:17 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:17 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:17 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:21 ERROR: AcceptToMemoryPool: non-final
2015-08-24 12:48:23 ERROR: AcceptToMemoryPool: non-final
....

The ERROR: AcceptToMemoryPool: non-final continued to be added to the debug.log and
the block chain did not grow after that.

Stopping and restarting Botcoin-qt.exe had a similar result.
  8. miguelmorales85 commented at 1:43 PM on September 10, 2015: none

    I am having the same issue using Ubuntu 14.04 64 bits. I checked debug.log and theres only the message "ERROR: AcceptToMemoryPool: non-final" over and over again

  9. laanwj commented at 8:21 PM on September 22, 2015: member

    Closing this, there doesn't seem to be a clear way forward Again, for anyone googling this, "ERROR: AcceptToMemoryPool: non-final" just means that you're receiving transactions that aren't final yet. It's not an error on your side.

  10. laanwj closed this on Sep 22, 2015
  11. bluikko commented at 3:01 AM on November 6, 2015: none

    Why would you log something that seems to be mostly "cosmetic" with "ERROR" loglevel? "ERROR" implies that something is wrong. No wonder you are getting newbies all riled up. It should be info/notice, warning at most.

  12. laanwj commented at 11:20 AM on November 6, 2015: member

    @bluikko Agreed, that has been solved in git master #6519

  13. laanwj added the label Data corruption on Feb 9, 2016
  14. laanwj removed the label Data corruption on Feb 9, 2016
  15. MarcoFalke locked this on Sep 8, 2021
Contributors
Drakonadrgoralaanwjrickycranddcousensmiguelmorales85bluikko
Labels
Windows
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 03:15 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me