Not syncing blocks after upgrading to 0.11.1 #6840

issue PRabahy opened this issue on October 16, 2015
  1. PRabahy commented at 11:14 AM on October 16, 2015: contributor

    I appear to be stuck on block 378906. I'm not exactly sure what I am looking for, but here is the log from after I upgraded.

    2015-10-15 01:23:19 Bitcoin version v0.11.1 (2015-10-12 20:58:31 +0200) 2015-10-15 01:23:19 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2015-10-15 01:23:19 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-10-15 01:23:19 Default data directory C:\Users\PRabahy\AppData\Roaming\Bitcoin 2015-10-15 01:23:19 Using data directory C:\Users\PRabahy\AppData\Roaming\Bitcoin 2015-10-15 01:23:19 Using config file C:\Users\PRabahy\AppData\Roaming\Bitcoin\bitcoin.conf 2015-10-15 01:23:19 Using at most 125 connections (2048 file descriptors available) 2015-10-15 01:23:19 Using 4 threads for script verification 2015-10-15 01:23:19 scheduler thread start 2015-10-15 01:23:19 Binding RPC on address ::1 port 8332 (IPv4+IPv6 bind any: 0) 2015-10-15 01:23:19 Binding RPC on address 127.0.0.1 port 8332 (IPv4+IPv6 bind any: 0) 2015-10-15 01:23:19 Bound to [::]:8333 2015-10-15 01:23:19 Bound to 0.0.0.0:8333 2015-10-15 01:23:19 Cache configuration: 2015-10-15 01:23:19 * Using 2.0MiB for block index database 2015-10-15 01:23:19 * Using 70.0MiB for chain state database 2015-10-15 01:23:19 * Using 178.0MiB for in-memory UTXO set 2015-10-15 01:23:19 init message: Loading block index... 2015-10-15 01:23:19 Opening LevelDB in C:\Users\PRabahy\AppData\Roaming\Bitcoin\blocks\index 2015-10-15 01:23:20 Opened LevelDB successfully 2015-10-15 01:23:20 Opening LevelDB in C:\Users\PRabahy\AppData\Roaming\Bitcoin\chainstate 2015-10-15 01:23:20 Opened LevelDB successfully 2015-10-15 01:23:25 LoadBlockIndexDB: last block file = 355 2015-10-15 01:23:25 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=114, size=63165871, heights=378794...378907, time=2015-10-14...2015-10-14) 2015-10-15 01:23:25 Checking all blk files are present... 2015-10-15 01:23:26 LoadBlockIndexDB: transaction index disabled 2015-10-15 01:23:26 LoadBlockIndexDB: hashBestChain=000000000000000001177ede53f989994350ff591954fb59a547b9f5683eb2b2 height=378906 date=2015-10-14 21:02:44 progress=0.999815 2015-10-15 01:23:26 init message: Verifying blocks... 2015-10-15 01:23:26 Verifying last 288 blocks at level 3 2015-10-15 01:23:48 No coin database inconsistencies in last 14 blocks (14480 transactions) 2015-10-15 01:23:48 block index 28384ms 2015-10-15 01:23:48 Wallet disabled! 2015-10-15 01:23:48 init message: Activating best chain... 2015-10-15 01:23:48 mapBlockIndex.size() = 379407 2015-10-15 01:23:48 nBestHeight = 378906 2015-10-15 01:23:48 setKeyPool.size() = 0 2015-10-15 01:23:48 mapWallet.size() = 0 2015-10-15 01:23:48 mapAddressBook.size() = 0 2015-10-15 01:23:48 init message: Loading addresses... 2015-10-15 01:23:48 Loaded 66066 addresses from peers.dat 218ms 2015-10-15 01:23:48 dnsseed thread start 2015-10-15 01:23:48 net thread start 2015-10-15 01:23:48 addcon thread start 2015-10-15 01:23:48 opencon thread start 2015-10-15 01:23:48 msghand thread start 2015-10-15 01:23:48 init message: Done loading 2015-10-15 01:23:48 receive version message: /Satoshi:0.9.99/: version 70002, blocks=-1, us=68.34.102.231:8333, peer=1 2015-10-15 01:23:48 Added time data, samples 2, offset -4 (+0 minutes) 2015-10-15 01:23:48 GUI: PaymentServer::LoadRootCAs: Loaded 39 root certificates 2015-10-15 01:23:49 receive version message: /Satoshi:0.11.0/: version 70002, blocks=378937, us=68.34.102.231:61836, peer=2 2015-10-15 01:23:49 Added time data, samples 3, offset -2 (+0 minutes) 2015-10-15 01:23:49 ERROR: AcceptBlockHeader: block is marked invalid 2015-10-15 01:23:49 ERROR: invalid header received 2015-10-15 01:23:49 ProcessMessages(headers, 2593 bytes) FAILED peer=2 2015-10-15 01:23:51 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:23:58 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:23:59 P2P peers available. Skipped DNS seeding. 2015-10-15 01:23:59 dnsseed thread exit 2015-10-15 01:24:01 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=378937, us=68.34.102.231:61841, peer=3 2015-10-15 01:24:01 Added time data, samples 4, offset -3 (+0 minutes) 2015-10-15 01:24:02 ERROR: AcceptBlockHeader: block is marked invalid 2015-10-15 01:24:02 ERROR: invalid header received 2015-10-15 01:24:02 ProcessMessages(headers, 2593 bytes) FAILED peer=3 2015-10-15 01:24:04 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:04 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:05 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-10-15 01:24:07 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:08 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-10-15 01:24:13 receive version message: /bitcoinj:0.14SNAPSHOT/: version 70001, blocks=378937, us=127.0.0.1:8333, peer=4 2015-10-15 01:24:13 Added time data, samples 5, offset -2 (+0 minutes) 2015-10-15 01:24:13 nTimeOffset = -2 (+0 minutes) 2015-10-15 01:24:14 receive version message: /Satoshi:0.9.99/: version 70002, blocks=-1, us=68.34.102.231:8333, peer=5 2015-10-15 01:24:14 Added time data, samples 6, offset -1 (+0 minutes) 2015-10-15 01:24:16 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:20 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:29 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:30 receive version message: /Satoshi:0.11.0/: version 70002, blocks=375495, us=68.34.102.231:8333, peer=6 2015-10-15 01:24:30 Added time data, samples 7, offset -1 (+0 minutes) 2015-10-15 01:24:30 nTimeOffset = -2 (+0 minutes) 2015-10-15 01:24:38 receive version message: /Satoshi:0.11.0/: version 70002, blocks=375915, us=68.34.102.231:8333, peer=7 2015-10-15 01:24:38 Added time data, samples 8, offset -2 (+0 minutes) 2015-10-15 01:24:38 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:24:52 receive version message: /bitcoinj:0.14SNAPSHOT/: version 70001, blocks=378937, us=127.0.0.1:8333, peer=8 2015-10-15 01:24:52 Added time data, samples 9, offset -1 (+0 minutes) 2015-10-15 01:24:52 nTimeOffset = -2 (+0 minutes) 2015-10-15 01:24:54 receive version message: /bitnodes.21.co:0.1/: version 70002, blocks=378936, us=68.34.102.231:8333, peer=9 2015-10-15 01:24:54 Added time data, samples 10, offset -2 (+0 minutes) 2015-10-15 01:24:54 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=68.34.102.231:8333, peer=10 2015-10-15 01:24:54 Added time data, samples 11, offset -19 (+0 minutes) 2015-10-15 01:24:54 nTimeOffset = -2 (+0 minutes) 2015-10-15 01:24:56 receive version message: /Satoshi:0.9.3/: version 70002, blocks=377855, us=68.34.102.231:61867, peer=11 2015-10-15 01:24:56 Added time data, samples 12, offset -1 (+0 minutes) 2015-10-15 01:24:59 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:01 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:03 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:06 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:08 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:08 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:10 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-10-15 01:25:10 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:11 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:11 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:12 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=68.34.102.231:8333, peer=12 2015-10-15 01:25:12 Added time data, samples 13, offset -2 (+0 minutes) 2015-10-15 01:25:12 nTimeOffset = -2 (+0 minutes) 2015-10-15 01:25:15 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:15 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:15 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-10-15 01:25:16 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=68.34.102.231:8333, peer=13 2015-10-15 01:25:16 Added time data, samples 14, offset -1 (+0 minutes) 2015-10-15 01:25:19 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:28 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:29 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-10-15 01:25:36 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=354548, us=68.34.102.231:8333, peer=14 2015-10-15 01:25:36 Added time data, samples 15, offset -1 (+0 minutes) 2015-10-15 01:25:36 nTimeOffset = -2 (+0 minutes) 2015-10-15 01:25:39 ERROR: CScriptCheck(): 26f9721a3b748fb69fb57c6fd927931a6d8e53632789edca55abd7c7cbd1bcf0:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high 2015-10-15 01:25:39 ERROR: AcceptToMemoryPool: ConnectInputs failed 26f9721a3b748fb69fb57c6fd927931a6d8e53632789edca55abd7c7cbd1bcf0 2015-10-15 01:25:53 ERROR: CScriptCheck(): dd52cc689d6531de0c68077df409286c2b9799af37f299f1f9ca7868cc0dc9bb:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high 2015-10-15 01:25:53 ERROR: AcceptToMemoryPool: ConnectInputs failed dd52cc689d6531de0c68077df409286c2b9799af37f299f1f9ca7868cc0dc9bb 2015-10-15 01:25:54 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:59 ERROR: AcceptToMemoryPool: non-final 2015-10-15 01:25:59 ERROR: CScriptCheck(): 13863052ce70d262fe33ca8b266bb5151251370ba9558625e7f63fac5c82e2b8:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high

  2. PRabahy commented at 2:05 PM on October 17, 2015: contributor

    Here is the full log that I have. http://sebsauvage.net/paste/?9a8243edb52a669a#McTIeTHqqLa+SSMke9+qSefgRZmA2bgQthdhhBjj884=

    I want to get my node working again, but also want to help get this issue debugged. My plan is to restart my node with -reindex in the next day or two to try to resolve the issue, but I don't want that to blow away any data that might be needed.

  3. dcousens commented at 11:44 PM on October 17, 2015: contributor

    2015-10-13 01:41:03 receive version message: /BitCoinJ:0.12SNAPSHOT/Satoshi:0.11.0/: version 70001, blocks=378647, us=127.0.0.1:8333, peer=10716

    Not sure if related, but is it normal for there to be so many new peers? (sounds like it is the same one over and over)

    edit: In fact, this takes up most of the first third of your log. It also seems to be binding to your local interface instead of your public (which most 'other' nodes seem to be connecting to).

    Is there anything irregular about your set up other than just bitcoind on a box?

  4. PRabahy commented at 5:24 AM on October 18, 2015: contributor

    Um... I wonder if that is a bitcoin client that I am running from my phone. I run both Bitcoin Wallet and MyCelium on my Android phone. When I am home, my phone would be on the same LAN as my bitcoin computer.

    Anything irregular... It is a Windows 7 64bit box. I use symlinks to put the blocks on a different drive than the rest of the bitcoin files (C:\Users\PRabahy\AppData\Roaming -> F:\Bitcoin and F:\Bitcoin\blocks -> E:\Bitcoin_blocks). I sometimes run Armory on the machine that runs Bitcoin-qt. I always run Bitcoin-qt with the wallet disabled. I think that covers it for stuff that would be relevant to Bitcoin not working properly.

  5. laanwj commented at 7:33 AM on October 20, 2015: member

    Relevant part seems to be:

    2015-10-15 01:23:49 ERROR: AcceptBlockHeader: block is marked invalid
2015-10-15 01:23:49 ERROR: invalid header received
2015-10-15 01:23:49 ProcessMessages(headers, 2593 bytes) FAILED peer=2

    Looks like the next block in the chain is somehow marked invalid. Could you try reconsiderblock on the block it is stuck on, as well as the block after it?

  6. laanwj added the label Bug on Oct 20, 2015
  7. laanwj commented at 7:34 AM on October 20, 2015: member

    What version did you upgrade from?

  8. PRabahy commented at 10:56 AM on October 20, 2015: contributor

    I upgraded from 0.11.0. I'll try reconsiderblock if it gets stuck again, but I started a -reindex yesterday. I am currently 30 weeks behind.

  9. PRabahy commented at 10:36 PM on October 20, 2015: contributor

    Reindex fixed it. I'm not sure if there is going to be much more that we can do.

  10. laanwj commented at 8:49 AM on October 21, 2015: member

    Yes, unfortunately: not enough information to troubleshoot, no path to reproduce this

  11. laanwj closed this on Oct 21, 2015
  12. hwinkler commented at 12:49 AM on October 22, 2015: none

    I just upgraded to 0.11.1 and I too now see a great many "VerifySignature failed: Non-canonical signature: S value is unnecessarily high"

    Edit: Ubuntu 14.04, using bitcoin ppa

  13. PRabahy commented at 11:11 AM on October 22, 2015: contributor

    @hwinkler Yep, that's expected. It is mentioned in the "Test for LowS signatures before relaying" section of https://bitcoin.org/en/release/v0.11.1. Basically its a step forward in reducing and eliminating transaction malleability.

  14. MarcoFalke locked this on Sep 8, 2021
Contributors
PRabahydcousenslaanwjhwinkler
Labels
Bug
Linked (view graph)
#7301 syncing stopped. coinbase pays too much
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-26 09:16 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me