Topic: Connecting to peers - nothing happening :-( (Read 1568 times)
Any news, guys? I have the same problem...
How can I do that if I'm not connecting to any peers? I tried the connection check that one uses when first installing to check node connectivity and it appears I now have none. This is odd as it's the same machine, and the same router.
Reindexing does not require any connections. Often times when people are unable to connect to the network, it is due to something corrupted in the database or in the blockchain data itself that prevents it from getting connections (i.e. disconnected by peers for bad data or something like that). Reindexing usually fixes it. Otherwise deleting the blockchain data lets your node restart completely from scratch.
I can't see how it would need to be set up again. I've got some interesting new errors in the logs too;
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
2017-04-17 13:07:04 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=29
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:12:18 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=30
2017-04-17 13:12:21 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462289, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:55863, peer=31
2017-04-17 13:16:43 ProcessMessages(version, 111 bytes) FAILED peer=32
These errors are usually benign and have nothing to do with your node. 2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
2017-04-17 13:07:04 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=29
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:12:18 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=30
2017-04-17 13:12:21 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462289, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:55863, peer=31
2017-04-17 13:16:43 ProcessMessages(version, 111 bytes) FAILED peer=32
How can I do that if I'm not connecting to any peers? I tried the connection check that one uses when first installing to check node connectivity and it appears I now have none. This is odd as it's the same machine, and the same router. I can't see how it would need to be set up again. I've got some interesting new errors in the logs too;
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
2017-04-17 13:07:04 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=29
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:12:18 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=30
2017-04-17 13:12:21 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462289, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:55863, peer=31
2017-04-17 13:16:43 ProcessMessages(version, 111 bytes) FAILED peer=32
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
2017-04-17 13:07:04 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=29
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 11
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:10:27 GUI: OpenType support missing for script 16
2017-04-17 13:12:18 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=30
2017-04-17 13:12:21 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462289, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:55863, peer=31
2017-04-17 13:16:43 ProcessMessages(version, 111 bytes) FAILED peer=32
You may need to reindex the blockchain, and possibly redownload the whole thing. First try reindexing it by adding -reindex to the startup command for Bitcoin Core.
Incidentally, is it true one can torrent the whole blockchain these days?
No. The torrent is old and will be much slower than just letting Bitcoin Core sync normally.
Here's some new bits, with interesting info;
2017-04-17 12:05:01 receive version message: : version 70001, blocks=469762048, us=127.0.0.1:8333, peer=12
2017-04-17 12:06:26 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=13
2017-04-17 12:11:30 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=14
2017-04-17 12:16:32 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=15
2017-04-17 12:18:03 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462281, us=81.109.35.225:54632, peer=16
2017-04-17 12:21:33 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=17
2017-04-17 12:26:35 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=18
2017-04-17 12:28:40 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462282, us=81.109.35.225:55058, peer=19
2017-04-17 12:30:05 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462282, us=81.109.35.225:55107, peer=20
2017-04-17 12:31:37 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=21
2017-04-17 12:31:38 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 12:36:38 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=22
2017-04-17 12:41:40 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=23
2017-04-17 12:51:59 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=24
2017-04-17 12:51:59 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 12:57:00 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=25
2017-04-17 13:02:03 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=26
2017-04-17 13:02:03 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 13:02:30 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 13:02:36 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462288, us=81.109.35.225:55732, peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
This doesn't look good :-( I'll be researching these error messages while I'm waiting to hear from anyone.
2017-04-17 12:05:01 receive version message: : version 70001, blocks=469762048, us=127.0.0.1:8333, peer=12
2017-04-17 12:06:26 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=13
2017-04-17 12:11:30 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=14
2017-04-17 12:16:32 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=15
2017-04-17 12:18:03 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462281, us=81.109.35.225:54632, peer=16
2017-04-17 12:21:33 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=17
2017-04-17 12:26:35 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=18
2017-04-17 12:28:40 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462282, us=81.109.35.225:55058, peer=19
2017-04-17 12:30:05 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462282, us=81.109.35.225:55107, peer=20
2017-04-17 12:31:37 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=21
2017-04-17 12:31:38 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 12:36:38 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=22
2017-04-17 12:41:40 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=23
2017-04-17 12:51:59 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=24
2017-04-17 12:51:59 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 12:57:00 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=25
2017-04-17 13:02:03 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=26
2017-04-17 13:02:03 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 13:02:30 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-04-17 13:02:36 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462288, us=81.109.35.225:55732, peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
This doesn't look good :-( I'll be researching these error messages while I'm waiting to hear from anyone.
Windows 10, the new version which was updated just the other day, Bitcoin 14, the latest, an old Dell machine, I did have Bitcoin running ok earlier for a couple months, made successful transactions into the wallet which I have backed up, core started giving error messages, became a regular thing, I uninstalled it (it was v12 I think) and installed the latest, now it just says connecting to peers and simply sits there doing nothing. I uninstalled it again and reinstalled it, wondering if things had gone wrong, but it all seems ok except for it aint doing anything :-) Here's the log
2017-04-17 11:42:58 Bitcoin version v0.14.0
2017-04-17 11:42:58 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-04-17 11:42:59 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-04-17 11:42:59 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-04-17 11:43:01 Default data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-17 11:43:01 Using data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-17 11:43:01 Using config file C:\Users\Dell\AppData\Roaming\Bitcoin\bitcoin.conf
2017-04-17 11:43:01 Using at most 125 automatic connections (2048 file descriptors available)
2017-04-17 11:43:01 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-04-17 11:43:01 Using 0 threads for script verification
2017-04-17 11:43:01 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-04-17 11:43:01 Using wallet wallet.dat
2017-04-17 11:43:01 scheduler thread start
2017-04-17 11:43:01 init message: Verifying wallet...
2017-04-17 11:43:01 CDBEnv::Open: LogDir=C:\Users\Dell\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Dell\AppData\Roaming\Bitcoin\db.log
2017-04-17 11:43:01 Bound to [::]:8333
2017-04-17 11:43:01 Bound to 0.0.0.0:8333
2017-04-17 11:43:01 Cache configuration:
2017-04-17 11:43:01 * Using 2.0MiB for block index database
2017-04-17 11:43:01 * Using 8.0MiB for chain state database
2017-04-17 11:43:01 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-04-17 11:43:01 init message: Loading block index...
2017-04-17 11:43:01 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index
2017-04-17 11:43:01 Opened LevelDB successfully
2017-04-17 11:43:01 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-04-17 11:43:01 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate
2017-04-17 11:43:01 Opened LevelDB successfully
2017-04-17 11:43:01 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate: 06cd9bb6457765a9
2017-04-17 11:43:22 LoadBlockIndexDB: last block file = 0
2017-04-17 11:43:22 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=4, size=1102, heights=0...1, time=2009-01-03...2009-01-09)
2017-04-17 11:43:22 Checking all blk files are present...
2017-04-17 11:43:22 LoadBlockIndexDB: transaction index disabled
2017-04-17 11:43:22 LoadBlockIndexDB: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000
2017-04-17 11:43:22 init message: Rewinding blocks...
2017-04-17 11:43:24 init message: Verifying blocks...
2017-04-17 11:43:24 block index 22772ms
2017-04-17 11:43:24 init message: Loading wallet...
2017-04-17 11:43:24 nFileVersion = 140000
2017-04-17 11:43:24 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2017-04-17 11:43:24 wallet 500ms
2017-04-17 11:43:24 setKeyPool.size() = 99
2017-04-17 11:43:24 mapWallet.size() = 3
2017-04-17 11:43:24 mapAddressBook.size() = 2
2017-04-17 11:43:24 mapBlockIndex.size() = 462281
2017-04-17 11:43:24 nBestHeight = 0
2017-04-17 11:43:24 torcontrol thread start
2017-04-17 11:43:24 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2017-04-17 11:43:25 AddLocal([2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333,1)
2017-04-17 11:43:25 Discover: smallformten - 2001:0:4137:9e76:3420:2fda:ae92:dc1e
2017-04-17 11:43:25 init message: Loading addresses...
2017-04-17 11:43:26 Loaded 66722 addresses from peers.dat 989ms
2017-04-17 11:43:26 init message: Loading banlist...
2017-04-17 11:43:26 init message: Starting network threads...
2017-04-17 11:43:26 net thread start
2017-04-17 11:43:26 dnsseed thread start
2017-04-17 11:43:26 addcon thread start
2017-04-17 11:43:26 opencon thread start
2017-04-17 11:43:26 msghand thread start
2017-04-17 11:43:26 init message: Done loading
2017-04-17 11:43:26 GUI: Platform customization: "windows"
2017-04-17 11:43:26 GUI: PaymentServer::LoadRootCAs: Loaded 50 root certificates
2017-04-17 11:43:37 Loading addresses from DNS seeds (could take a while)
2017-04-17 11:43:38 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54149, peer=0
2017-04-17 11:43:38 142 addresses found from DNS seeds
2017-04-17 11:43:38 dnsseed thread exit
2017-04-17 11:44:00 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54156, peer=1
2017-04-17 11:44:06 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462280, us=81.109.35.225:54159, peer=2
2017-04-17 11:44:12 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54161, peer=3
2017-04-17 11:44:18 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=81.109.35.225:54163, peer=4
2017-04-17 11:44:24 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=81.109.35.225:54166, peer=5
2017-04-17 11:44:53 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54176, peer=6
2017-04-17 11:45:10 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54180, peer=7
2017-04-17 11:45:47 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=8
2017-04-17 11:48:14 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=9
2017-04-17 12:01:21 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=10
2017-04-17 12:04:11 receive version message: /Satoshi:0.14.0(UASF-SegWit-BIP148)/: version 70015, blocks=462281, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:54540, peer=11
2017-04-17 12:05:01 receive version message: : version 70001, blocks=469762048, us=127.0.0.1:8333, peer=12
None of which means a great deal to me :-) Is it too soon to worry or should I expect to wait a few hours? I had a look at Windows firewall and it says it's letting the core access both private and public networks so I guess that isn't the problem. Incidentally, is it true one can torrent the whole blockchain these days? Thanks! Let me know if I've missed out anything.
2017-04-17 11:42:58 Bitcoin version v0.14.0
2017-04-17 11:42:58 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-04-17 11:42:59 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-04-17 11:42:59 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-04-17 11:43:01 Default data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-17 11:43:01 Using data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-17 11:43:01 Using config file C:\Users\Dell\AppData\Roaming\Bitcoin\bitcoin.conf
2017-04-17 11:43:01 Using at most 125 automatic connections (2048 file descriptors available)
2017-04-17 11:43:01 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-04-17 11:43:01 Using 0 threads for script verification
2017-04-17 11:43:01 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-04-17 11:43:01 Using wallet wallet.dat
2017-04-17 11:43:01 scheduler thread start
2017-04-17 11:43:01 init message: Verifying wallet...
2017-04-17 11:43:01 CDBEnv::Open: LogDir=C:\Users\Dell\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Dell\AppData\Roaming\Bitcoin\db.log
2017-04-17 11:43:01 Bound to [::]:8333
2017-04-17 11:43:01 Bound to 0.0.0.0:8333
2017-04-17 11:43:01 Cache configuration:
2017-04-17 11:43:01 * Using 2.0MiB for block index database
2017-04-17 11:43:01 * Using 8.0MiB for chain state database
2017-04-17 11:43:01 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-04-17 11:43:01 init message: Loading block index...
2017-04-17 11:43:01 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index
2017-04-17 11:43:01 Opened LevelDB successfully
2017-04-17 11:43:01 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-04-17 11:43:01 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate
2017-04-17 11:43:01 Opened LevelDB successfully
2017-04-17 11:43:01 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate: 06cd9bb6457765a9
2017-04-17 11:43:22 LoadBlockIndexDB: last block file = 0
2017-04-17 11:43:22 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=4, size=1102, heights=0...1, time=2009-01-03...2009-01-09)
2017-04-17 11:43:22 Checking all blk files are present...
2017-04-17 11:43:22 LoadBlockIndexDB: transaction index disabled
2017-04-17 11:43:22 LoadBlockIndexDB: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000
2017-04-17 11:43:22 init message: Rewinding blocks...
2017-04-17 11:43:24 init message: Verifying blocks...
2017-04-17 11:43:24 block index 22772ms
2017-04-17 11:43:24 init message: Loading wallet...
2017-04-17 11:43:24 nFileVersion = 140000
2017-04-17 11:43:24 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2017-04-17 11:43:24 wallet 500ms
2017-04-17 11:43:24 setKeyPool.size() = 99
2017-04-17 11:43:24 mapWallet.size() = 3
2017-04-17 11:43:24 mapAddressBook.size() = 2
2017-04-17 11:43:24 mapBlockIndex.size() = 462281
2017-04-17 11:43:24 nBestHeight = 0
2017-04-17 11:43:24 torcontrol thread start
2017-04-17 11:43:24 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2017-04-17 11:43:25 AddLocal([2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333,1)
2017-04-17 11:43:25 Discover: smallformten - 2001:0:4137:9e76:3420:2fda:ae92:dc1e
2017-04-17 11:43:25 init message: Loading addresses...
2017-04-17 11:43:26 Loaded 66722 addresses from peers.dat 989ms
2017-04-17 11:43:26 init message: Loading banlist...
2017-04-17 11:43:26 init message: Starting network threads...
2017-04-17 11:43:26 net thread start
2017-04-17 11:43:26 dnsseed thread start
2017-04-17 11:43:26 addcon thread start
2017-04-17 11:43:26 opencon thread start
2017-04-17 11:43:26 msghand thread start
2017-04-17 11:43:26 init message: Done loading
2017-04-17 11:43:26 GUI: Platform customization: "windows"
2017-04-17 11:43:26 GUI: PaymentServer::LoadRootCAs: Loaded 50 root certificates
2017-04-17 11:43:37 Loading addresses from DNS seeds (could take a while)
2017-04-17 11:43:38 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54149, peer=0
2017-04-17 11:43:38 142 addresses found from DNS seeds
2017-04-17 11:43:38 dnsseed thread exit
2017-04-17 11:44:00 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54156, peer=1
2017-04-17 11:44:06 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462280, us=81.109.35.225:54159, peer=2
2017-04-17 11:44:12 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54161, peer=3
2017-04-17 11:44:18 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=81.109.35.225:54163, peer=4
2017-04-17 11:44:24 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=81.109.35.225:54166, peer=5
2017-04-17 11:44:53 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54176, peer=6
2017-04-17 11:45:10 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54180, peer=7
2017-04-17 11:45:47 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=8
2017-04-17 11:48:14 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=9
2017-04-17 12:01:21 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=10
2017-04-17 12:04:11 receive version message: /Satoshi:0.14.0(UASF-SegWit-BIP148)/: version 70015, blocks=462281, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:54540, peer=11
2017-04-17 12:05:01 receive version message: : version 70001, blocks=469762048, us=127.0.0.1:8333, peer=12
None of which means a great deal to me :-) Is it too soon to worry or should I expect to wait a few hours? I had a look at Windows firewall and it says it's letting the core access both private and public networks so I guess that isn't the problem. Incidentally, is it true one can torrent the whole blockchain these days? Thanks! Let me know if I've missed out anything.
Jump to: