Outgoing P2P connections are reset immediately #17247

issue GiveMeSunShine opened this issue on October 25, 2019

GiveMeSunShine commented at 10:08 AM on October 25, 2019: none

2019-10-25T09:39:28Z Bitcoin Core version v0.17.0.1 (release build)
2019-10-25T09:39:28Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-10-25T09:39:28Z Assuming ancestors of block 0000000000000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8 have valid signatu
res.
2019-10-25T09:39:28Z Setting nMinimumChainWork=0000000000000000000000000000000000000000028822fef1c230963535a90d
2019-10-25T09:39:28Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2019-10-25T09:39:28Z Using RdRand as an additional entropy source
2019-10-25T09:39:28Z Default data directory /home/mpsp/.bitcoin
2019-10-25T09:39:28Z Using data directory /data/project/online_project/node/bitcoin_test/bitcoin
2019-10-25T09:39:28Z Using config file /data/project/online_project/node/bitcoin_test/bitcoin/bitcoin.conf
2019-10-25T09:39:28Z Using at most 125 automatic connections (1024 file descriptors available)
2019-10-25T09:39:28Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-10-25T09:39:28Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-10-25T09:39:28Z Using 16 threads for script verification
2019-10-25T09:39:28Z scheduler thread start
2019-10-25T09:39:28Z Allowing HTTP connections from: 127.0.0.0/8 ::1/128 0.0.0.0/0 
2019-10-25T09:39:28Z Binding RPC on address 10.8.64.178 port 8232
2019-10-25T09:39:28Z Initialized HTTP server
2019-10-25T09:39:28Z HTTP: creating work queue of depth 128
2019-10-25T09:39:28Z Starting RPC
2019-10-25T09:39:28Z Starting HTTP RPC server
2019-10-25T09:39:28Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use
 cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2019-10-25T09:39:28Z Registering HTTP handler for / (exactmatch 1)
2019-10-25T09:39:28Z Registering HTTP handler for /wallet/ (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/tx/ (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/block/notxdetails/ (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/block/ (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/chaininfo (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/mempool/info (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/mempool/contents (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/headers/ (exactmatch 0)
2019-10-25T09:39:28Z Registering HTTP handler for /rest/getutxos (exactmatch 0)
2019-10-25T09:39:28Z Starting HTTP server
2019-10-25T09:39:28Z HTTP: starting 100 worker threads
2019-10-25T09:39:28Z Entering http event loop
2019-10-25T09:39:28Z Using wallet directory /data/project/online_project/node/bitcoin_test/bitcoin
2019-10-25T09:39:28Z init message: Verifying wallet(s)...
2019-10-25T09:39:28Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-10-25T09:39:28Z Using wallet wallet.dat
2019-10-25T09:39:28Z BerkeleyEnvironment::Open: LogDir=/data/project/online_project/node/bitcoin_test/bitcoin/database ErrorFile=/da
ta/project/online_project/node/bitcoin_test/bitcoin/db.log
2019-10-25T09:39:28Z net: setting try another outbound peer=false
2019-10-25T09:39:28Z Cache configuration:
2019-10-25T09:39:28Z * Using 2.0MiB for block index database
2019-10-25T09:39:28Z * Using 56.0MiB for transaction index database
2019-10-25T09:39:28Z * Using 8.0MiB for chain state database
2019-10-25T09:39:28Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-10-25T09:39:28Z init message: Loading block index...
2019-10-25T09:39:28Z LevelDB using max_open_files=1000 (default=1000)
2019-10-25T09:39:28Z Opening LevelDB in /data/project/online_project/node/bitcoin_test/bitcoin/blocks/index
2019-10-25T09:39:28Z leveldb: Delete type=3 [#1](/bitcoin-bitcoin/1/)
2019-10-25T09:39:28Z Opened LevelDB successfully
2019-10-25T09:39:28Z Using obfuscation key for /data/project/online_project/node/bitcoin_test/bitcoin/blocks/index: 0000000000000000
2019-10-25T09:39:28Z LoadBlockIndexDB: last block file = 0
2019-10-25T09:39:28Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-
01-01)
2019-10-25T09:39:28Z Checking all blk files are present...
2019-10-25T09:39:28Z Initializing databases...
2019-10-25T09:39:28Z Pre-allocating up to position 0x1000000 in blk00000.dat
2019-10-25T09:39:28Z LevelDB using max_open_files=1000 (default=1000)
2019-10-25T09:39:28Z Opening LevelDB in /data/project/online_project/node/bitcoin_test/bitcoin/chainstate
2019-10-25T09:39:28Z leveldb: Delete type=3 [#1](/bitcoin-bitcoin/1/)
2019-10-25T09:39:28Z Opened LevelDB successfully
2019-10-25T09:39:28Z WriteBatch memory usage: db=chainstate, before=0.0MiB, after=0.0MiB
2019-10-25T09:39:28Z Wrote new obfuscate key for /data/project/online_project/node/bitcoin_test/bitcoin/chainstate: 28879900dc24e41c
2019-10-25T09:39:28Z Using obfuscation key for /data/project/online_project/node/bitcoin_test/bitcoin/chainstate: 28879900dc24e41c
2019-10-25T09:39:28Z init message: Rewinding blocks...
2019-10-25T09:39:28Z  block index               3ms
2019-10-25T09:39:28Z LevelDB using max_open_files=1000 (default=1000)
2019-10-25T09:39:28Z Opening LevelDB in /data/project/online_project/node/bitcoin_test/bitcoin/indexes/txindex
2019-10-25T09:39:28Z leveldb: Delete type=3 [#1](/bitcoin-bitcoin/1/)
2019-10-25T09:39:28Z Opened LevelDB successfully
2019-10-25T09:39:28Z Using obfuscation key for /data/project/online_project/node/bitcoin_test/bitcoin/indexes/txindex: 0000000000000
000
2019-10-25T09:39:28Z init message: Loading wallet...
2019-10-25T09:39:28Z txindex thread start
2019-10-25T09:39:28Z txindex is enabled
2019-10-25T09:39:28Z txindex thread exit
2019-10-25T09:39:28Z [default wallet] nFileVersion = 170001
2019-10-25T09:39:28Z [default wallet] Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total. Unknown wallet records: 0
2019-10-25T09:39:28Z [default wallet] Performing wallet upgrade to 169900
2019-10-25T09:39:29Z [default wallet] keypool added 2000 keys (1000 internal), size=2000 (1000 internal)
2019-10-25T09:39:29Z [default wallet] Wallet completed loading in            1103ms
2019-10-25T09:39:29Z [default wallet] setKeyPool.size() = 2000
2019-10-25T09:39:29Z [default wallet] mapWallet.size() = 0
2019-10-25T09:39:29Z [default wallet] mapAddressBook.size() = 0
2019-10-25T09:39:29Z   - Load block from disk: 0.11ms [0.00s]
2019-10-25T09:39:29Z   - Connect total: 0.06ms [0.00s (infms/blk)]
2019-10-25T09:39:29Z   - Flush: 0.01ms [0.00s (infms/blk)]
2019-10-25T09:39:29Z   - Writing chainstate: 0.01ms [0.00s (infms/blk)]
2019-10-25T09:39:29Z UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x0000000
1 log2_work=32.000022 tx=1 date='2009-01-03T18:15:05Z' progress=0.000000 cache=0.0MiB(0txo)
2019-10-25T09:39:29Z   - Connect postprocess: 5.37ms [0.01s (infms/blk)]
2019-10-25T09:39:29Z - Connect block: 5.57ms [0.01s (infms/blk)]
2019-10-25T09:39:29Z mapBlockIndex.size() = 1
2019-10-25T09:39:29Z Failed to open mempool file from disk. Continuing anyway.
2019-10-25T09:39:29Z nBestHeight = 0
2019-10-25T09:39:29Z torcontrol thread start
2019-10-25T09:39:29Z WriteBatch memory usage: db=txindex, before=0.0MiB, after=0.0MiB
2019-10-25T09:39:29Z tor: Error connecting to Tor control socket
2019-10-25T09:39:29Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:29Z Bound to [::]:8233
2019-10-25T09:39:29Z Bound to 0.0.0.0:8233
2019-10-25T09:39:29Z init message: Loading P2P addresses...
2019-10-25T09:39:29Z ERROR: DeserializeFileDB: Failed to open file /data/project/online_project/node/bitcoin_test/bitcoin/peers.dat
2019-10-25T09:39:29Z Invalid or missing peers.dat; recreating
2019-10-25T09:39:29Z Flushed 0 addresses to peers.dat  0ms
2019-10-25T09:39:29Z init message: Loading banlist...
2019-10-25T09:39:29Z ERROR: DeserializeFileDB: Failed to open file /data/project/online_project/node/bitcoin_test/bitcoin/banlist.da
t
2019-10-25T09:39:29Z Invalid or missing banlist.dat; recreating
2019-10-25T09:39:29Z Flushed 0 banned node ips/subnets to banlist.dat  1ms
2019-10-25T09:39:29Z init message: Starting network threads...
2019-10-25T09:39:29Z net thread start
2019-10-25T09:39:29Z dnsseed thread start
2019-10-25T09:39:29Z Loading addresses from DNS seeds (could take a while)
2019-10-25T09:39:29Z init message: Done loading
2019-10-25T09:39:29Z addcon thread start
2019-10-25T09:39:29Z opencon thread start
2019-10-25T09:39:29Z msghand thread start
2019-10-25T09:39:29Z Added 40 addresses from sxa35bqgjufzajdt.internal: 0 tried, 39 new
2019-10-25T09:39:29Z Added 33 addresses from 3ruqazlhqrx4izs4.internal: 0 tried, 72 new
2019-10-25T09:39:29Z Added 34 addresses from fc46cby4cw6bvgfz.internal: 0 tried, 106 new
2019-10-25T09:39:29Z Added 40 addresses from nzcecuuaj4fa5dcl.internal: 0 tried, 146 new
2019-10-25T09:39:30Z trying connection [2a01:4f8:1c17:7e2a::1]:8333 lastseen=75.2hrs
2019-10-25T09:39:30Z connect() to [2a01:4f8:1c17:7e2a::1]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:30Z tor: Error connecting to Tor control socket
2019-10-25T09:39:30Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:30Z trying connection 174.138.51.147:8333 lastseen=152.4hrs
2019-10-25T09:39:31Z Added connection peer=0
2019-10-25T09:39:31Z sending version (104 bytes) peer=0
2019-10-25T09:39:31Z send version message: version 70015, blocks=0, us=[::]:0, peer=0
2019-10-25T09:39:31Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:31Z disconnecting peer=0
2019-10-25T09:39:31Z Cleared nodestate for peer=0
2019-10-25T09:39:31Z Added 37 addresses from epu7hertnka6c2px.internal: 0 tried, 183 new
2019-10-25T09:39:31Z trying connection [2001:760:2c0c:202:f4bb:ff:fe80:2b42]:8333 lastseen=81.1hrs
2019-10-25T09:39:31Z connect() to [2001:760:2c0c:202:f4bb:ff:fe80:2b42]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:31Z Added 23 addresses from mr3yswg4s4rrqkm4.internal: 0 tried, 206 new
2019-10-25T09:39:32Z trying connection 90.187.18.209:8333 lastseen=145.3hrs
2019-10-25T09:39:32Z Flushing wallet.dat
2019-10-25T09:39:32Z tor: Error connecting to Tor control socket
2019-10-25T09:39:32Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:32Z Flushed wallet.dat 2ms
2019-10-25T09:39:32Z Added connection peer=1
2019-10-25T09:39:32Z sending version (104 bytes) peer=1
2019-10-25T09:39:32Z send version message: version 70015, blocks=0, us=[::]:0, peer=1
2019-10-25T09:39:32Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:32Z disconnecting peer=1
2019-10-25T09:39:32Z Cleared nodestate for peer=1
2019-10-25T09:39:32Z trying connection 13.250.32.177:8333 lastseen=74.9hrs
2019-10-25T09:39:33Z Added connection peer=2
2019-10-25T09:39:33Z sending version (104 bytes) peer=2
2019-10-25T09:39:33Z send version message: version 70015, blocks=0, us=[::]:0, peer=2
2019-10-25T09:39:33Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:33Z disconnecting peer=2
2019-10-25T09:39:33Z Cleared nodestate for peer=2
2019-10-25T09:39:33Z Added 34 addresses from 7v4ngmag7nmkcv4l.internal: 0 tried, 240 new
2019-10-25T09:39:33Z 245 addresses found from DNS seeds
2019-10-25T09:39:33Z dnsseed thread exit
2019-10-25T09:39:33Z trying connection 13.229.152.67:8333 lastseen=125.0hrs
2019-10-25T09:39:33Z Added connection peer=3
2019-10-25T09:39:33Z sending version (104 bytes) peer=3
2019-10-25T09:39:33Z send version message: version 70015, blocks=0, us=[::]:0, peer=3
**2019-10-25T09:39:33Z socket recv error Connection reset by peer (104)**
2019-10-25T09:39:33Z disconnecting peer=3
2019-10-25T09:39:33Z Cleared nodestate for peer=3
2019-10-25T09:39:34Z trying connection 116.62.64.237:8333 lastseen=109.1hrs
2019-10-25T09:39:34Z Added connection peer=4
2019-10-25T09:39:34Z sending version (104 bytes) peer=4
2019-10-25T09:39:34Z send version message: version 70015, blocks=0, us=[::]:0, peer=4
**2019-10-25T09:39:34Z socket recv error Connection reset by peer (104)**
2019-10-25T09:39:34Z disconnecting peer=4
2019-10-25T09:39:34Z Cleared nodestate for peer=4
2019-10-25T09:39:34Z tor: Error connecting to Tor control socket
2019-10-25T09:39:34Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:34Z trying connection 5.196.65.205:8333 lastseen=136.8hrs
2019-10-25T09:39:34Z Added connection peer=5
2019-10-25T09:39:34Z sending version (104 bytes) peer=5
2019-10-25T09:39:34Z send version message: version 70015, blocks=0, us=[::]:0, peer=5
2019-10-25T09:39:34Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:34Z disconnecting peer=5
2019-10-25T09:39:34Z Cleared nodestate for peer=5
2019-10-25T09:39:35Z trying connection 52.197.62.118:8333 lastseen=116.4hrs
2019-10-25T09:39:35Z Added connection peer=6
2019-10-25T09:39:35Z sending version (104 bytes) peer=6
2019-10-25T09:39:35Z send version message: version 70015, blocks=0, us=[::]:0, peer=6
2019-10-25T09:39:35Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:35Z disconnecting peer=6
2019-10-25T09:39:35Z Cleared nodestate for peer=6
2019-10-25T09:39:35Z trying connection 45.45.30.90:8333 lastseen=138.0hrs
2019-10-25T09:39:36Z Added connection peer=7
2019-10-25T09:39:36Z sending version (104 bytes) peer=7
2019-10-25T09:39:36Z send version message: version 70015, blocks=0, us=[::]:0, peer=7
2019-10-25T09:39:36Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:36Z disconnecting peer=7
2019-10-25T09:39:36Z Cleared nodestate for peer=7
2019-10-25T09:39:36Z trying connection 75.136.216.43:8333 lastseen=140.0hrs
2019-10-25T09:39:36Z Added connection peer=8
2019-10-25T09:39:36Z sending version (104 bytes) peer=8
2019-10-25T09:39:36Z send version message: version 70015, blocks=0, us=[::]:0, peer=8
2019-10-25T09:39:36Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:36Z disconnecting peer=8
2019-10-25T09:39:36Z Cleared nodestate for peer=8
2019-10-25T09:39:37Z trying connection [2a01:4f8:c2c:1b21::1]:8333 lastseen=143.3hrs
2019-10-25T09:39:37Z connect() to [2a01:4f8:c2c:1b21::1]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:37Z tor: Error connecting to Tor control socket
2019-10-25T09:39:37Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:37Z trying connection 18.136.51.188:8333 lastseen=138.7hrs
2019-10-25T09:39:38Z Added connection peer=9
2019-10-25T09:39:38Z sending version (104 bytes) peer=9
2019-10-25T09:39:38Z send version message: version 70015, blocks=0, us=[::]:0, peer=9
2019-10-25T09:39:38Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:38Z disconnecting peer=9
2019-10-25T09:39:38Z Cleared nodestate for peer=9
2019-10-25T09:39:38Z trying connection 60.191.106.148:8333 lastseen=99.3hrs
2019-10-25T09:39:38Z Added connection peer=10
2019-10-25T09:39:38Z sending version (104 bytes) peer=10
2019-10-25T09:39:38Z send version message: version 70015, blocks=0, us=[::]:0, peer=10
2019-10-25T09:39:38Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:38Z disconnecting peer=10
2019-10-25T09:39:38Z Cleared nodestate for peer=10
2019-10-25T09:39:39Z trying connection 31.43.140.190:8333 lastseen=111.4hrs
2019-10-25T09:39:39Z Added connection peer=11
2019-10-25T09:39:39Z sending version (104 bytes) peer=11
2019-10-25T09:39:39Z send version message: version 70015, blocks=0, us=[::]:0, peer=11
2019-10-25T09:39:39Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:39Z disconnecting peer=11
2019-10-25T09:39:39Z Cleared nodestate for peer=11
2019-10-25T09:39:39Z trying connection [2a01:4f8:c010:2f11::1]:8333 lastseen=138.8hrs
2019-10-25T09:39:39Z connect() to [2a01:4f8:c010:2f11::1]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:40Z trying connection [2001:67c:22fc:1337::5]:8333 lastseen=102.4hrs
2019-10-25T09:39:40Z connect() to [2001:67c:22fc:1337::5]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:40Z trying connection [2001:0:9d38:6ab8:141b:2d1:b83d:5257]:8333 lastseen=162.3hrs
2019-10-25T09:39:40Z connect() to [2001:0:9d38:6ab8:141b:2d1:b83d:5257]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:41Z trying connection [2001:0:4137:9e76:30c6:355c:b954:92d9]:8333 lastseen=142.0hrs
2019-10-25T09:39:41Z connect() to [2001:0:4137:9e76:30c6:355c:b954:92d9]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:41Z trying connection 173.212.220.9:8333 lastseen=131.6hrs
2019-10-25T09:39:42Z Added connection peer=12
2019-10-25T09:39:42Z sending version (104 bytes) peer=12
2019-10-25T09:39:42Z send version message: version 70015, blocks=0, us=[::]:0, peer=12
2019-10-25T09:39:42Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:42Z disconnecting peer=12
2019-10-25T09:39:42Z Cleared nodestate for peer=12
2019-10-25T09:39:42Z trying connection 145.239.133.16:8333 lastseen=141.8hrs
2019-10-25T09:39:43Z tor: Error connecting to Tor control socket
2019-10-25T09:39:43Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:43Z Added connection peer=13
2019-10-25T09:39:43Z sending version (104 bytes) peer=13
2019-10-25T09:39:43Z send version message: version 70015, blocks=0, us=[::]:0, peer=13
2019-10-25T09:39:43Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:43Z disconnecting peer=13
2019-10-25T09:39:43Z Cleared nodestate for peer=13
2019-10-25T09:39:44Z trying connection 195.242.93.189:8333 lastseen=133.7hrs
2019-10-25T09:39:44Z Added connection peer=14
2019-10-25T09:39:44Z sending version (104 bytes) peer=14
2019-10-25T09:39:44Z send version message: version 70015, blocks=0, us=[::]:0, peer=14
2019-10-25T09:39:44Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:44Z disconnecting peer=14
2019-10-25T09:39:44Z Cleared nodestate for peer=14
2019-10-25T09:39:45Z trying connection [2001:0:5ef5:79fb:1090:2e42:b3bc:41c8]:8333 lastseen=145.1hrs
2019-10-25T09:39:45Z connect() to [2001:0:5ef5:79fb:1090:2e42:b3bc:41c8]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:45Z trying connection [2a01:4f8:c2c:27fc::1]:8333 lastseen=106.5hrs
2019-10-25T09:39:45Z connect() to [2a01:4f8:c2c:27fc::1]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:46Z trying connection [2a01:cb00:7cd:b000:fa1f:bd1:fe0:62a6]:8333 lastseen=88.2hrs
2019-10-25T09:39:46Z connect() to [2a01:cb00:7cd:b000:fa1f:bd1:fe0:62a6]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:46Z trying connection 3.1.203.33:8333 lastseen=133.5hrs
2019-10-25T09:39:46Z Added connection peer=15
2019-10-25T09:39:46Z sending version (104 bytes) peer=15
2019-10-25T09:39:46Z send version message: version 70015, blocks=0, us=[::]:0, peer=15
2019-10-25T09:39:46Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:46Z disconnecting peer=15
2019-10-25T09:39:46Z Cleared nodestate for peer=15
2019-10-25T09:39:47Z trying connection [2a00:d2a0:a:3d00:405:3f71:b2e:34f9]:8333 lastseen=109.3hrs
2019-10-25T09:39:47Z connect() to [2a00:d2a0:a:3d00:405:3f71:b2e:34f9]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:47Z trying connection 94.242.187.147:8333 lastseen=152.1hrs
2019-10-25T09:39:50Z tor: Error connecting to Tor control socket
2019-10-25T09:39:50Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2019-10-25T09:39:52Z connection to 94.242.187.147:8333 timeout
2019-10-25T09:39:53Z trying connection 167.86.105.128:8333 lastseen=77.1hrs
2019-10-25T09:39:53Z Added connection peer=16
2019-10-25T09:39:53Z sending version (104 bytes) peer=16
2019-10-25T09:39:53Z send version message: version 70015, blocks=0, us=[::]:0, peer=16
2019-10-25T09:39:53Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:53Z disconnecting peer=16
2019-10-25T09:39:53Z Cleared nodestate for peer=16
2019-10-25T09:39:54Z trying connection 217.160.185.97:8333 lastseen=126.7hrs
2019-10-25T09:39:54Z Added connection peer=17
2019-10-25T09:39:54Z sending version (104 bytes) peer=17
2019-10-25T09:39:54Z send version message: version 70015, blocks=0, us=[::]:0, peer=17
2019-10-25T09:39:54Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:54Z disconnecting peer=17
2019-10-25T09:39:54Z Cleared nodestate for peer=17
2019-10-25T09:39:54Z trying connection 62.210.124.142:8333 lastseen=75.1hrs
2019-10-25T09:39:54Z Added connection peer=18
2019-10-25T09:39:54Z sending version (104 bytes) peer=18
2019-10-25T09:39:54Z send version message: version 70015, blocks=0, us=[::]:0, peer=18
2019-10-25T09:39:55Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:55Z disconnecting peer=18
2019-10-25T09:39:55Z Cleared nodestate for peer=18
2019-10-25T09:39:55Z trying connection [2001:470:6c80:101::1]:8333 lastseen=73.1hrs
2019-10-25T09:39:55Z connect() to [2001:470:6c80:101::1]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:56Z trying connection 18.138.255.8:8333 lastseen=163.6hrs
2019-10-25T09:39:56Z Added connection peer=19
2019-10-25T09:39:56Z sending version (104 bytes) peer=19
2019-10-25T09:39:56Z send version message: version 70015, blocks=0, us=[::]:0, peer=19
2019-10-25T09:39:56Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:56Z disconnecting peer=19
2019-10-25T09:39:56Z Cleared nodestate for peer=19
2019-10-25T09:39:56Z trying connection 31.179.204.142:8333 lastseen=145.7hrs
2019-10-25T09:39:56Z Added connection peer=20
2019-10-25T09:39:56Z sending version (104 bytes) peer=20
2019-10-25T09:39:56Z send version message: version 70015, blocks=0, us=[::]:0, peer=20
2019-10-25T09:39:56Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:56Z disconnecting peer=20
2019-10-25T09:39:56Z Cleared nodestate for peer=20
2019-10-25T09:39:57Z trying connection 139.180.161.239:8333 lastseen=119.7hrs
2019-10-25T09:39:57Z Added connection peer=21
2019-10-25T09:39:57Z sending version (104 bytes) peer=21
2019-10-25T09:39:57Z send version message: version 70015, blocks=0, us=[::]:0, peer=21
2019-10-25T09:39:57Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:57Z disconnecting peer=21
2019-10-25T09:39:57Z Cleared nodestate for peer=21
2019-10-25T09:39:58Z trying connection 62.212.83.41:8333 lastseen=90.7hrs
2019-10-25T09:39:58Z Added connection peer=22
2019-10-25T09:39:58Z sending version (104 bytes) peer=22
2019-10-25T09:39:58Z send version message: version 70015, blocks=0, us=[::]:0, peer=22
2019-10-25T09:39:58Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:58Z disconnecting peer=22
2019-10-25T09:39:58Z Cleared nodestate for peer=22
2019-10-25T09:39:58Z trying connection [2a01:4f8:191:418f::2]:8333 lastseen=85.5hrs
2019-10-25T09:39:58Z connect() to [2a01:4f8:191:418f::2]:8333 failed: Network is unreachable (101)
2019-10-25T09:39:59Z trying connection 167.99.224.63:8333 lastseen=149.8hrs
2019-10-25T09:39:59Z Added connection peer=23
2019-10-25T09:39:59Z sending version (104 bytes) peer=23
2019-10-25T09:39:59Z send version message: version 70015, blocks=0, us=[::]:0, peer=23
2019-10-25T09:39:59Z socket recv error Connection reset by peer (104)
2019-10-25T09:39:59Z disconnecting peer=23

When my node starts, it always wraps “socket recv error Connection reset by peer (104)” error，does not synchronize blocks，Why？

GiveMeSunShine added the label Bug on Oct 25, 2019
laanwj renamed this:
~~socket recv error Connection reset by peer (104)~~
Outgoing P2P connections are reset immediately
on Oct 25, 2019
laanwj added the label P2P on Oct 25, 2019
laanwj removed the label Bug on Oct 25, 2019
laanwj added the label Questions and Help on Oct 25, 2019
laanwj commented at 10:25 AM on October 25, 2019: member

This is really strange; it looks like your firewall or ISP is actively closing bitcoin P2P connections.
laanwj commented at 12:13 PM on October 25, 2019: member

~~Can you try with -logips command line option enabled (or logips=1 in bitcoin.conf) and send the resulting log? This would allow to see what peer(s) it's failing on.~~

Unnecessary, I noticed later that the IPs are in the log, just before the connection attempt.
MarcoFalke commented at 1:31 PM on October 25, 2019: member

Are you running this in a corporate or university network?

Sjors commented at 5:38 PM on October 25, 2019: member

I'm seeing tons of these messages too on mainnet and testnet. Here's a few from testnet:

2019-10-25T17:23:59Z Added connection to 59.83.201.121:7603 peer=168
2019-10-25T17:23:59Z connection from 59.83.201.121:7603 accepted
...
2019-10-25T17:24:10Z socket recv error Connection reset by peer (104)
2019-10-25T17:24:10Z disconnecting peer=168
2019-10-25T17:24:10Z Cleared nodestate for peer=168
...
2019-10-25T17:31:01Z Added connection to 113.78.64.65:56551 peer=380
2019-10-25T17:31:01Z connection from 113.78.64.65:56551 accepted
...
2019-10-25T17:31:12Z socket recv error Connection reset by peer (104)
2019-10-25T17:31:12Z disconnecting peer=380
2019-10-25T17:31:12Z Cleared nodestate for peer=380
...
2019-10-25T17:32:35Z Added connection to 117.94.64.209:52103 peer=429
2019-10-25T17:32:35Z connection from 117.94.64.209:52103 accepted
2019-10-25T17:32:35Z received: version (102 bytes) peer=429
2019-10-25T17:32:35Z sending version (103 bytes) peer=429
2019-10-25T17:32:35Z send version message: version 70015, blocks=1583984, us=[::]:0, them=117.94.64.209:52103, peer=429
2019-10-25T17:32:35Z sending verack (0 bytes) peer=429
2019-10-25T17:32:35Z receive version message: /Satoshi:0.17.1/: version 70013, blocks=0, us=84.105.61.15:18333, peer=429, peeraddr=117.94.64.209:52103
2019-10-25T17:32:35Z received: verack (0 bytes) peer=429
2019-10-25T17:32:35Z sending sendheaders (0 bytes) peer=429
2019-10-25T17:32:35Z sending ping (8 bytes) peer=429
2019-10-25T17:32:35Z AdvertiseLocal: advertising addres
2019-10-25T17:32:35Z sending addr (31 bytes) peer=429
2019-10-25T17:32:35Z sending feefilter (8 bytes) peer=429
2019-10-25T17:34:15Z socket recv error Connection reset by peer (104)
2019-10-25T17:34:15Z disconnecting peer=429

Most of them are not very chatty. I tried reconnecting from another node, but they disappear very quickly.

Though maybe I'm seeing something different, because in your case the nodes are all on port 8333.

TheBlueMatt commented at 5:45 PM on October 25, 2019: member

@sjors What you're seeing i just an uptick in reset connections, not an uptick in outgoing resets. The fact that we log "Connection reset by peer" so aggressively really needs to stop.
MarcoFalke commented at 5:50 PM on October 25, 2019: member

@Sjors You got at least a verack back, while this is still sketchy. It seems unrelated to this issue.
TheBlueMatt commented at 6:02 PM on October 25, 2019: member

@GiveMeSunShine how long did you wait for it to connect? The printing of RSTs (which can happen when you just connect to a server that is no longer running bitcoind) is not strange, and a bug itself, but it looks like your node was only trying to connect for under a minute?
laanwj commented at 8:40 AM on October 26, 2019: member
@Sjors It's not strange to have some of these messages in your log. Network issues always happen, chatty logs are not a major problem.

The problem here is that the OP doesn't get outgoing connections at all and it doesn't sync. I assumed that's because of the immediate resets.

These are definitely outgoing connections that are reset; it's the same every time, a version message is sent and the peer disconnects:
```
2019-10-25T09:39:33Z trying connection 13.229.152.67:8333 lastseen=125.0hrs
2019-10-25T09:39:33Z Added connection peer=3
2019-10-25T09:39:33Z sending version (104 bytes) peer=3
2019-10-25T09:39:33Z send version message: version 70015, blocks=0, us=[::]:0, peer=3
**2019-10-25T09:39:33Z socket recv error Connection reset by peer (104)**
2019-10-25T09:39:33Z disconnecting peer=3
```
GiveMeSunShine commented at 1:09 AM on October 28, 2019: none

@MarcoFalke running this in a corporate network。
GiveMeSunShine commented at 1:37 AM on October 28, 2019: none

@TheBlueMatt @MarcoFalke I started a main network node that has already synchronized the height of the 595258 block in a corporate network. Start the command by ./bitcoind2 -daemon -txindex -debug=1 -rest -server -datadir=/data/project/online_project/node/bitcoin_node/bitcoin/ -port=8133 -rpcport=8132 -rpcuser=tom -rpcpassword=tom -rpcthreads=100 -rpcworkqueue=128 -rpcbind=0.0.0.0 -rpcallowip=0.0.0.0/0 When I restart the node, the node cannot connect to other nodes on the main network, and can find the relevant chain info through url curl GET "http://*.*.*.*:8132/rest/chaininfo.json"， The message is： {"chain":"main","blocks":595258,"headers":595258,"bestblockhash":"0000000000000000001200dc3c2a781a5d2bad39b666e00ed51e3b2b014ca229","difficulty":11890594958795.76,"mediantime":1568700852,"verificationprogress":0.9818047790541046,"initialblockdownload":true,"chainwork":"0000000000000000000000000000000000000000088ea60dbdabab7899badcc8","size_on_disk":272798646834,"pruned":false,"softforks":[{"id":"bip34","version":2,"reject":{"status":true}},{"id":"bip66","version":3,"reject":{"status":true}},{"id":"bip65","version":4,"reject":{"status":true}}],"bip9_softforks":{"csv":{"status":"active","startTime":1462060800,"timeout":1493596800,"since":419328},"segwit":{"status":"active","startTime":1479168000,"timeout":1510704000,"since":481824}},"warnings":""} The node always reports socket recv error Connection reset by peer (104) error messages and does not synchronize blocks
MarcoFalke commented at 5:19 PM on April 26, 2020: member

@GiveMeSunShine What hardware are you running on?
MarcoFalke added the label Waiting for author on Apr 26, 2020
MarcoFalke closed this on Apr 27, 2020

adu-web3 commented at 3:19 AM on March 8, 2021: none

I have met with the exactly same problems as yours

2021-03-08T03:13:40Z trying connection [2a03:b0c0:3:d0::f00:d001]:8333 lastseen=107.5hrs
2021-03-08T03:13:40Z connect() to [2a03:b0c0:3:d0::f00:d001]:8333 failed: Network is unreachable (101)
2021-03-08T03:13:40Z trying connection 77.134.172.81:8333 lastseen=101.8hrs
2021-03-08T03:13:40Z Added connection peer=13
2021-03-08T03:13:40Z sending version (102 bytes) peer=13
2021-03-08T03:13:40Z send version message: version 70016, blocks=0, us=[::]:0, peer=13
2021-03-08T03:13:40Z socket recv error for peer=13: Connection reset by peer (104)
2021-03-08T03:13:40Z disconnecting peer=13
2021-03-08T03:13:40Z Cleared nodestate for peer=13
2021-03-08T03:13:41Z trying connection 213.148.199.23:8333 lastseen=184.4hrs
2021-03-08T03:13:41Z Added connection peer=14
2021-03-08T03:13:41Z sending version (102 bytes) peer=14
2021-03-08T03:13:41Z send version message: version 70016, blocks=0, us=[::]:0, peer=14
2021-03-08T03:13:41Z socket recv error for peer=14: Connection reset by peer (104)
2021-03-08T03:13:41Z disconnecting peer=14
2021-03-08T03:13:41Z Cleared nodestate for peer=14
2021-03-08T03:13:42Z trying connection [240e:38a:85b5:8600:b403:ed05:b2aa:f01f]:8333 lastseen=145.6hrs
2021-03-08T03:13:42Z connect() to [240e:38a:85b5:8600:b403:ed05:b2aa:f01f]:8333 failed: Network is unreachable (101)
2021-03-08T03:13:42Z trying connection 185.209.70.17:8333 lastseen=120.5hrs
2021-03-08T03:13:42Z Added connection peer=15
2021-03-08T03:13:42Z sending version (102 bytes) peer=15
2021-03-08T03:13:42Z send version message: version 70016, blocks=0, us=[::]:0, peer=15
2021-03-08T03:13:42Z socket recv error for peer=15: Connection reset by peer (104)
2021-03-08T03:13:42Z disconnecting peer=15
2021-03-08T03:13:42Z Cleared nodestate for peer=15
2021-03-08T03:13:43Z trying connection [2001:0:4137:9e76:34bb:2f1f:a952:3394]:8333 lastseen=85.1hrs
2021-03-08T03:13:43Z connect() to [2001:0:4137:9e76:34bb:2f1f:a952:3394]:8333 failed: Network is unreachable (101)
2021-03-08T03:13:43Z trying connection 188.25.205.82:8333 lastseen=106.6hrs
2021-03-08T03:13:44Z connect() to 188.25.205.82:8333 failed after select(): Connection refused (111)
2021-03-08T03:13:44Z trying connection [2001:0:4137:9e76:9:139:ad7e:c3bf]:8333 lastseen=73.6hrs
2021-03-08T03:13:44Z connect() to [2001:0:4137:9e76:9:139:ad7e:c3bf]:8333 failed: Network is unreachable (101)

DrahtBot locked this on Aug 18, 2022

Contributors

Labels

P2P Questions and Help Waiting for author

Linked (view graph)

#1 JSON-RPC support for mobile devices ("ultra-lightweight" clients)#18678 Rethink use of thread_local