Problem with block sync. Help please!

[maksymsh]

Hi. I have my own blockchain forked from bitcoin. Also i have a mining pool.
It was working fine until node server fell down.

When server was restarted, the problem with syncronization apear. Wallets cant sync with node and says: "Synchronizing with network" or "No block source found".
It seams that some block information was corrupted on server, because blockchain height in my wallet is 6138, but in server - 6014, when is MPOS database last block height is 6139.

I tried to replace blockchain information on server with my own, but useless.

Help please, how can i fix this issue?

[maksymsh]

After reindexing main node on server i have 1639 blocks. But still no sync.

Debug log:

2018-01-18 14:19:45 Coinbit version v0.12.1.0-g9779e1e1f320 (Mon, 11 Apr 2016 13:01:43 +0200)
2018-01-18 14:19:45 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-01-18 14:19:45 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-01-18 14:19:45 Default data directory /root/.coinbit
2018-01-18 14:19:45 Using data directory /root/.coinbit
2018-01-18 14:19:45 Using config file /root/.coinbit/coinbit.conf
2018-01-18 14:19:45 Using at most 125 connections (1024 file descriptors available)
2018-01-18 14:19:45 Using 8 threads for script verification
2018-01-18 14:19:45 scheduler thread start
2018-01-18 14:19:45 libevent: getaddrinfo: address family for nodename not supported
2018-01-18 14:19:45 Binding RPC on address :: port 9443 failed.
2018-01-18 14:19:45 HTTP: creating work queue of depth 16
2018-01-18 14:19:45 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/rpcuser for rpcauth auth generation.
2018-01-18 14:19:45 HTTP: starting 4 worker threads
2018-01-18 14:19:45 Using wallet wallet.dat
2018-01-18 14:19:45 init message: Verifying wallet...
2018-01-18 14:19:45 CDBEnv::Open: LogDir=/root/.coinbit/database ErrorFile=/root/.coinbit/db.log
2018-01-18 14:19:45 Bound to [::]:9444
2018-01-18 14:19:45 Bound to 0.0.0.0:9444
2018-01-18 14:19:45 Cache configuration:
2018-01-18 14:19:45 * Using 2.0MiB for block index database
2018-01-18 14:19:45 * Using 32.5MiB for chain state database
2018-01-18 14:19:45 * Using 65.5MiB for in-memory UTXO set
2018-01-18 14:19:45 init message: Loading block index...
2018-01-18 14:19:45 Opening LevelDB in /root/.coinbit/blocks/index
2018-01-18 14:19:46 Opened LevelDB successfully
2018-01-18 14:19:46 Using obfuscation key for /root/.coinbit/blocks/index: 0000000000000000
2018-01-18 14:19:46 Opening LevelDB in /root/.coinbit/chainstate
2018-01-18 14:19:46 Opened LevelDB successfully
2018-01-18 14:19:46 Using obfuscation key for /root/.coinbit/chainstate: 235e53d5d75c0bb4
2018-01-18 14:19:47 LoadBlockIndexDB: last block file = 0
2018-01-18 14:19:47 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=187838, size=59463790, heights=0...6139, time=2018-01-03...2018-01-16)
2018-01-18 14:19:47 Checking all blk files are present...
2018-01-18 14:19:47 LoadBlockIndexDB: transaction index disabled
2018-01-18 14:19:48 LoadBlockIndexDB: hashBestChain=0000000006af34b2fbbce06c8ce86315ade4a2e41f6b82d0b25e9a992e280276 height=6139 date=2018-01-16 10:05:28 progress=0.044918
2018-01-18 14:19:48 init message: Verifying blocks...
2018-01-18 14:19:48 Verifying last 288 blocks at level 3
2018-01-18 14:19:48 No coin database inconsistencies in last 289 blocks (289 transactions)
2018-01-18 14:19:48  block index            2878ms
2018-01-18 14:19:48 init message: Loading wallet...
2018-01-18 14:19:48 nFileVersion = 120100
2018-01-18 14:19:48 Keys: 104 plaintext, 0 encrypted, 104 w/ metadata, 104 total
2018-01-18 14:19:48  wallet                  182ms
2018-01-18 14:19:48 init message: Activating best chain...
2018-01-18 14:19:48 UpdateTip: new best=00000000001784f585f2fbc540e5424239fa3e8b77cc7036f4a8c85779f73606  height=6138  log2_work=46.30552  tx=6141  date=2018-01-16 09:54:26 progress=0.044760  cache=0.0MiB(1tx)
2018-01-18 14:19:48 AddToWallet 4735aa4fa49c081163536e0d1671d09d4908c301e47ee42015924121f65ceef3 
2018-01-18 14:19:48 UpdateTip: new best=0000000006a5e058bfa287ccc78380c2c1055ce510b77762fe194475025b3503  height=6139  log2_work=46.307321  tx=6142  date=2018-01-16 10:05:28 progress=0.044918  cache=0.0MiB(2tx)
2018-01-18 14:19:48 AddToWallet 7a09fdfcd6d7e7214f34d1d5f2eef6af9750136f1883b532b0f8dc6a69b63ede  new
2018-01-18 14:19:48 mapBlockIndex.size() = 187838
2018-01-18 14:19:48 nBestHeight = 6139
2018-01-18 14:19:48 setKeyPool.size() = 101
2018-01-18 14:19:48 mapWallet.size() = 5505
2018-01-18 14:19:48 mapAddressBook.size() = 2
2018-01-18 14:19:48 init message: Loading addresses...
2018-01-18 14:19:48 torcontrol thread start
2018-01-18 14:19:48 ERROR: Read: Failed to open file /root/.coinbit/banlist.dat
2018-01-18 14:19:48 Invalid or missing banlist.dat; recreating
2018-01-18 14:19:48 Loaded 25 addresses from peers.dat  1ms
2018-01-18 14:19:48 AddLocal(85.25.119.154:9444,1)
2018-01-18 14:19:48 Discover: IPv4 enp2s0: 85.25.119.154
2018-01-18 14:19:48 addcon thread start
2018-01-18 14:19:48 dnsseed thread start
2018-01-18 14:19:48 net thread start
2018-01-18 14:19:48 init message: Done loading
2018-01-18 14:19:48 opencon thread start
2018-01-18 14:19:48 msghand thread start
2018-01-18 14:19:48 receive version message: /Satoshi:0.12.1/: version 70012, blocks=5119, us=85.25.119.154:9444, peer=1
2018-01-18 14:19:48 receive version message: /Satoshi:0.12.1/: version 70012, blocks=5999, us=85.25.119.154:9444, peer=2
2018-01-18 14:19:49 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=3
2018-01-18 14:19:49 keypool reserve 4
2018-01-18 14:19:49 keypool return 4
2018-01-18 14:19:59 P2P peers available. Skipped DNS seeding.
2018-01-18 14:19:59 dnsseed thread exit
2018-01-18 14:21:01 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=4
2018-01-18 14:21:12 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)
2018-01-18 14:21:41 keypool reserve 4
2018-01-18 14:21:41 keypool return 4
2018-01-18 14:22:46 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6138, us=85.25.119.154:9444, peer=5
2018-01-18 14:29:11 keypool reserve 4
2018-01-18 14:29:11 keypool return 4
2018-01-18 14:29:56 connect() to 31.43.86.211:9444 failed after select(): Network is unreachable (101)
2018-01-18 14:31:12 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)
2018-01-18 14:33:06 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6014, us=85.25.119.154:9444, peer=6
2018-01-18 14:33:41 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6014, us=85.25.119.154:9444, peer=7
2018-01-18 14:37:17 receive version message: /Satoshi:0.12.1/: version 70012, blocks=27, us=85.25.119.154:9444, peer=8
2018-01-18 14:37:52 receive version message: /Satoshi:0.12.1/: version 70012, blocks=579, us=85.25.119.154:9444, peer=9
2018-01-18 14:41:15 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)
2018-01-18 14:42:38 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=10
2018-01-18 14:43:16 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=11
2018-01-18 14:43:31 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=12
2018-01-18 14:46:29 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=13
2018-01-18 14:47:49 receive version message: /Satoshi:0.12.1/: version 70012, blocks=0, us=85.25.119.154:9444, peer=14
2018-01-18 14:48:17 receive version message: /Satoshi:0.12.1/: version 70012, blocks=0, us=85.25.119.154:9444, peer=15
2018-01-18 14:48:29 receive version message: /Satoshi:0.12.1/: version 70012, blocks=0, us=85.25.119.154:9444, peer=16
2018-01-18 14:48:39 receive version message: /Satoshi:0.12.1/: version 70012, blocks=0, us=85.25.119.154:9444, peer=17
2018-01-18 14:50:03 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6014, us=85.25.119.154:9444, peer=18
2018-01-18 14:50:13 receive version message: /Satoshi:0.12.1/: version 70012, blocks=3482, us=85.25.119.154:9444, peer=19
2018-01-18 14:50:47 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=20
2018-01-18 14:51:19 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)
2018-01-18 14:52:00 keypool reserve 4
2018-01-18 14:52:00 keypool return 4
2018-01-18 15:01:24 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)
2018-01-18 15:04:39 keypool reserve 4
2018-01-18 15:04:39 keypool return 4

[maksymsh]

Any idead?

[SuperTraderZ]

Hi Max, I wiil ask my friens about your trable...

[bctcomm]

Hey,
1.
Are you sure of your IP configuration? or connection ?

it can be seen that the problem here - 2018-01-18 14:31:12 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)

make a ping for exaple to 92.72.62.19  , which answer ?

2.
if everything is normal with the Internet and with a connection at least to the above written, then check the file /root/.coinbit/banlist.dat

especially important - check permission CHMOD to banlist.dat

[maksymsh]

Hi, bctcomm! Thanks for answer.

1. 2018-01-18 14:31:12 connect() to 92.72.62.19:9444 failed after select(): No route to host (113)
Problem solved and this error doesnt appear in log any more.

2. /root/.coinbit/banlist.dat File doesnt exist. There cant be problems with permissions, because i run my coin as root

New debug.log:
2018-01-24 12:28:48 Coinbit version v0.12.1.0-g9779e1e1f320 (Mon, 11 Apr 2016 13:01:43 +0200)
2018-01-24 12:28:48 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-01-24 12:28:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-01-24 12:28:48 Default data directory /root/.coinbit
2018-01-24 12:28:48 Using data directory /root/.coinbit
2018-01-24 12:28:48 Using config file /root/.coinbit/coinbit.conf
2018-01-24 12:28:48 Using at most 125 connections (1024 file descriptors available)
2018-01-24 12:28:48 Using 8 threads for script verification
2018-01-24 12:28:48 scheduler thread start
2018-01-24 12:28:48 libevent: getaddrinfo: address family for nodename not supported
2018-01-24 12:28:48 Binding RPC on address :: port 9443 failed.
2018-01-24 12:28:48 HTTP: creating work queue of depth 16
2018-01-24 12:28:48 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/rpcuser for rpcauth auth generation.
2018-01-24 12:28:48 HTTP: starting 4 worker threads
2018-01-24 12:28:48 Using wallet wallet.dat
2018-01-24 12:28:48 init message: Verifying wallet...
2018-01-24 12:28:48 CDBEnv::Open: LogDir=/root/.coinbit/database ErrorFile=/root/.coinbit/db.log
2018-01-24 12:28:48 Bound to [::]:9444
2018-01-24 12:28:48 Bound to 0.0.0.0:9444
2018-01-24 12:28:48 Cache configuration:
2018-01-24 12:28:48 * Using 2.0MiB for block index database
2018-01-24 12:28:48 * Using 32.5MiB for chain state database
2018-01-24 12:28:48 * Using 65.5MiB for in-memory UTXO set
2018-01-24 12:28:48 init message: Loading block index...
2018-01-24 12:28:48 Opening LevelDB in /root/.coinbit/blocks/index
2018-01-24 12:28:48 Opened LevelDB successfully
2018-01-24 12:28:48 Using obfuscation key for /root/.coinbit/blocks/index: 0000000000000000
2018-01-24 12:28:48 Opening LevelDB in /root/.coinbit/chainstate
2018-01-24 12:28:49 Opened LevelDB successfully
2018-01-24 12:28:49 Using obfuscation key for /root/.coinbit/chainstate: 235e53d5d75c0bb4
2018-01-24 12:28:50 LoadBlockIndexDB: last block file = 0
2018-01-24 12:28:50 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=187838, size=59463790, heights=0...6139, time=2018-01-03...2018-01-16)
2018-01-24 12:28:50 Checking all blk files are present...
2018-01-24 12:28:50 LoadBlockIndexDB: transaction index disabled
2018-01-24 12:28:50 LoadBlockIndexDB: hashBestChain=0000000000db8bf46c714d2a11410c89127a3f7970421b85ef3af9d304362703 height=6139 date=2018-01-16 10:05:28 progress=0.012481
2018-01-24 12:28:50 init message: Verifying blocks...
2018-01-24 12:28:50 Verifying last 288 blocks at level 3
2018-01-24 12:28:50 No coin database inconsistencies in last 289 blocks (289 transactions)
2018-01-24 12:28:50  block index            2084ms
2018-01-24 12:28:50 init message: Loading wallet...
2018-01-24 12:28:51 nFileVersion = 120100
2018-01-24 12:28:51 Keys: 104 plaintext, 0 encrypted, 104 w/ metadata, 104 total
2018-01-24 12:28:51  wallet                  194ms
2018-01-24 12:28:51 init message: Activating best chain...
2018-01-24 12:28:51 UpdateTip: new best=00000000001784f585f2fbc540e5424239fa3e8b77cc7036f4a8c85779f73606  height=6138  log2_work=46.30552  tx=6141  date=2018-01-16 09:54:26 progress=0.012467  cache=0.0MiB(1tx)
2018-01-24 12:28:51 AddToWallet dc035ebd22d771d9d7757e11b51ec161ffa7b756d22bb5df959bd2173ceb8907  
2018-01-24 12:28:51 UpdateTip: new best=00000000063882ce46b075d0dc7d127034c675d9b0dec741688db430eab62103  height=6139  log2_work=46.307321  tx=6142  date=2018-01-16 10:05:28 progress=0.012481  cache=0.0MiB(2tx)
2018-01-24 12:28:51 AddToWallet 8fbb104733d4de872805af4bfc6af6accfbc1ac610a5dafdb9a09456f1635fd2  
2018-01-24 12:28:51 mapBlockIndex.size() = 187840
2018-01-24 12:28:51 nBestHeight = 6139
2018-01-24 12:28:51 setKeyPool.size() = 101
2018-01-24 12:28:51 mapWallet.size() = 5510
2018-01-24 12:28:51 mapAddressBook.size() = 2
2018-01-24 12:28:51 init message: Loading addresses...
2018-01-24 12:28:51 torcontrol thread start
2018-01-24 12:28:51 ERROR: Read: Failed to open file /root/.coinbit/banlist.dat
2018-01-24 12:28:51 Invalid or missing banlist.dat; recreating
2018-01-24 12:28:51 Loaded 3 addresses from peers.dat  1ms
2018-01-24 12:28:51 AddLocal(85.25.119.154:9444,1)
2018-01-24 12:28:51 Discover: IPv4 enp2s0: 85.25.119.154
2018-01-24 12:28:51 init message: Done loading
2018-01-24 12:28:51 dnsseed thread start
2018-01-24 12:28:51 msghand thread start
2018-01-24 12:28:51 net thread start
2018-01-24 12:28:51 opencon thread start
2018-01-24 12:28:51 addcon thread start
2018-01-24 12:28:51 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=85.25.119.154:9444, peer=1
2018-01-24 12:29:02 Loading addresses from DNS seeds (could take a while)
2018-01-24 12:29:02 2 addresses found from DNS seeds
2018-01-24 12:29:02 dnsseed thread exit
2018-01-24 12:29:02 keypool reserve 4
2018-01-24 12:29:02 keypool return 4
2018-01-24 12:30:47 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6014, us=85.25.119.154:9444, peer=2




file /root/.coinbit/coinbit.conf:
rpcuser=rpcuser
rpcpassword=rpcpassword
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
port=9444
rpcport=9443
addnode=85.25.119.154
addnode=94.130.236.187


Still no sync

[bctcomm]

hey,
the problem with this file still exists:
2018-01-24 12:28:51 ERROR: Read: Failed to open file /root/.coinbit/banlist.dat
if you do't have banlist, create it empty (not forgetting about CHMOD) and try to restart wallet .....

[maksymsh]

Debug log from wallet:

2018-01-24 13:52:57



















2018-01-24 13:52:57 Coinbit version v0.12.1.0-g9779e1e1f320 (Mon, 11 Apr 2016 13:01:43 +0200)
2018-01-24 13:52:57 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-01-24 13:52:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-01-24 13:52:57 Default data directory /home/max/.coinbit
2018-01-24 13:52:57 Using data directory /home/max/.coinbit
2018-01-24 13:52:57 Using config file /home/max/.coinbit/coinbit.conf
2018-01-24 13:52:57 Using at most 125 connections (1024 file descriptors available)
2018-01-24 13:52:57 Using 4 threads for script verification
2018-01-24 13:52:57 Using wallet wallet.dat
2018-01-24 13:52:57 init message: Verifying wallet...
2018-01-24 13:52:57 CDBEnv::Open: LogDir=/home/max/.coinbit/database ErrorFile=/home/max/.coinbit/db.log
2018-01-24 13:52:57 scheduler thread start
2018-01-24 13:52:57 Bound to [::]:9444
2018-01-24 13:52:57 Bound to 0.0.0.0:9444
2018-01-24 13:52:57 Cache configuration:
2018-01-24 13:52:57 * Using 2.0MiB for block index database
2018-01-24 13:52:57 * Using 32.5MiB for chain state database
2018-01-24 13:52:57 * Using 65.5MiB for in-memory UTXO set
2018-01-24 13:52:57 init message: Loading block index...
2018-01-24 13:52:57 Opening LevelDB in /home/max/.coinbit/blocks/index
2018-01-24 13:52:58 Opened LevelDB successfully
2018-01-24 13:52:58 Using obfuscation key for /home/max/.coinbit/blocks/index: 0000000000000000
2018-01-24 13:52:58 Opening LevelDB in /home/max/.coinbit/chainstate
2018-01-24 13:52:58 Opened LevelDB successfully
2018-01-24 13:52:58 Using obfuscation key for /home/max/.coinbit/chainstate: b440dcdf5b74a653
2018-01-24 13:52:59 LoadBlockIndexDB: last block file = 0
2018-01-24 13:52:59 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=187838, size=59463790, heights=0...6139, time=2018-01-03...2018-01-16)
2018-01-24 13:52:59 Checking all blk files are present...
2018-01-24 13:52:59 LoadBlockIndexDB: transaction index disabled
2018-01-24 13:52:59 LoadBlockIndexDB: hashBestChain=0000000006af34b2fbbce06c8ce86315ade4a2e41f6b82d0b25e9a992e280276 height=6139 date=2018-01-16 10:05:28 progress=0.012393
2018-01-24 13:52:59 init message: Verifying blocks...
2018-01-24 13:52:59 Verifying last 288 blocks at level 3
2018-01-24 13:52:59 No coin database inconsistencies in last 289 blocks (289 transactions)
2018-01-24 13:52:59  block index            1660ms
2018-01-24 13:52:59 init message: Loading wallet...
2018-01-24 13:52:59 nFileVersion = 120100
2018-01-24 13:52:59 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total
2018-01-24 13:52:59  wallet                    7ms
2018-01-24 13:52:59 init message: Activating best chain...
2018-01-24 13:52:59 UpdateTip: new best=00000000001784f585f2fbc540e5424239fa3e8b77cc7036f4a8c85779f73606  height=6138  log2_work=46.30552  tx=6141  date=2018-01-16 09:54:26 progress=0.012379  cache=0.0MiB(1tx)
2018-01-24 13:52:59 UpdateTip: new best=000000000833edb9e62ec320f553a6852154006893925eb21126137569e61400  height=6139  log2_work=46.307321  tx=6142  date=2018-01-16 10:05:28 progress=0.012393  cache=0.0MiB(2tx)
2018-01-24 13:52:59 mapBlockIndex.size() = 187838
2018-01-24 13:52:59 nBestHeight = 6139
2018-01-24 13:52:59 setKeyPool.size() = 100
2018-01-24 13:52:59 mapWallet.size() = 3
2018-01-24 13:52:59 mapAddressBook.size() = 1
2018-01-24 13:52:59 init message: Loading addresses...
2018-01-24 13:52:59 torcontrol thread start
2018-01-24 13:52:59 ERROR: Read: Failed to open file /home/max/.coinbit/banlist.dat
2018-01-24 13:52:59 Invalid or missing banlist.dat; recreating
2018-01-24 13:52:59 Loaded 2 addresses from peers.dat  0ms
2018-01-24 13:52:59 dnsseed thread start
2018-01-24 13:52:59 net thread start
2018-01-24 13:52:59 addcon thread start
2018-01-24 13:52:59 init message: Done loading
2018-01-24 13:52:59 GUI: Platform customization: "other"
2018-01-24 13:52:59 msghand thread start
2018-01-24 13:52:59 opencon thread start
2018-01-24 13:52:59 GUI: PaymentServer::LoadRootCAs: Loaded  146  root certificates
2018-01-24 13:52:59 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=193.93.217.51:2147, peer=1
2018-01-24 13:53:00 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=193.93.217.51:2297, peer=2
2018-01-24 13:53:10 P2P peers available. Skipped DNS seeding.
2018-01-24 13:53:10 dnsseed thread exit


Creating empty banlist.dat doesnt solve error. But this error was displayed in working blockchain too.
It means that there is no data in banlist and file banlist.dat is not generated. This error is not related to the topic!

https://ibb.co/iAEFib
https://ibb.co/nGME9G
https://ibb.co/cnoK9G
https://ibb.co/hq2J3b
https://ibb.co/kugp9G

[maksymsh]

Whas this mean?
2018-01-18 14:29:11 keypool reserve 4
2018-01-18 14:29:11 keypool return 4

They indicate that a key has been temporarily removed from the pool and then returned to the pool while an operation involving it is taking place. See the wallet.cpp file.

These functions allow multi-threading (two threads can't be using the same key at the same time).

This messages appears after running getinfo cli command
Output:
 getinfo
{
  "version": 120100,
  "protocolversion": 70012,
  "walletversion": 60000,
  "balance": 265591.59997420,
  "blocks": 6139,
  "timeoffset": 0,
  "connections": 2,
  "proxy": "",
  "difficulty": 25.2872232672551,
  "testnet": false,
  "keypoololdest": 1515072303,
  "keypoolsize": 101,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "errors": ""
}


After start mining (set generate true):

2018-01-24 14:30:03 CoinbitMiner started
2018-01-24 14:30:03 keypool added key 103, size=101
2018-01-24 14:30:03 keypool reserve 3
2018-01-24 14:33:08 keypool added key 104, size=101
2018-01-24 14:33:08 keypool reserve 4
2018-01-24 14:33:08 keypool return 4

But miner not working, there is no CPU usage

[bctcomm]

2018-01-24 13:52:59 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=193.93.217.51:2147, peer=1
2018-01-24 13:53:00 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=193.93.217.51:2297, peer=2

everything looks OK already  what does not work yet ?

[maksymsh]

https://ibb.co/iAEFib

Still no sync, miner not working

[bctcomm]

look, is't OK or ?

Number of connection 2 (In:0 / Out:2)  (Number of connection 2 (In:0 / Out:2) - https://ibb.co/cnoK9G)

Check again all- configs of network, ports and firewalls

[bctcomm]

you did not show the full configuration of the test network - maybe the answer from the second host is lost, or there is an incorrect default gateway - ping all the hosts of each other....
 

[maksymsh]

If i start a new wallet without any blockchain data i get this debug.log:

2018-01-24 16:29:37 Coinbit version v0.12.1.0-g9779e1e1f320 (Mon, 11 Apr 2016 13:01:43 +0200)
2018-01-24 16:29:37 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-01-24 16:29:38 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-01-24 16:29:38 Default data directory /home/max/.coinbit
2018-01-24 16:29:38 Using data directory /home/max/.coinbit
2018-01-24 16:29:38 Using config file /home/max/.coinbit/coinbit.conf
2018-01-24 16:29:38 Using at most 125 connections (1024 file descriptors available)
2018-01-24 16:29:38 Using 2 threads for script verification
2018-01-24 16:29:38 Using wallet wallet.dat
2018-01-24 16:29:38 init message: Verifying wallet...
2018-01-24 16:29:38 CDBEnv::Open: LogDir=/home/max/.coinbit/database ErrorFile=/home/max/.coinbit/db.log
2018-01-24 16:29:38 scheduler thread start
2018-01-24 16:29:38 Bound to [::]:9444
2018-01-24 16:29:38 Bound to 0.0.0.0:9444
2018-01-24 16:29:38 Cache configuration:
2018-01-24 16:29:38 * Using 2.0MiB for block index database
2018-01-24 16:29:38 * Using 32.5MiB for chain state database
2018-01-24 16:29:38 * Using 65.5MiB for in-memory UTXO set
2018-01-24 16:29:38 init message: Loading block index...
2018-01-24 16:29:38 Opening LevelDB in /home/max/.coinbit/blocks/index
2018-01-24 16:29:38 Opened LevelDB successfully
2018-01-24 16:29:38 Using obfuscation key for /home/max/.coinbit/blocks/index: 0000000000000000
2018-01-24 16:29:38 Opening LevelDB in /home/max/.coinbit/chainstate
2018-01-24 16:29:38 Opened LevelDB successfully
2018-01-24 16:29:38 Wrote new obfuscate key for /home/max/.coinbit/chainstate: 6bf5ba8196c16f05
2018-01-24 16:29:38 Using obfuscation key for /home/max/.coinbit/chainstate: 6bf5ba8196c16f05
2018-01-24 16:29:38 LoadBlockIndexDB: last block file = 0
2018-01-24 16:29:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-01-24 16:29:38 Checking all blk files are present...
2018-01-24 16:29:38 LoadBlockIndexDB: transaction index disabled
2018-01-24 16:29:38 Initializing databases...
2018-01-24 16:29:38 Pre-allocating up to position 0x1000000 in blk00000.dat
2018-01-24 16:29:38 UpdateTip: new best=00000000323b8b1db35e8511c231a5b8fa45f9c19ac2348c4a3c5d94df8d2ae7  height=0  log2_work=32.000022  tx=1  date=2018-01-03 20:37:53 progress=0.000001  cache=0.0MiB(0tx)
2018-01-24 16:29:38 init message: Verifying blocks...
2018-01-24 16:29:38  block index             488ms
2018-01-24 16:29:38 init message: Loading wallet...
2018-01-24 16:29:38 nFileVersion = 120100
2018-01-24 16:29:38 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total
2018-01-24 16:29:38  wallet                  108ms
2018-01-24 16:29:38 init message: Activating best chain...
2018-01-24 16:29:38 mapBlockIndex.size() = 1
2018-01-24 16:29:38 nBestHeight = 0
2018-01-24 16:29:38 setKeyPool.size() = 100
2018-01-24 16:29:38 mapWallet.size() = 0
2018-01-24 16:29:38 mapAddressBook.size() = 1
2018-01-24 16:29:38 init message: Loading addresses...
2018-01-24 16:29:38 torcontrol thread start
2018-01-24 16:29:38 ERROR: Read: Failed to open file /home/max/.coinbit/peers.dat
2018-01-24 16:29:38 Invalid or missing peers.dat; recreating
2018-01-24 16:29:38 ERROR: Read: Failed to open file /home/max/.coinbit/banlist.dat
2018-01-24 16:29:38 Invalid or missing banlist.dat; recreating
2018-01-24 16:29:38 Loaded 0 addresses from peers.dat  0ms
2018-01-24 16:29:38 dnsseed thread start
2018-01-24 16:29:38 Loading addresses from DNS seeds (could take a while)
2018-01-24 16:29:38 net thread start
2018-01-24 16:29:38 init message: Done loading
2018-01-24 16:29:38 addcon thread start
2018-01-24 16:29:38 GUI: Platform customization: "other"
2018-01-24 16:29:38 msghand thread start
2018-01-24 16:29:38 opencon thread start
2018-01-24 16:29:38 2 addresses found from DNS seeds
2018-01-24 16:29:38 dnsseed thread exit
2018-01-24 16:29:38 GUI: PaymentServer::LoadRootCAs: Loaded  146  root certificates
2018-01-24 16:29:39 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=94.231.68.146:37542, peer=1
2018-01-24 16:29:41 receive version message: /Satoshi:0.12.1/: version 70012, blocks=6139, us=94.231.68.146:36054, peer=2

Where 94.231.68.146 is my local pc address with started wallet.
As u can see, wallet found 6139 blocks but they are not downloaded.
We can see 2 our node peers in debug window (https://ibb.co/kugp9G), we have received and sent data -> connection is OK, but "No block source available" message shown in wallet.
And there are no other related errors
Why?

[bctcomm]

85.25.119.154:9444 via 193.93.217.51 ........
what is it ?

Once again, what is your test network environment ? - draw to begin and show me ...
which hosts have what address?

and ping from all hosts - each host must respond to another

[maksymsh]

I have 2 VPS with nodes

VPS1 85.25.119.154
VPS2 94.130.236.187

And LOCAL PC with dynamic IP. Currently its 94.231.68.146.

Ping results:

1) Ping from VPS1 to VPS2 - OK

Code:

triton746:~# ping 94.130.236.187
PING 94.130.236.187 (94.130.236.187) 56(84) bytes of data.
64 bytes from 94.130.236.187: icmp_seq=1 ttl=57 time=8.42 ms
64 bytes from 94.130.236.187: icmp_seq=2 ttl=57 time=8.39 ms
64 bytes from 94.130.236.187: icmp_seq=3 ttl=57 time=8.39 ms
64 bytes from 94.130.236.187: icmp_seq=4 ttl=57 time=8.42 ms
64 bytes from 94.130.236.187: icmp_seq=5 ttl=57 time=8.43 ms
64 bytes from 94.130.236.187: icmp_seq=6 ttl=57 time=8.44 ms
64 bytes from 94.130.236.187: icmp_seq=7 ttl=57 time=8.39 ms
64 bytes from 94.130.236.187: icmp_seq=8 ttl=57 time=8.38 ms
64 bytes from 94.130.236.187: icmp_seq=9 ttl=57 time=8.44 ms
64 bytes from 94.130.236.187: icmp_seq=10 ttl=57 time=8.39 ms
--- 94.130.236.187 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 8.382/8.413/8.447/0.047 ms

2) Ping from VPS2 to VPS1 - OK

Code:

root@Ubuntu-1604-xenial-64-minimal ~/.coinbit # ping 85.25.119.154
PING 85.25.119.154 (85.25.119.154) 56(84) bytes of data.
64 bytes from 85.25.119.154: icmp_seq=1 ttl=56 time=8.34 ms
64 bytes from 85.25.119.154: icmp_seq=2 ttl=56 time=8.38 ms
64 bytes from 85.25.119.154: icmp_seq=3 ttl=56 time=8.38 ms
64 bytes from 85.25.119.154: icmp_seq=4 ttl=56 time=8.37 ms
64 bytes from 85.25.119.154: icmp_seq=5 ttl=56 time=8.38 ms
64 bytes from 85.25.119.154: icmp_seq=6 ttl=56 time=8.41 ms
64 bytes from 85.25.119.154: icmp_seq=7 ttl=56 time=8.42 ms
64 bytes from 85.25.119.154: icmp_seq=8 ttl=56 time=8.38 ms
64 bytes from 85.25.119.154: icmp_seq=9 ttl=56 time=8.40 ms
64 bytes from 85.25.119.154: icmp_seq=10 ttl=56 time=8.37 ms
--- 85.25.119.154 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 8.343/8.386/8.420/0.093 ms

3) Ping from LOCAL to VPS1 - OK

Code:

ping 85.25.119.154
PING 85.25.119.154 (85.25.119.154) 56(84) bytes of data.
64 bytes from 85.25.119.154: icmp_seq=1 ttl=57 time=41.9 ms
64 bytes from 85.25.119.154: icmp_seq=2 ttl=57 time=38.5 ms
64 bytes from 85.25.119.154: icmp_seq=3 ttl=57 time=42.8 ms
64 bytes from 85.25.119.154: icmp_seq=4 ttl=57 time=41.9 ms
64 bytes from 85.25.119.154: icmp_seq=5 ttl=57 time=43.7 ms
64 bytes from 85.25.119.154: icmp_seq=6 ttl=57 time=46.4 ms
64 bytes from 85.25.119.154: icmp_seq=7 ttl=57 time=45.9 ms
64 bytes from 85.25.119.154: icmp_seq=8 ttl=57 time=43.7 ms
64 bytes from 85.25.119.154: icmp_seq=9 ttl=57 time=46.4 ms
64 bytes from 85.25.119.154: icmp_seq=10 ttl=57 time=40.8 ms
--- 85.25.119.154 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 38.516/43.251/46.474/2.445 ms

4) Ping from LOCAL to VPS2 - OK

Code:

ping 94.231.68.146
PING 94.231.68.146 (94.231.68.146) 56(84) bytes of data.
64 bytes from 94.231.68.146: icmp_seq=1 ttl=64 time=0.908 ms
64 bytes from 94.231.68.146: icmp_seq=2 ttl=64 time=1.37 ms
64 bytes from 94.231.68.146: icmp_seq=3 ttl=64 time=0.948 ms
64 bytes from 94.231.68.146: icmp_seq=4 ttl=64 time=0.846 ms
64 bytes from 94.231.68.146: icmp_seq=5 ttl=64 time=38.2 ms
64 bytes from 94.231.68.146: icmp_seq=6 ttl=64 time=0.864 ms
64 bytes from 94.231.68.146: icmp_seq=7 ttl=64 time=0.944 ms
64 bytes from 94.231.68.146: icmp_seq=8 ttl=64 time=0.882 ms
64 bytes from 94.231.68.146: icmp_seq=9 ttl=64 time=0.950 ms
64 bytes from 94.231.68.146: icmp_seq=10 ttl=64 time=0.924 ms
64 bytes from 94.231.68.146: icmp_seq=11 ttl=64 time=0.872 ms
64 bytes from 94.231.68.146: icmp_seq=12 ttl=64 time=2.03 ms
64 bytes from 94.231.68.146: icmp_seq=13 ttl=64 time=0.851 ms
64 bytes from 94.231.68.146: icmp_seq=14 ttl=64 time=0.944 ms
^C
--- 94.231.68.146 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13074ms
rtt min/avg/max/mdev = 0.846/3.682/38.204/9.579 ms

5) Ping from VPS1 to LOCAL - Error

Code:

triton746:~# ping 94.231.68.146
PING 94.231.68.146 (94.231.68.146) 56(84) bytes of data.
--- 94.231.68.146 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9072ms

6) Ping from VPS2 to LOCAL - Error

Code:

root@Ubuntu-1604-xenial-64-minimal ~/.coinbit # ping 94.231.68.146
PING 94.231.68.146 (94.231.68.146) 56(84) bytes of data.
--- 94.231.68.146 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9210ms

7) Ping from Local to 94.231.68.146 - OK

Code:

ping 94.231.68.146
PING 94.231.68.146 (94.231.68.146) 56(84) bytes of data.
64 bytes from 94.231.68.146: icmp_seq=1 ttl=64 time=1.12 ms
64 bytes from 94.231.68.146: icmp_seq=2 ttl=64 time=0.843 ms
64 bytes from 94.231.68.146: icmp_seq=3 ttl=64 time=0.882 ms
64 bytes from 94.231.68.146: icmp_seq=4 ttl=64 time=0.952 ms
64 bytes from 94.231.68.146: icmp_seq=5 ttl=64 time=0.914 ms
64 bytes from 94.231.68.146: icmp_seq=6 ttl=64 time=0.811 ms
64 bytes from 94.231.68.146: icmp_seq=7 ttl=64 time=0.849 ms
64 bytes from 94.231.68.146: icmp_seq=8 ttl=64 time=0.887 ms
64 bytes from 94.231.68.146: icmp_seq=9 ttl=64 time=0.910 ms
64 bytes from 94.231.68.146: icmp_seq=10 ttl=64 time=1.06 ms
--- 94.231.68.146 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9083ms
rtt min/avg/max/mdev = 0.811/0.923/1.122/0.095 ms

Next we will listen requests on rpc port 9444 :

VPS1

Code:

triton746:~# tcpdump port 9444 and '(tcp-syn|tcp-ack)!=0'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
19:13:24.146918 IP static.187.236.130.94.clients.your-server.de.9444 > triton746.hostiq.ua.54854: Flags [P.], seq 1209101586:1209101618, ack 537668388, win 240, options [nop,nop,TS val 4230430442 ecr 113821175], length 32
19:13:24.147244 IP triton746.hostiq.ua.54854 > static.187.236.130.94.clients.your-server.de.9444: Flags [P.], seq 1:33, ack 32, win 250, options [nop,nop,TS val 113851181 ecr 4230430442], length 32
19:13:24.147362 IP triton746.hostiq.ua.54854 > static.187.236.130.94.clients.your-server.de.9444: Flags [P.], seq 33:65, ack 32, win 250, options [nop,nop,TS val 113851181 ecr 4230430442], length 32
19:13:24.155681 IP static.187.236.130.94.clients.your-server.de.9444 > triton746.hostiq.ua.54854: Flags [.], ack 33, win 240, options [nop,nop,TS val 4230430451 ecr 113851181], length 0
19:13:24.155708 IP static.187.236.130.94.clients.your-server.de.9444 > triton746.hostiq.ua.54854: Flags [.], ack 65, win 240, options [nop,nop,TS val 4230430451 ecr 113851181], length 0
19:13:24.155798 IP static.187.236.130.94.clients.your-server.de.9444 > triton746.hostiq.ua.54854: Flags [P.], seq 32:64, ack 65, win 240, options [nop,nop,TS val 4230430451 ecr 113851181], length 32
19:13:24.193808 IP triton746.hostiq.ua.54854 > static.187.236.130.94.clients.your-server.de.9444: Flags [.], ack 64, win 250, options [nop,nop,TS val 113851193 ecr 4230430451], length 0
19:13:45.667604 IP pppoe.lvivlan.net.ua.36954 > triton746.hostiq.ua.9444: Flags [F.], seq 3429690245, ack 2677835407, win 229, options [nop,nop,TS val 2048434459 ecr 113837619], length 0
19:13:45.667784 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.36954: Flags [F.], seq 1, ack 1, win 227, options [nop,nop,TS val 113856561 ecr 2048434459], length 0
19:13:45.707913 IP pppoe.lvivlan.net.ua.36954 > triton746.hostiq.ua.9444: Flags [.], ack 2, win 229, options [nop,nop,TS val 2048434500 ecr 113856561], length 0
19:13:59.006428 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [S], seq 2641790739, win 29200, options [mss 1452,sackOK,TS val 2048447798 ecr 0,nop,wscale 7], length 0
19:13:59.006468 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [S.], seq 3190066764, ack 2641790740, win 28960, options [mss 1460,sackOK,TS val 113859896 ecr 2048447798,nop,wscale 7], length 0
19:13:59.057026 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [.], ack 1, win 229, options [nop,nop,TS val 2048447848 ecr 113859896], length 0
19:13:59.057626 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [P.], seq 1:127, ack 1, win 229, options [nop,nop,TS val 2048447849 ecr 113859896], length 126
19:13:59.057639 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [.], ack 127, win 227, options [nop,nop,TS val 113859908 ecr 2048447849], length 0
19:13:59.058022 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [P.], seq 1:127, ack 127, win 227, options [nop,nop,TS val 113859909 ecr 2048447849], length 126
19:13:59.058191 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [P.], seq 127:151, ack 127, win 227, options [nop,nop,TS val 113859909 ecr 2048447849], length 24
19:13:59.058365 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [P.], seq 151:183, ack 127, win 227, options [nop,nop,TS val 113859909 ecr 2048447849], length 32
19:13:59.104120 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [.], ack 127, win 229, options [nop,nop,TS val 2048447895 ecr 113859909], length 0
19:13:59.104385 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [.], ack 151, win 229, options [nop,nop,TS val 2048447895 ecr 113859909], length 0
19:13:59.104717 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [P.], seq 127:151, ack 151, win 229, options [nop,nop,TS val 2048447895 ecr 113859909], length 24
19:13:59.104884 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [P.], seq 183:207, ack 151, win 227, options [nop,nop,TS val 113859920 ecr 2048447895], length 24
19:13:59.107588 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [P.], seq 151:263, ack 183, win 229, options [nop,nop,TS val 2048447899 ecr 113859909], length 112
19:13:59.107870 IP triton746.hostiq.ua.9444 > pppoe.lvivlan.net.ua.37004: Flags [P.], seq 207:239, ack 263, win 227, options [nop,nop,TS val 113859921 ecr 2048447899], length 32
19:13:59.151313 IP pppoe.lvivlan.net.ua.37004 > triton746.hostiq.ua.9444: Flags [.], ack 239, win 229, options [nop,nop,TS val 2048447943 ecr 113859920], length 0
^C
25 packets captured
25 packets received by filter
0 packets dropped by kernel

VPS2

Code:

root@Ubuntu-1604-xenial-64-minimal ~ # tcpdump port 9444 and '(tcp-syn|tcp-ack)!=0'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
19:13:24.140416 IP Ubuntu-1604-xenial-64-minimal.9444 > triton746.dedicatedpanel.com.54854: Flags [P.], seq 1209101586:1209101618, ack 537668388, win 240, options [nop,nop,TS val 4230430442 ecr 113821175], length 32
19:13:24.149205 IP triton746.dedicatedpanel.com.54854 > Ubuntu-1604-xenial-64-minimal.9444: Flags [P.], seq 1:33, ack 32, win 250, options [nop,nop,TS val 113851181 ecr 4230430442], length 32
19:13:24.149229 IP Ubuntu-1604-xenial-64-minimal.9444 > triton746.dedicatedpanel.com.54854: Flags [.], ack 33, win 240, options [nop,nop,TS val 4230430451 ecr 113851181], length 0
19:13:24.149254 IP triton746.dedicatedpanel.com.54854 > Ubuntu-1604-xenial-64-minimal.9444: Flags [P.], seq 33:65, ack 32, win 250, options [nop,nop,TS val 113851181 ecr 4230430442], length 32
19:13:24.149260 IP Ubuntu-1604-xenial-64-minimal.9444 > triton746.dedicatedpanel.com.54854: Flags [.], ack 65, win 240, options [nop,nop,TS val 4230430451 ecr 113851181], length 0
19:13:24.149405 IP Ubuntu-1604-xenial-64-minimal.9444 > triton746.dedicatedpanel.com.54854: Flags [P.], seq 32:64, ack 65, win 240, options [nop,nop,TS val 4230430451 ecr 113851181], length 32
19:13:24.195761 IP triton746.dedicatedpanel.com.54854 > Ubuntu-1604-xenial-64-minimal.9444: Flags [.], ack 64, win 250, options [nop,nop,TS val 113851193 ecr 4230430451], length 0
19:13:45.663992 IP pppoe.lvivlan.net.ua.38444 > Ubuntu-1604-xenial-64-minimal.9444: Flags [F.], seq 1062401278, ack 3660925363, win 229, options [nop,nop,TS val 4001573094 ecr 314325229], length 0
19:13:45.664075 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38444: Flags [F.], seq 1, ack 1, win 235, options [nop,nop,TS val 314401629 ecr 4001573094], length 0
19:13:45.705420 IP pppoe.lvivlan.net.ua.38444 > Ubuntu-1604-xenial-64-minimal.9444: Flags [.], ack 2, win 229, options [nop,nop,TS val 4001573136 ecr 314401629], length 0
19:13:58.456773 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [S], seq 300531225, win 29200, options [mss 1452,sackOK,TS val 4001585887 ecr 0,nop,wscale 7], length 0
19:13:58.456799 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [S.], seq 4276075128, ack 300531226, win 28960, options [mss 1460,sackOK,TS val 314414421 ecr 4001585887,nop,wscale 7], length 0
19:13:58.501648 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [.], ack 1, win 229, options [nop,nop,TS val 4001585932 ecr 314414421], length 0
19:13:58.502306 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [P.], seq 1:127, ack 1, win 229, options [nop,nop,TS val 4001585933 ecr 314414421], length 126
19:13:58.502325 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [.], ack 127, win 227, options [nop,nop,TS val 314414467 ecr 4001585933], length 0
19:13:58.502523 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [P.], seq 1:127, ack 127, win 227, options [nop,nop,TS val 314414467 ecr 4001585933], length 126
19:13:58.502547 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [P.], seq 127:151, ack 127, win 227, options [nop,nop,TS val 314414467 ecr 4001585933], length 24
19:13:58.502688 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [P.], seq 151:183, ack 127, win 227, options [nop,nop,TS val 314414467 ecr 4001585933], length 32
19:13:58.554172 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [.], ack 127, win 229, options [nop,nop,TS val 4001585976 ecr 314414467], length 0
19:13:58.554295 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [P.], seq 127:151, ack 127, win 229, options [nop,nop,TS val 4001585976 ecr 314414467], length 24
19:13:58.554432 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [P.], seq 183:207, ack 151, win 227, options [nop,nop,TS val 314414519 ecr 4001585976], length 24
19:13:58.555013 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [.], ack 183, win 229, options [nop,nop,TS val 4001585978 ecr 314414467], length 0
19:13:58.556530 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [P.], seq 151:356, ack 183, win 229, options [nop,nop,TS val 4001585987 ecr 314414467], length 205
19:13:58.556724 IP Ubuntu-1604-xenial-64-minimal.9444 > pppoe.lvivlan.net.ua.38494: Flags [P.], seq 207:239, ack 356, win 235, options [nop,nop,TS val 314414521 ecr 4001585987], length 32
19:13:58.598720 IP pppoe.lvivlan.net.ua.38494 > Ubuntu-1604-xenial-64-minimal.9444: Flags [.], ack 239, win 229, options [nop,nop,TS val 4001586029 ecr 314414519], length 0
^C
25 packets captured
25 packets received by filter
0 packets dropped by kernel

LOCAL

Code:

tcpdump port 9444 and '(tcp-syn|tcp-ack)!=0'
[sudo] password for max: 
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlp3s0, link-type EN10MB (Ethernet), capture size 262144 bytes
20:08:29.153560 IP max-Lenovo-G500.Dlink.38444 > static.187.236.130.94.clients.your-server.de.9444: Flags [P.], seq 1062401086:1062401118, ack 3660925171, win 229, options [nop,nop,TS val 4001256605 ecr 313965144], length 32
20:08:29.185004 IP static.187.236.130.94.clients.your-server.de.9444 > max-Lenovo-G500.Dlink.38444: Flags [P.], seq 1:33, ack 0, win 235, options [nop,nop,TS val 314085134 ecr 4001136598], length 32
20:08:29.185218 IP max-Lenovo-G500.Dlink.38444 > static.187.236.130.94.clients.your-server.de.9444: Flags [P.], seq 32:64, ack 33, win 229, options [nop,nop,TS val 4001256636 ecr 314085134], length 32
20:08:29.196239 IP static.187.236.130.94.clients.your-server.de.9444 > max-Lenovo-G500.Dlink.38444: Flags [P.], seq 33:65, ack 32, win 235, options [nop,nop,TS val 314085146 ecr 4001256605], length 32
20:08:29.238164 IP max-Lenovo-G500.Dlink.38444 > static.187.236.130.94.clients.your-server.de.9444: Flags [.], ack 65, win 229, options [nop,nop,TS val 4001256647 ecr 314085146], length 0
20:08:29.343998 IP static.187.236.130.94.clients.your-server.de.9444 > max-Lenovo-G500.Dlink.38444: Flags [.], ack 64, win 235, options [nop,nop,TS val 314085230 ecr 4001256636], length 0
20:08:29.697114 IP max-Lenovo-G500.Dlink.36954 > triton746.dedicatedpanel.com.9444: Flags [P.], seq 3429690053:3429690085, ack 2677835215, win 229, options [nop,nop,TS val 2048118513 ecr 113747558], length 32
20:08:29.698245 IP triton746.dedicatedpanel.com.9444 > max-Lenovo-G500.Dlink.36954: Flags [P.], seq 1:33, ack 0, win 227, options [nop,nop,TS val 113777563 ecr 2047998499], length 32
20:08:29.698386 IP max-Lenovo-G500.Dlink.36954 > triton746.dedicatedpanel.com.9444: Flags [P.], seq 32:64, ack 33, win 229, options [nop,nop,TS val 2048118514 ecr 113777563], length 32
20:08:29.740845 IP triton746.dedicatedpanel.com.9444 > max-Lenovo-G500.Dlink.36954: Flags [P.], seq 33:65, ack 32, win 227, options [nop,nop,TS val 113777573 ecr 2048118513], length 32
20:08:29.781488 IP triton746.dedicatedpanel.com.9444 > max-Lenovo-G500.Dlink.36954: Flags [.], ack 64, win 227, options [nop,nop,TS val 113777584 ecr 2048118514], length 0
20:08:29.782154 IP max-Lenovo-G500.Dlink.36954 > triton746.dedicatedpanel.com.9444: Flags [.], ack 65, win 229, options [nop,nop,TS val 2048118598 ecr 113777573], length 0

[bctcomm]

this must be told before begins ...
 
now, keep explaining, do not be shy...

why do you use the first and second VPSs?

what is installed on them and for what?
I need to exclude the Variant, that the problem is on the VPS side...

to be cont.....,  - the local computer:  there only installed the Wallet or ?

why did the system collapse or what happened?

tell in detail ....