Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Bitcoin Technical Support
Merits 4 from 2 users
Topic OP
bitcoin core wont connect to mainnet
by
maxeprom
on 27/08/2019, 13:47:04 UTC
⭐ Merited by LoyceV (2) ,bones261 (2)
Hello,
I have installed Bitcoin Core 0.18.1 on my linux box. It has fixed and public IP, and no firewall so port 8333 is ok.
I just ran "bitcoind", starts ok, generates the files at $HOME/.bitcoin, but then complains "socket receive error Connection reset by peer (104)"
forever.
After 24 hours, I got connection with just one node, as it shows netstat and bitcoin-cli getpeerinfo.
Getblockcount is always 0.
 
I've tryied connecting to testnet (bitcoind -testnet), and no problem. After a minute or two,  I got 8 peers, blockchain filesize at .bitcoin/testnet3 increasing, bitcoin-cli returns good info.

But of course, I wan to ran my node on the real net!

What can I do?

Here's some of my debug.log

2019-08-27T04:43:34Z Bitcoin Core version v0.18.1 (release build)
2019-08-27T04:43:34Z Assuming ancestors of block 0000000000000000000f1c54590ee18
d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-08-27T04:43:34Z Setting nMinimumChainWork=000000000000000000000000000000000
0000000051dc8b82f450202ecb3d471
2019-08-27T04:43:34Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-08-27T04:43:34Z Default data directory /home/btc/.bitcoin
2019-08-27T04:43:34Z Using data directory /home/btc/.bitcoin
2019-08-27T04:43:34Z Config file: /home/btc/.bitcoin/bitcoin.conf (not found, sk
ipping)
2019-08-27T04:43:34Z Using at most 125 automatic connections (1024 file descript
ors available)
2019-08-27T04:43:34Z Using 16 MiB out of 32/2 requested for signature cache, abl
e to store 524288 elements
2019-08-27T04:43:34Z Using 16 MiB out of 32/2 requested for script execution cac
he, able to store 524288 elements
2019-08-27T04:43:34Z Using 8 threads for script verification
2019-08-27T04:43:34Z scheduler thread start
2019-08-27T04:43:34Z HTTP: creating work queue of depth 16
2019-08-27T04:43:34Z No rpcpassword set - using random cookie authentication.
2019-08-27T04:43:34Z Generated RPC authentication cookie /home/btc/.bitcoin/.coo
kie
2019-08-27T04:43:34Z HTTP: starting 4 worker threads
2019-08-27T04:43:34Z Using wallet directory /home/btc/.bitcoin/wallets
2019-08-27T04:43:34Z init message: Verifying wallet(s)...
2019-08-27T04:43:34Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 201
0)
2019-08-27T04:43:34Z Using wallet /home/btc/.bitcoin/wallets
2019-08-27T04:43:34Z BerkeleyEnvironment::Open: LogDir=/home/btc/.bitcoin/wallet
s/database ErrorFile=/home/btc/.bitcoin/wallets/db.log
2019-08-27T04:43:34Z init message: Loading banlist...
2019-08-27T04:43:35Z Cache configuration:
2019-08-27T04:43:35Z * Using 2.0 MiB for block index database
2019-08-27T04:43:35Z * Using 8.0 MiB for chain state database
2019-08-27T04:43:35Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1
MiB of unused mempool space)
2019-08-27T04:43:35Z init message: Loading block index...
2019-08-27T04:43:35Z Opening LevelDB in /home/btc/.bitcoin/blocks/index
2019-08-27T04:43:35Z Opened LevelDB successfully
2019-08-27T04:43:35Z Using obfuscation key for /home/btc/.bitcoin/blocks/index:
0000000000000000
2019-08-27T04:43:35Z LoadBlockIndexDB: last block file = 0
2019-08-27T04:43:35Z LoadBlockIndexDB: last block file info: CBlockFileInfo(bloc
ks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2019-08-27T04:43:35Z Checking all blk files are present...
2019-08-27T04:43:35Z Opening LevelDB in /home/btc/.bitcoin/chainstate
2019-08-27T04:43:35Z Opened LevelDB successfully
2019-08-27T04:43:35Z Using obfuscation key for /home/btc/.bitcoin/chainstate: 1a
a07bbe3971b111
2019-08-27T04:43:35Z Loaded best chain: hashBestChain=000000000019d6689c085ae165
831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progre
ss=0.000000
2019-08-27T04:43:35Z init message: Rewinding blocks...
2019-08-27T04:43:35Z init message: Verifying blocks...
2019-08-27T04:43:35Z  block index             363ms
2019-08-27T04:43:35Z init message: Loading wallet...
2019-08-27T04:43:35Z BerkeleyEnvironment::Open: LogDir=/home/btc/.bitcoin/wallet
s/database ErrorFile=/home/btc/.bitcoin/wallets/db.log
2019-08-27T04:43:35Z [default wallet] nFileVersion = 180100
2019-08-27T04:43:35Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/
 metadata, 2001 total. Unknown wallet records: 0
2019-08-27T04:43:35Z [default wallet] Wallet completed loading in             10
1ms
2019-08-27T04:43:35Z [default wallet] setKeyPool.size() = 2000
2019-08-27T04:43:35Z [default wallet] mapWallet.size() = 0
2019-08-27T04:43:35Z [default wallet] mapAddressBook.size() = 0
2019-08-27T04:43:35Z mapBlockIndex.size() = 1
2019-08-27T04:43:35Z nBestHeight = 0
2019-08-27T04:43:35Z torcontrol thread start
2019-08-27T04:43:35Z AddLocal(146.83.56.69:8333,1)
2019-08-27T04:43:35Z Discover: IPv4 eth0: 146.83.56.69
2019-08-27T04:43:35Z Bound to [::]:8333
2019-08-27T04:43:35Z Bound to 0.0.0.0:8333
2019-08-27T04:43:35Z init message: Loading P2P addresses...
2019-08-27T04:43:35Z Loaded 282 addresses from peers.dat  35ms
2019-08-27T04:43:35Z init message: Starting network threads...
2019-08-27T04:43:35Z net thread start
2019-08-27T04:43:35Z opencon thread start
2019-08-27T04:43:35Z addcon thread start
2019-08-27T04:43:35Z dnsseed thread start
2019-08-27T04:43:35Z init message: Done loading
2019-08-27T04:43:35Z msghand thread start
2019-08-27T04:43:35Z Imported mempool transactions from disk: 0 succeeded, 0 fai
led, 0 expired, 0 already there
2019-08-27T04:43:36Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:37Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:38Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:38Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:39Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:40Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:40Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:41Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:42Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:43Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:46Z Loading addresses from DNS seeds (could take a while)
2019-08-27T04:43:50Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:50Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:50Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:51Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:52Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:52Z 294 addresses found from DNS seeds
2019-08-27T04:43:52Z dnsseed thread exit
2019-08-27T04:43:53Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:53Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:54Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:54Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:55Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:56Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:57Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:58Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:58Z socket recv error Connection reset by peer (104)
2019-08-27T04:43:59Z socket recv error Connection reset by peer (104)
2019-08-27T04:44:00Z socket recv error Connection reset by peer (104)
2019-08-27T04:44:00Z socket recv error Connection reset by peer (104)
2019-08-27T04:44:01Z socket recv error Connection reset by peer (104)
2019-08-27T04:44:02Z socket recv error Connection reset by peer (104)

......   and so on forever