Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to open mempool file from disk. Continuing anyway AND failed: Network is unreachable (101) #566

Open
zhousi666 opened this issue May 25, 2018 · 0 comments

Comments

@zhousi666
Copy link

  • I use abc-bitcoin-cash-hardfork branch to deploy my bitcoin-cash-node-service , and then perform block information synchronization. When the %99 was reached, the following problems occurred. I restarted the service and did not solve it. Then I deleted the synced information and resynchronized, but the problem is still there.

  • In addition, I was using docker deployment, I open the 3001 and 8333 port

  • my service log

[2018-05-25T02:54:38.062Z] info: Bitcoin Height: 530144 Percentage: 98.81
[2018-05-25T02:54:53.049Z] info: Bitcoin Height: 530144 Percentage: 99.01
  • my debug.log
2018-05-25 02:54:43 UpdateTip: new best=00000000000000000031687b7320832e5035abe8e3f81fb71517fc541765de83 height=530358 version=0x20000000 log2_work=87.290869 tx=249415371 date='2018-05-15 18:17:47' progress=0.989732 cache=119.4MiB(906966txo)
2018-05-25 02:54:43 UpdateTip: new best=0000000000000000012f7ed499fd8f51fa6b9ea0c1e35ed24d11b5bee8c8b0fe height=530359 version=0x20000000 log2_work=87.290889 tx=249416576 date='2018-05-15 19:16:03' progress=0.989776 cache=119.4MiB(907551txo)
2018-05-25 02:54:43 Failed to open mempool file from disk. Continuing anyway.
2018-05-25 02:54:44 Pre-allocating up to position 0xc00000 in rev01004.dat
2018-05-25 02:54:44 UpdateTip: new best=000000000000000000e2620c245f007f49fb08a51e3f412c436a98ae173dfcb4 height=530360 version=0x20000000 log2_work=87.29091 tx=249419214 date='2018-05-16 01:02:07' progress=0.990037 cache=119.8MiB(910428txo)
2018-05-25 02:54:44 UpdateTip: new best=000000000000000001863cc51b8c32b4e1a6105253cbab88e8e9335a92bff84d height=530361 version=0x20000000 log2_work=87.290929 tx=249419841 date='2018-05-16 02:30:22' progress=0.990104 cache=119.9MiB(911021txo)
2018-05-25 02:58:19 connect() to [2a03:3b40:268:0:5054:ff:fe2d:1d57]:8333 failed: Network is unreachable (101)
2018-05-25 03:00:40 receive version message: [120.77.236.148:8333] /Bitcoin ABC:0.17.1(EB32.0)/: version 70015, blocks=531696, us=195.201.106.187:38760, peer=8
2018-05-25 03:00:40 peer 8 uses CASH magic in its headers
2018-05-25 03:01:35 connect() to [2001:0:5ef5:79fd:149a:29d9:419c:15eb]:8333 failed: Network is unreachable (101)
2018-05-25 03:02:26 receive version message: [119.23.137.81:8333] /Bitcoin ABC:0.17.1(EB32.0)/: version 70015, blocks=531696, us=195.201.106.187:41730, peer=9
2018-05-25 03:02:26 peer 9 uses CASH magic in its headers
2018-05-25 03:04:52 receive version message: [173.255.198.125:8333] /Bitcoin ABC:0.16.0(EB8.0)/: version 70015, blocks=530361, us=195.201.106.187:52928, peer=10
2018-05-25 03:04:52 peer 10 uses CASH magic in its headers
  • my bitcoin.conf file:
server=1
whitelist=127.0.0.1
txindex=1
addressindex=1
timestampindex=1
spentindex=1
zmqpubrawtx=tcp://127.0.0.1:28332
zmqpubhashblock=tcp://127.0.0.1:28332
rpcallowip=127.0.0.1
rpcuser=bitcoin
rpcpassword=local321
uacomment=bitcore
  • my bitcore-node.json
{
  "network": "livenet",
  "port": 3001,
  "services": [
    "bitcoind",
    "insight-api",
    "insight-ui",
    "web"
  ],
  "servicesConfig": {
    "bitcoind": {
      "spawn": {
        "datadir": "/root/data/live.bitcoin.cash.node",
        "exec": "/root/bitcoin-abc/bin/bitcoind"
      }
    }
  }
}

What's missing from my configuration or what else needs to be done? Who can help me, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant