I'm going to guess you have a corrupt database then. Start your client with -reindex command.
EDIT: sorry for being unclear the submitblock command was in the console -reindex needs to be passed as a command when starting the client or you can add reindex ( without hyphen ) to your conf file.
Topic: New Tor 3.6.3, no Vidalia, now Bitcoin-Qt can't connect (Read 2169 times)
EDIT: Here is the raw block, try "submitblock "
Like in the debug window console? It responds with "Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade. (code -2)", and the information tab still lists 312933.
EDIT: I don't know what I am looking for, but I see nothing in the log that would seem to correspond to the submitblock.
Thanks for chiming in Challisto.
I'm over my depth here. But things continue to look funny. If you scrutinize your linked transaction, it indicates that 13MuqnHSqDX1KyCM4GKpT3ZkvqwxyiRor2 has been spent.
But if you look at https://blockchain.info/block/0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665, it shows 13MuqnHSqDX1KyCM4GKpT3ZkvqwxyiRor2 as unspent.
That just seems weird to me.
Further, isn't it normal to receive invalid blocks? Should my client not just have discarded it, and grabbed another copy of height 312934?
I'm over my depth here. But things continue to look funny. If you scrutinize your linked transaction, it indicates that 13MuqnHSqDX1KyCM4GKpT3ZkvqwxyiRor2 has been spent.
But if you look at https://blockchain.info/block/0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665, it shows 13MuqnHSqDX1KyCM4GKpT3ZkvqwxyiRor2 as unspent.
That just seems weird to me.
Further, isn't it normal to receive invalid blocks? Should my client not just have discarded it, and grabbed another copy of height 312934?
Code:
2014-07-29 18:50:19 received block 0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665
2014-07-29 18:50:20 ERROR: CScriptCheck() : a8ef403bc8dbb6274539c14c42c2029ccea150cdb6a63a0969a908aabe4c34a8 VerifySignature failed
2014-07-29 18:50:20 InvalidChainFound: invalid block=0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 height=312934 log2_work=79.938362 date=2014-07-29 01:18:42
2014-07-29 18:50:20 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:50:20 InvalidChainFound: invalid block=0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 height=312934 log2_work=79.938362 date=2014-07-29 01:18:42
2014-07-29 18:50:20 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:50:20 ERROR: SetBestBlock() : ConnectBlock 0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 failed
2014-07-29 18:50:20 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-07-29 18:50:20 ERROR: ProcessBlock() : AcceptBlock FAILED
This transaction verification fails on your node for some reason. This causes the block to be rejected, but the entire network has accepted this block as valid and is continuing to build on it. Something is odd here. I'm trying right now to get the block data from my node, "getblock 0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 false", but all it does is cause my cpu to run at 100%.
EDIT: Took about 7 minutes to get the raw block
EDIT: Here is the raw block, try "submitblock
The message simply means you are not completely synced. The db is fine. Let me know if Bitcoin Core starts syncing once you let it run for a bit.
Nope - still stuck at block 312933. I've done some spelunking in the logs. Bearing in mind that I've not scrutinized bitcoind logs before, I think the problem is that nobody will send me block 312934, even though I tell them on connection that I've got 312933.
Code:
...
2014-07-29 18:50:10 Committing 41364 changed transactions to coin database...
2014-07-29 18:50:12 SetBestChain: new best=00000000000000002d13084f12db627f25ee3f8c3d4b5ecd4bb4273db3586c5c height=312930 log2_work=79.937961 tx=43420240 date=2014-07-29 00:33:47 progress=0.998261
2014-07-29 18:50:12 ProcessBlock: ACCEPTED
2014-07-29 18:50:12 received block 00000000000000000cff90ee70512f98a69fc70f540ab71e014ab2e36d937912
2014-07-29 18:50:12 Committing 599 changed transactions to coin database...
2014-07-29 18:50:12 SetBestChain: new best=00000000000000000cff90ee70512f98a69fc70f540ab71e014ab2e36d937912 height=312931 log2_work=79.938061 tx=43420398 date=2014-07-29 00:36:59 progress=0.998266
2014-07-29 18:50:12 ProcessBlock: ACCEPTED
2014-07-29 18:50:16 received block 0000000000000000024cdf17308087ecd93bb10b42287898c455d9a6fec642e3
2014-07-29 18:50:18 Committing 2837 changed transactions to coin database...
2014-07-29 18:50:18 SetBestChain: new best=0000000000000000024cdf17308087ecd93bb10b42287898c455d9a6fec642e3 height=312932 log2_work=79.938161 tx=43421235 date=2014-07-29 01:03:13 progress=0.998308
2014-07-29 18:50:18 ProcessBlock: ACCEPTED
2014-07-29 18:50:18 received block 00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4
2014-07-29 18:50:18 Committing 311 changed transactions to coin database...
2014-07-29 18:50:18 SetBestChain: new best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 tx=43421321 date=2014-07-29 01:03:42 progress=0.998308
2014-07-29 18:50:18 ProcessBlock: ACCEPTED
2014-07-29 18:50:19 received block 0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665
2014-07-29 18:50:20 ERROR: CScriptCheck() : a8ef403bc8dbb6274539c14c42c2029ccea150cdb6a63a0969a908aabe4c34a8 VerifySignature failed
2014-07-29 18:50:20 InvalidChainFound: invalid block=0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 height=312934 log2_work=79.938362 date=2014-07-29 01:18:42
2014-07-29 18:50:20 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:50:20 InvalidChainFound: invalid block=0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 height=312934 log2_work=79.938362 date=2014-07-29 01:18:42
2014-07-29 18:50:20 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:50:20 ERROR: SetBestBlock() : ConnectBlock 0000000000000000371fcf07810c3ac1b9c17daa5ddc9710dea32158d3f75665 failed
2014-07-29 18:50:20 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-07-29 18:50:20 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-07-29 18:50:20 Misbehaving: 202.46.224.184:8333 (0 -> 100) DISCONNECTING
2014-07-29 18:50:20 disconnecting node 202.46.224.184:8333
2014-07-29 18:50:20 socket select error 9
2014-07-29 18:51:46 ERROR: Proxy error: TTL expired
2014-07-29 18:51:46 trying connection dnsseed.bluematt.me lastseen=0.0hrs
2014-07-29 18:51:46 SOCKS5 connecting dnsseed.bluematt.me
2014-07-29 18:51:47 SOCKS5 connected dnsseed.bluematt.me
2014-07-29 18:51:47 connected dnsseed.bluematt.me
2014-07-29 18:51:47 send version message: version 70001, blocks=312933, us=5.79.68.161:8333, them=0.0.0.0:0, peer=0.0.0.0:0
2014-07-29 18:51:47 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=313043, us=37.130.227.133:38676, them=92.108.78.71:8333, peer=0.0.0.0:0
2014-07-29 18:51:47 trying connection 176.196.31.188:8333 lastseen=32.2hrs
2014-07-29 18:51:47 SOCKS5 connecting 176.196.31.188
2014-07-29 18:51:50 Added 666 addresses from 0.0.0.0: 1251 tried, 14219 new
2014-07-29 18:51:50 disconnecting node dnsseed.bluematt.me
2014-07-29 18:51:54 ERROR: Proxy error: TTL expired
2014-07-29 18:51:54 trying connection dnsseed.bitcoin.dashjr.org lastseen=0.0hrs
2014-07-29 18:51:54 SOCKS5 connecting dnsseed.bitcoin.dashjr.org
2014-07-29 18:53:55 ERROR: Proxy error: host unreachable
2014-07-29 18:53:56 trying connection 71.200.202.72:8333 lastseen=2360.3hrs
2014-07-29 18:53:56 SOCKS5 connecting 71.200.202.72
2014-07-29 18:54:53 ERROR: Proxy error: TTL expired
2014-07-29 18:54:53 trying connection bitseed.xf2.org lastseen=0.0hrs
2014-07-29 18:54:53 SOCKS5 connecting bitseed.xf2.org
2014-07-29 18:54:54 SOCKS5 connected bitseed.xf2.org
2014-07-29 18:54:54 connected bitseed.xf2.org
2014-07-29 18:54:54 send version message: version 70001, blocks=312933, us=5.79.68.161:8333, them=0.0.0.0:0, peer=0.0.0.0:0
2014-07-29 18:54:54 receive version message: /Satoshi:0.9.1/: version 70002, blocks=313043, us=109.163.234.2:3412, them=209.208.110.92:8333, peer=0.0.0.0:0
2014-07-29 18:54:54 trying connection 80.86.85.95:8333 lastseen=8.3hrs
2014-07-29 18:54:54 SOCKS5 connecting 80.86.85.95
2014-07-29 18:54:55 SOCKS5 connected 80.86.85.95
2014-07-29 18:54:55 connected 80.86.85.95:8333
2014-07-29 18:54:55 send version message: version 70001, blocks=312933, us=5.79.68.161:8333, them=80.86.85.95:8333, peer=80.86.85.95:8333
2014-07-29 18:54:55 trying connection dnsseed.bitcoin.dashjr.org lastseen=0.0hrs
2014-07-29 18:54:55 SOCKS5 connecting dnsseed.bitcoin.dashjr.org
2014-07-29 18:54:55 Added time data, samples 4, offset -4 (+0 minutes)
2014-07-29 18:54:55 receive version message: /Satoshi:0.8.2.2/: version 70001, blocks=313043, us=109.163.234.2:9257, them=80.86.85.95:8333, peer=80.86.85.95:8333
2014-07-29 18:54:56 stored orphan tx 9a2481c6ed0ca05336df6237921663453a4e739e746435aa550e06039484cae6 (mapsz 1)
2014-07-29 18:54:57 received block 000000000000000011191b14eaf5c628f349384489c50e165ce406407ffdacfd
2014-07-29 18:54:57 InvalidChainFound: invalid block=000000000000000011191b14eaf5c628f349384489c50e165ce406407ffdacfd height=312935 log2_work=79.938462 date=2014-07-29 01:28:06
2014-07-29 18:54:57 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:54:57 ProcessBlock: ACCEPTED
2014-07-29 18:54:57 received block 00000000000000001106927a48e84a5f846d1890667834b651f98d2ec10ea9a6
2014-07-29 18:54:57 InvalidChainFound: invalid block=00000000000000001106927a48e84a5f846d1890667834b651f98d2ec10ea9a6 height=312936 log2_work=79.938562 date=2014-07-29 01:36:33
2014-07-29 18:54:57 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:54:57 ProcessBlock: ACCEPTED
2014-07-29 18:54:58 received block 000000000000000004a83f1906e06483927c50b11c73dffc108a1f0277284067
2014-07-29 18:54:58 InvalidChainFound: invalid block=000000000000000004a83f1906e06483927c50b11c73dffc108a1f0277284067 height=312937 log2_work=79.938662 date=2014-07-29 01:41:22
2014-07-29 18:54:58 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:54:58 ProcessBlock: ACCEPTED
2014-07-29 18:54:59 received block 0000000000000000280339c79066e3efefd2ed981c17456f05f84b8857302db4
2014-07-29 18:54:59 InvalidChainFound: invalid block=0000000000000000280339c79066e3efefd2ed981c17456f05f84b8857302db4 height=312938 log2_work=79.938762 date=2014-07-29 01:58:58
2014-07-29 18:54:59 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:54:59 ProcessBlock: ACCEPTED
2014-07-29 18:54:59 received block 00000000000000000287c9d83019e1f6c2530108f01a61c5202fad8500ec9b52
2014-07-29 18:54:59 InvalidChainFound: invalid block=00000000000000000287c9d83019e1f6c2530108f01a61c5202fad8500ec9b52 height=312939 log2_work=79.938863 date=2014-07-29 02:09:19
2014-07-29 18:54:59 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:54:59 ProcessBlock: ACCEPTED
2014-07-29 18:55:00 received block 00000000000000001aefd23d14629bb05225cd09373a2c7e9c129627cddd64a6
2014-07-29 18:55:00 InvalidChainFound: invalid block=00000000000000001aefd23d14629bb05225cd09373a2c7e9c129627cddd64a6 height=312940 log2_work=79.938963 date=2014-07-29 02:15:55
2014-07-29 18:55:00 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:55:00 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-07-29 18:55:00 ProcessBlock: ACCEPTED
2014-07-29 18:55:00 received block 000000000000000008598e9c80bc53acd1cb905ce5808ff527afc4253930be3c
2014-07-29 18:55:00 InvalidChainFound: invalid block=000000000000000008598e9c80bc53acd1cb905ce5808ff527afc4253930be3c height=312941 log2_work=79.939063 date=2014-07-29 02:18:12
2014-07-29 18:55:00 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:55:00 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-07-29 18:55:00 ProcessBlock: ACCEPTED
...
That host continues to send subsequent blocks 312935..313043 (highest he has, as listed in his version message?). Note the appearance of the additional message "InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." at 312940 et seq.
It then seems to settle into a mode of receiving incoming transactions, most of which it cannot resolve:
Code:
...
2014-07-29 18:55:57 received block 00000000000000001250d7f59065fa4ca1b860c7a4b479ceb3d88dfad63f34b1
2014-07-29 18:55:57 InvalidChainFound: invalid block=00000000000000001250d7f59065fa4ca1b860c7a4b479ceb3d88dfad63f34b1 height=313042 log2_work=79.949146 date=2014-07-29 18:39:12
2014-07-29 18:55:57 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:55:57 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-07-29 18:55:57 ProcessBlock: ACCEPTED
2014-07-29 18:55:57 received block 00000000000000002acf0ec600909115fb0acfa632ec4e79119a733a081175aa
2014-07-29 18:55:57 InvalidChainFound: invalid block=00000000000000002acf0ec600909115fb0acfa632ec4e79119a733a081175aa height=313043 log2_work=79.949245 date=2014-07-29 18:40:10
2014-07-29 18:55:57 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:55:57 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-07-29 18:55:57 ProcessBlock: ACCEPTED
2014-07-29 18:55:57 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 78da698b18e543dfcd4a9ee05fe8d6f81c53b8effec1a6ec112889de635806ef (poolsz 1)
2014-07-29 18:55:57 stored orphan tx 6ed253e7f195fcfbd2cb311ded6df1541974fe8450f0326d42d75d9ee76faf1d (mapsz 2)
2014-07-29 18:55:57 stored orphan tx b3f8f06135d0541a4fcf41b5935948da008e88f060933194a53b9a06b36039d9 (mapsz 3)
2014-07-29 18:55:57 stored orphan tx c2a03b6299089657c7e37b8f383ce03e1d4a00417dbda20678e484c7c3e5852b (mapsz 4)
2014-07-29 18:55:57 stored orphan tx 3559c480ff81274c2b62421f7ebfe2dcd8afa7d99574165a1ecec33f8bbfea10 (mapsz 5)
2014-07-29 18:55:57 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 520cd891d75f29947916da0bd74f857ec17f440a3667b15cc2a49f2b75f12b8f (poolsz 2)
2014-07-29 18:55:57 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 6b98d9208feb1b091c3f26b30b5f686fc76879ef5679917b1af03c638202dcc4 (poolsz 3)
2014-07-29 18:55:57 stored orphan tx 12f63f9460ecdeb1fcc1b82dbc1ae752d58a7503fab7949c49d7789d82b89d13 (mapsz 6)
2014-07-29 18:55:57 stored orphan tx fbc5c7014aec6858f2fba13ba9beb6ee4f3903ecbde7a279267b714f3887eeff (mapsz 7)
2014-07-29 18:55:57 stored orphan tx 43bd69fd487bd3abb878b8d8e2987c72ca20aed0ac6b46c6e4473c957884b65d (mapsz 8)
2014-07-29 18:55:57 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 8c44d801898140a630c3a7b668c35db91b7264c02d2f62709a0ed6e009a3e8a6 (poolsz 4)
2014-07-29 18:55:57 stored orphan tx 0ac43eb041a627798e9a64bfbec973c0a2404704b9df0d5b529d765c8a74aad7 (mapsz 9)
2014-07-29 18:55:57 stored orphan tx 579e0f69bde7cf898457300fbcc876a04b3b3422276145eb17034e879d87d854 (mapsz 10)
2014-07-29 18:55:57 stored orphan tx 17c6d066c4ab96f35d26bc46057998abb745c0ab520182fe388cfff99744b687 (mapsz 11)
2014-07-29 18:55:57 stored orphan tx 810990ca98afbe8df35cedfab78b872920bd088072aa6a06e05f6d656216ff0d (mapsz 12)
2014-07-29 18:55:57 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 60b93d2c14566b970c406de619e2904dc1a42f9fb138b3204fc71cfcebd34983 (poolsz 5)
2014-07-29 18:55:57 stored orphan tx a7adfb7c2ba3d202e54a36c6cab28090eeb6c448efe1f368e702d9b1e1593c28 (mapsz 13)
2014-07-29 18:55:57 stored orphan tx 9e1207fd2e377c386d31c79a0fd68735bdee7ab4eab397959a8b8c0728cd8faf (mapsz 14)
2014-07-29 18:55:57 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted d1fe994bdf5b3bac1c1c7afc23fe23402e96d60de4a0777983185ff5d4bf060a (poolsz 6)
2014-07-29 18:55:57 stored orphan tx 5ea6b013d58b127971e68031baeeec193af7e99c332a1790fda05bdbdf9393ce (mapsz 15)
2014-07-29 18:55:57 stored orphan tx 45440d25e5197de9c3006a1e09ef17c58dc96c326a18bc10b151238c9f4f200d (mapsz 16)
2014-07-29 18:55:57 stored orphan tx 5a333623d89a9f14837770b18201a4745f8a4a3238f2f5c4c21b518473a17a30 (mapsz 17)
2014-07-29 18:55:57 stored orphan tx d41c78ac1247a95411439bcd9f1cca3fd6579d78b417baed2baf3f18279db8e0 (mapsz 18)
2014-07-29 18:55:57 stored orphan tx aad537d2e65968da2eff5964ffc1c90aac5b01193b61338f65d7dd7364dd69d6 (mapsz 19)
...
It periodically receives another block, which it cannot add, as it still has not seen 312934:
Code:
...
2014-07-29 18:56:16 stored orphan tx 1695dc7b0d55d8b1e79cba41fcb4baf9354486e42cb9bea743ae63cb7bebefef (mapsz 40)
2014-07-29 18:56:16 stored orphan tx 91bb6d92c6c3896a4b6b56b5efba01113e8c98f5b13947221d4b08e60380b062 (mapsz 41)
2014-07-29 18:56:20 received block 00000000000000000e83bbcc35f638ab6b1216950f94d655a2f9fc65a4ebbc10
2014-07-29 18:56:20 InvalidChainFound: invalid block=00000000000000000e83bbcc35f638ab6b1216950f94d655a2f9fc65a4ebbc10 height=313044 log2_work=79.949345 date=2014-07-29 18:55:43
2014-07-29 18:56:20 InvalidChainFound: current best=00000000000000000be786475800ebb520270b2edba8316a6a8afb287f19dec4 height=312933 log2_work=79.938261 date=2014-07-29 01:03:42
2014-07-29 18:56:20 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-07-29 18:56:20 ProcessBlock: ACCEPTED
2014-07-29 18:56:20 stored orphan tx 20444212a2c902cbc5f052efc483d3ec17a6815e33baeb616182b15cca3ae795 (mapsz 42)
2014-07-29 18:56:21 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 384266cdb2877a5e9cbfdf19a70e8fabb69738a8eec75d113a86dfbf532f3d5e (poolsz 15)
2014-07-29 18:56:21 stored orphan tx 0013fc4a82df6136b751c5a1bbcd6cfbd8de880e90df5ead847146257d3f04a2 (mapsz 43)
...
Every once in a while it connects to someone new - but they won't send 312934 either:
Code:
...
2014-07-29 18:58:31 stored orphan tx f62b7e67e55c72c3d0afb5e2d252e24ffd49fdca59580b3be83d711dad6cea81 (mapsz 151)
2014-07-29 18:58:36 stored orphan tx fbf2200f19e0361ccc3cb6bb52fd67f6ab6af4e27cd6fcce855423528481894e (mapsz 152)
2014-07-29 18:58:36 SOCKS5 connected 98.230.176.161
2014-07-29 18:58:36 connected 98.230.176.161:8333
2014-07-29 18:58:36 send version message: version 70001, blocks=312933, us=5.79.68.161:8333, them=98.230.176.161:8333, peer=98.230.176.161:8333
2014-07-29 18:58:36 trying connection dnsseed.bitcoin.dashjr.org lastseen=0.0hrs
2014-07-29 18:58:36 SOCKS5 connecting dnsseed.bitcoin.dashjr.org
2014-07-29 18:58:37 Added time data, samples 5, offset -20 (+0 minutes)
2014-07-29 18:58:37 nTimeOffset = -4 (+0 minutes)
2014-07-29 18:58:37 receive version message: /Satoshi:0.9.0/: version 70002, blocks=312965, us=94.242.255.236:56404, them=98.230.176.161:8333, peer=98.230.176.161:8333
2014-07-29 18:58:37 getblocks 312925 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-07-29 18:58:38 Added 639 addresses from 98.230.176.161: 1251 tried, 14285 new
2014-07-29 18:58:38 Added 650 addresses from 98.230.176.161: 1251 tried, 14313 new
2014-07-29 18:58:38 Added 320 addresses from 98.230.176.161: 1251 tried, 14317 new
2014-07-29 18:58:38 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-07-29 18:58:48 Added 1 addresses from 80.86.85.95: 1251 tried, 14317 new
2014-07-29 18:58:48 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted a2551889f40d563af50f486cde23fcc900ddc67092edae614a370bd57efb674e (poolsz 38)
2014-07-29 18:58:48 stored orphan tx ca3798176f7428db07c5c45d257469499b28c3857f3bc84ffe35d60ef7a71b3f (mapsz 153)
2014-07-29 18:58:48 stored orphan tx 448d7daf41498515e4d79cb7f447a53bbd6b380cb6f1b3acc2284a8ede1c68b8 (mapsz 154)
...
and
Code:
...
2014-07-29 19:07:48 stored orphan tx 4a58e9c43bea6396286b65065bf1d7f09d277ab95815f8e87b7e03c67c89900e (mapsz 525)
2014-07-29 19:07:50 stored orphan tx c16e62805677431e19d123fd092a08e6071c752c9b8e66a6020882598aad696d (mapsz 526)
2014-07-29 19:07:50 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted 427df0833336f86b45c53e489942f9f765c09df300d63312317b7c59f844af0a (poolsz 122)
2014-07-29 19:07:50 AcceptToMemoryPool: 80.86.85.95:8333 /Satoshi:0.8.2.2/ : accepted f54e646a5371633f83969f59865f1282ed59b217b06a1c284d477da76283d6d1 (poolsz 123)
2014-07-29 19:07:52 stored orphan tx b76274d45e75f152c79bcf83e3c91f75e77a386b202b3cccbe6e3e11397f8f17 (mapsz 527)
2014-07-29 19:07:53 received getdata for: tx 427df0833336f86b45c53e489942f9f765c09df300d63312317b7c59f844af0a
2014-07-29 19:07:54 ERROR: Proxy error: host unreachable
2014-07-29 19:07:55 trying connection 24.121.133.163:8333 lastseen=5.7hrs
2014-07-29 19:07:55 SOCKS5 connecting 24.121.133.163
2014-07-29 19:07:55 Added 1 addresses from 80.86.85.95: 1251 tried, 14300 new
2014-07-29 19:07:55 SOCKS5 connected 24.121.133.163
2014-07-29 19:07:55 connected 24.121.133.163:8333
2014-07-29 19:07:55 send version message: version 70001, blocks=312933, us=5.79.68.161:8333, them=24.121.133.163:8333, peer=24.121.133.163:8333
2014-07-29 19:07:55 trying connection dnsseed.bitcoin.dashjr.org lastseen=0.0hrs
2014-07-29 19:07:55 SOCKS5 connecting dnsseed.bitcoin.dashjr.org
2014-07-29 19:07:56 stored orphan tx acdb0af7fb7ecfb638a841a1d2f67ce6f98b5ce7d85c41f95ea2a69db29cb8b0 (mapsz 528)
2014-07-29 19:07:56 Added time data, samples 7, offset -5 (+0 minutes)
2014-07-29 19:07:56 nTimeOffset = -5 (+0 minutes)
2014-07-29 19:07:56 receive version message: /Satoshi:0.9.1/: version 70002, blocks=313044, us=178.175.139.138:16764, them=24.121.133.163:8333, peer=24.121.133.163:8333
2014-07-29 19:07:57 Added 662 addresses from 24.121.133.163: 1251 tried, 14289 new
2014-07-29 19:07:58 Added 663 addresses from 24.121.133.163: 1251 tried, 14294 new
2014-07-29 19:07:58 Added 341 addresses from 24.121.133.163: 1251 tried, 14311 new
2014-07-29 19:08:00 stored orphan tx ee9ed5388b0316bc9cc8ff94634618de3e245b0981eb901d752fc4fd1e481231 (mapsz 529)
2014-07-29 19:08:04 socket no message in first 60 seconds, 0 1
2014-07-29 19:08:04 disconnecting node 71.9.51.33:8333
2014-07-29 19:08:04 stored orphan tx 45cb13c74f79841b3e4a526d7eab8977ce4a2aafdfbfcd56978756b47998dea2 (mapsz 530)
2014-07-29 19:08:08 stored orphan tx 4c86c2f769cbe85b3734648fea8cbde891e561af282d58a698d0a74770420f49 (mapsz 531)
...
Actually, AFAICT, none of these other connections sends any blocks whatsoever - why is that? Does the
Code:
them=0.0.0.0, peer=0.0.0.0
in the send version message mean 'send me blocks', and any other values mean 'don't send me blocks'? Seems kinda wonky.
But to cut to the chase - how do I get a copy of 312934?
Shut down, restarted Bitcoin-Qt. New error message on dialog: "Warning: displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Maybe the error is merely because it already knows that it is not caught up with the tip? If so, perhaps the db is OK? Should I just wait it out?
Maybe the error is merely because it already knows that it is not caught up with the tip? If so, perhaps the db is OK? Should I just wait it out?
The message simply means you are not completely synced. The db is fine. Let me know if Bitcoin Core starts syncing once you let it run for a bit.
Funny thing there... way back when, I set Armory to autostart bitcoind - but it never did. I still need to run it (well, Bitcoin-Qt) manually.
Are you sure Armory won't autostart bitcoind? Bitcoind is Bitcoin Core without the user interface. It won't show up on your desktop, but you can confirm it is running through Activity Monitor (Mac version of Task Manager).
I am still somewhat confused by the interaction between bitcoin.conf, and the fields in Bitcoin-Qt>Preferences. I had already changed some of those through the GUI. I was puzzled that invoking 'touch bitcoin.conf' at the prompt did not revert all the settings in the GUI to defaults. Yes, I had terminated Bitcoin-Qt before creating the file.
From my experience the bitcoin.conf only affects the settings which are set in the file. If you don't have an option for it in bitcoin.conf file it will stay as it is.
Hmm. I seem to be going from bad to worse.
Shut down, restarted Bitcoin-Qt. New error message on dialog: "Warning: displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Shutdown Bitcoin-Qt, shutdown TorBrowser, restarted TorBrowser, restarted Bitcoin-Qt. Same error.
Shutdown Bitcoin-Qt, reverted port=8333 to listen=1, restarted Bitcoin-Qt. Same error.
Shutdown Bitcoin-Qt, mv bitcoin.conf, restarted Bitcoin-Qt. Same error.
Shutdown Bitcoin-Qt, changed settings in GUI to not use proxy, restarted Bitcoin-Qt. Same error.
I'm guessing my database is corrupted? But...
Maybe the error is merely because it already knows that it is not caught up with the tip? If so, perhaps the db is OK? Should I just wait it out?
Shut down, restarted Bitcoin-Qt. New error message on dialog: "Warning: displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Shutdown Bitcoin-Qt, shutdown TorBrowser, restarted TorBrowser, restarted Bitcoin-Qt. Same error.
Shutdown Bitcoin-Qt, reverted port=8333 to listen=1, restarted Bitcoin-Qt. Same error.
Shutdown Bitcoin-Qt, mv bitcoin.conf, restarted Bitcoin-Qt. Same error.
Shutdown Bitcoin-Qt, changed settings in GUI to not use proxy, restarted Bitcoin-Qt. Same error.
I'm guessing my database is corrupted? But...
Code:
2014-07-29 23:14:34 No coin database inconsistencies in last 74 blocks (38162 transactions)
Maybe the error is merely because it already knows that it is not caught up with the tip? If so, perhaps the db is OK? Should I just wait it out?
Looks like your using my bitcoin.conf file from here (minus the update I just made):https://bitcointalksearch.org/topic/m.6917399
I thought your avatar looked familiar... yes, that's where I grabbed the bitcoin.conf contents.
Quote
Can I also assume that all other configuration is the same (besides Armory not being set to start Bitcoind on it own)?
Funny thing there... way back when, I set Armory to autostart bitcoind - but it never did. I still need to run it (well, Bitcoin-Qt) manually.
To answer the question, I guess so.
I am still somewhat confused by the interaction between bitcoin.conf, and the fields in Bitcoin-Qt>Preferences. I had already changed some of those through the GUI. I was puzzled that invoking 'touch bitcoin.conf' at the prompt did not revert all the settings in the GUI to defaults. Yes, I had terminated Bitcoin-Qt before creating the file.
Indeed, after creating a meaningful bitcoin.conf, all the settings are as I last set through the GUI, with the exception of the port 9150.
So the effective settings seem to be some inscrutable combination of GUI settings and bitcoin.conf? Fragile. Well, I probably just don't yet see the obvious relationship between the two.
Quote
...
port=8333 (Listen for connections on port 8333. This allows Bitcoin Core to talk to Armory on port 8333 while talking to Tor on port 9150.)
...
None of the options should prevent you from syncin while your connected. Try restarting your computer and see if that helps.
port=8333 (Listen for connections on port 8333. This allows Bitcoin Core to talk to Armory on port 8333 while talking to Tor on port 9150.)
...
None of the options should prevent you from syncin while your connected. Try restarting your computer and see if that helps.
Hours later, still stuck at the same point. I'll give the above a try.
The manpage (or lack thereof) is kind of weak. The explanations of the options are rather ambiguous. Yeah I know - patch & pull request
Looks like your using my bitcoin.conf file from here (minus the update I just made):https://bitcointalksearch.org/topic/m.6917399
Can I also assume that all other configuration is the same (besides Armory not being set to start Bitcoind on it own)?
This isn't normal but I don't believe the problem is your config file. Here's what each option actually does(source=https://en.bitcoin.it/wiki/Running_Bitcoin:
bind=127.0.0.1 (Bind to given address and always listen on it. In other words Bitcoin Core only communicates with your computer and thus only with Armory or through Tor.)
port=8333 (Listen for connections on port 8333. This allows Bitcoin Core to talk to Armory on port 8333 while talking to Tor on port 9150.)
upnp=0 (Turns off UPnP. Not sure what UPnP is, but this needs to be turned of to properly use Tor)
proxy=127.0.0.1:9150 (Connect through SOCKS proxy. This is what tells Bitcoin Core to connect to Tor.)
None of the options should prevent you from syncin while your connected. Try restarting your computer and see if that helps. If that doesn't work try running Bitcoin Core without Tor. You'll have to remove the config file in order to run Bitcoin Core without Tor.
I reallize this is a lot of information without an actual solution, but hopefully this helps you or someone else solve your problem.
Can I also assume that all other configuration is the same (besides Armory not being set to start Bitcoind on it own)?
I have been sitting at 'Current number of blocks: 312933', 'Estimated total blocks 313044' since launch about an hour ago.
This isn't normal but I don't believe the problem is your config file. Here's what each option actually does(source=https://en.bitcoin.it/wiki/Running_Bitcoin:
bind=127.0.0.1 (Bind to given address and always listen on it. In other words Bitcoin Core only communicates with your computer and thus only with Armory or through Tor.)
port=8333 (Listen for connections on port 8333. This allows Bitcoin Core to talk to Armory on port 8333 while talking to Tor on port 9150.)
upnp=0 (Turns off UPnP. Not sure what UPnP is, but this needs to be turned of to properly use Tor)
proxy=127.0.0.1:9150 (Connect through SOCKS proxy. This is what tells Bitcoin Core to connect to Tor.)
None of the options should prevent you from syncin while your connected. Try restarting your computer and see if that helps. If that doesn't work try running Bitcoin Core without Tor. You'll have to remove the config file in order to run Bitcoin Core without Tor.
I reallize this is a lot of information without an actual solution, but hopefully this helps you or someone else solve your problem.
Tor isn't your bottleneck, maybe you're connected to a slow peer.
What settings or options are you using to connect Armory to Bitcoin Core while Bitcoin Core is connected through Tor?
All configuration necessary was done in bitcoin.conf. I did not previously have this file on my system. It now consists of:
Code:
bind=127.0.0.1
listen=1
upnp=0
proxy=127.0.0.1:9150
Of course, today, results are puzzling (synced and operated fine yesterday). I launched TorBrowser and fired up Bitcoin-Qt. While the debug window shows a varying number of connections have been made (currently 8 ), I have been sitting at 'Current number of blocks: 312933', 'Estimated total blocks 313044' since launch about an hour ago.
The fact that I am not caught up with the tip of the blockchain makes me think my config is broken. But the fact that I have connections (and I can see stored orphan tx's, Added Addresses, and other progress in the Console), indicates to me that things are working?
Note I typically (as today) refrain from launching Armory until Bitcoin-Qt syncs.
Should I worry that I am broken again? Does running across Tor just take that much longer?
ETA: closing paren
What settings or options are you using to connect Armory to Bitcoin Core while Bitcoin Core is connected through Tor?
Just for future reference here is a guide to properly set up your node to run behind Tor: bitcoin/doc/tor.md
You can add these nodes to your conf file "connect=" to help your node with connecting to the Bitcoin network.
You can add these nodes to your conf file "connect=
Just updating. Yeah - that works. TorBrowser needs to be running.
Indeed. Good to know that you got it up and running again OK.
Yes. You can of course attempt to 'Torify' any application by pointing it to your localhost ( i.e. 127.0.0.1 ) 9150 whilst the TBB is running.
The TBB now starts Tor directly and also closes Tor when you close TBB Firefox (which I agree is far from ideal).
It is possible to get a standalone Tor client running without using the TBB, although this does require some more technical knowledge of Tor.
If your running Tor 24/7 for your Bitcoin client mostly and not really using Tor for browsing the internet - then you should probably investigate how to set-up and run as a Tor Relay, as you actually get slightly increased anonymity that way.
Additional: I'd also recommend setting-up and running an Encrypted DNS as this makes it much harder for an adversary to track your connections when you bootstrap to the Tor network itself.
Here is a post I made with the links: https://bitcointalksearch.org/topic/m.8073451 - There is a Mac version of the DNS crypt client.
Just updating. Yeah - that works. TorBrowser needs to be running.
ETA: strikethrough. No, it is not working after all.
ETA: strikethrough. No, it is not working after all.
The TBB socks port is now 9150 (instead of 9050).
So I just update my Bitcoin-Qt settings to use this port? I'll give it a go.
I too miss Vidalia - although the new TTB is actually an improvement for regular internet users seeking increased privacy, once you get used to it, imho.
So without Vidalia, how do I invoke Tor to begin with? Does running the TorBrowser create a Tor connection for use by (e.g.) Bitcoin-Qt and other programs, as long as they use port 9150? Do I really need to be running a browser session that I don't use? Or is there some other way to set up port 9150?
The TBB socks port is now 9150 (instead of 9050).
You might find this interesting: https://bitcointalksearch.org/topic/m.6677546 (I will try to update this thread soon).
I too miss Vidalia - although the new TTB is actually an improvement for regular internet users seeking increased privacy, once you get used to it, imho.
However, recent updates have made running a relay or exit node unnecessarily complicated and somewhat difficult to update.
You might find this interesting: https://bitcointalksearch.org/topic/m.6677546 (I will try to update this thread soon).
I too miss Vidalia - although the new TTB is actually an improvement for regular internet users seeking increased privacy, once you get used to it, imho.
However, recent updates have made running a relay or exit node unnecessarily complicated and somewhat difficult to update.
First off, I am somewhat sketchy in my Tor knowledge. Second, I am Mac/OS X 10.7.5, should it be relevant. Third, I use Armory 0.90 atop Bitcoin-Qt v0.8.6-beta.
I have had this configuration working atop Tor 0.2.2.37, using Vidalia 0.2.20.
Upon launching Tor this morning, I got a message imploring me to update to the newest version of Tor. This was accompanied by a number of log messages indicating what seemed to be connection problems.
Despite these error messages, launching Bitcoin-Qt eventually seemed to result in syncing with the blockchain. However, upon launching Armory, I got an error indicating "Armory is Offline".
In a perhaps poorly reasoned decision, I decided I ought to update to the newest Tor, as suggested. I uninstalled Vidalia and TorBrowser (unused in my listed configuration).
Upon browsing to the Tor website, I discovered that Vidalia is seemingly no longer available. I dl'd and installed TorBrowser 3.6.3.
Launching TorBrowser seems to work - the https://check.torproject.org/?lang=en_US page tells me "Congratulations. This browser is configured to use Tor."
Launching Bitcoin-Qt (configured for SOCKS proxy on port 9050) seems to no longer work - while the top GUI tells me I am synced by means of a green checkmark, the debug console indicates 0 connections, and the 'Estimated total blocks, is behind what I can see at blockchain.info.
I would like to restore Bitcoin-Qt, and subsequently Armory, to a working configuration atop Tor. I am assuming that the change in Tor is what broke things. How do I restore operation? Is Tor no longer usable for anything but web browsing? That would seem silly. But why no control panel (Vidalia) any longer? Is there a tor.conf or similar that should be used for configuration?
I have had this configuration working atop Tor 0.2.2.37, using Vidalia 0.2.20.
Upon launching Tor this morning, I got a message imploring me to update to the newest version of Tor. This was accompanied by a number of log messages indicating what seemed to be connection problems.
Despite these error messages, launching Bitcoin-Qt eventually seemed to result in syncing with the blockchain. However, upon launching Armory, I got an error indicating "Armory is Offline".
In a perhaps poorly reasoned decision, I decided I ought to update to the newest Tor, as suggested. I uninstalled Vidalia and TorBrowser (unused in my listed configuration).
Upon browsing to the Tor website, I discovered that Vidalia is seemingly no longer available. I dl'd and installed TorBrowser 3.6.3.
Launching TorBrowser seems to work - the https://check.torproject.org/?lang=en_US page tells me "Congratulations. This browser is configured to use Tor."
Launching Bitcoin-Qt (configured for SOCKS proxy on port 9050) seems to no longer work - while the top GUI tells me I am synced by means of a green checkmark, the debug console indicates 0 connections, and the 'Estimated total blocks, is behind what I can see at blockchain.info.
I would like to restore Bitcoin-Qt, and subsequently Armory, to a working configuration atop Tor. I am assuming that the change in Tor is what broke things. How do I restore operation? Is Tor no longer usable for anything but web browsing? That would seem silly. But why no control panel (Vidalia) any longer? Is there a tor.conf or similar that should be used for configuration?
Jump to: