bitcore Problem Connection / Disconnection

Problem Connection / Disconnection

Open Droppix opened this issue 4 years ago • 4 comments

Hi,

I have on my server bitcoin (bitcore 0.19.x, prune, testnet), and I install the last version of bitpay/bitcore (from master)

bitcoin.conf

prune=550
minrelaytxfee=0.00005
limitfreerelay=0
dbcache=50
maxmempool=100
maxorphantx=10

whitelist=127.0.0.1
txindex=0
listen=1
server=1
testnet=1
irc=1
upnp=1

[test]
port=18333
rpcuser=TEST
rpcpassword=TEST
rpcport=18332
rpcallowip=0.0.0.0/0
rpcallowip=127.0.0.1
rpcbind=X.X.X.X

bitcore config

 Object.assign(config.chains, {
      BTC: {
        testnet: {
          chainSource: 'p2p',
          trustedPeers: [{ host: 'X.X.X.X', port: 18333 }],
          rpc: {
            host: 'X.X.X.X,
            port: 18332,
            username: 'TEST',
            password: 'TEST'
          }
        }
      }
    });

I receive a few events peerready/peerheaders, then disconnect (peerdisconnect). (on server: ufw allow 18332, ufw allow 18333)

Any idea ?

Log file

{"message":"2020-05-30 17:38:40.574 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"This worker is now the syncing node for BTC testnet","level":"info"}
{"message":"InternalStateProvider::getLocalTip::called::","level":"debug"}
{"message":"InternalStateProvider::getLocalTip::resolved::","level":"debug"}
{"message":"InternalStateProvider::getLocatorHashes::called::","level":"debug"}
{"message":"InternalStateProvider::getLocatorHashes::resolved::","level":"debug"}
{"peer":"X.X.X.X:18333","chain":"BTC","network":"testnet","count":2000,"level":"debug","message":"peerheaders message received"}
{"message":"InternalStateProvider::getLocalTip::called::","level":"debug"}
{"message":"InternalStateProvider::getLocalTip::resolved::","level":"debug"}
{"message":"2020-05-30 17:38:43.541 GMT+2 | Syncing 2000 blocks | Chain: BTC | Network: testnet","level":"info"}
{"level":"debug","message":"Getting block, hash:"}
{"message":"2020-05-30 17:38:43.569 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:39:15.575 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:39:15.673 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:39:50.581 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:39:50.743 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:40:25.598 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:40:25.847 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:41:00.612 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:41:00.955 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:41:35.627 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:41:36.550 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:42:10.648 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:42:11.167 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}
{"message":"2020-05-30 17:42:45.668 GMT+2 | Connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"info"}
{"message":"2020-05-30 17:42:46.272 GMT+2 | Not connected to peer: X.X.X.X:18333 | Chain: BTC | Network: testnet","level":"warn"}