Sync is very slow or such an error #14669

issue gasparyanyur opened this issue on November 6, 2018
  1. gasparyanyur commented at 2:47 PM on November 6, 2018: none

    <!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->

    <!-- Describe the issue -->

    Very slow sync. When the blocks reach approximately 550.000, the synchronization stops, or starts running very slowly (1 block per hour or 0 block per hour)

    The result of running command

    bitcoind -conf=/root/.bitcoin/bitcoin.conf -datadir=/root/.bitcoin -debug=1 --printtoconsole --disable-wallet

    screenshot from 2018-11-06 09-36-50

    screenshot from 2018-11-06 09-37-19

    <!--- How reliably can you reproduce the issue, what are the steps to do so? -->

    I have installed bitcoin-core , have created configuration file look like this

    server=1
    rpcuser=chainapi
    rpcpassword=whyDidTheBulletProofElephantCrossTheRoad
    rpcallowip=0.0.0.0/0
    rpcport=8332
    dbcache=8192
    maxconnections=40
    

    and have started syncing by the command bitcoind. So after few hours I have got he error look like this

    2018-11-06 15:40:55 connect() to 217.23.10.13:8333 failed after select(): No route to host (113)
    2018-11-06 15:40:55 New outbound peer connected: version: 70015, blocks=549022, peer=8
    2018-11-06 15:40:56 connect() to 173.239.230.40:8333 failed after select(): Connection refused (111)
    2018-11-06 15:40:57 connect() to [2606:c380::215:17ff:feb3:3ec]:8333 failed: Network is unreachable (101)
    2018-11-06 15:40:57 New outbound peer connected: version: 70015, blocks=549022, peer=9
    2018-11-06 15:40:58 connect() to 143.248.56.117:8333 failed after select(): Connection refused (111)
    2018-11-06 15:41:04 New outbound peer connected: version: 70015, blocks=549022, peer=13
    2018-11-06 15:41:04 New outbound peer connected: version: 70015, blocks=549022, peer=14
    2018-11-06 15:41:46 socket recv error Connection reset by peer (104)
    2018-11-06 15:41:46 socket recv error Connection reset by peer (104)
    

    <!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

    Bitcoin 0.16

    <!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

    Ubuntu 18 , SSD Disk, result of lshw

    description: CPU
              product: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
              bus info: cpu@0
              version: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
              slot: CPU1
    

    <!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->

  2. fanquake added the label Linux/Unix on Nov 10, 2018
  3. dongcarl commented at 4:39 AM on November 16, 2018: member

    Could you try without the rpcallowip config option?

  4. MarcoFalke commented at 12:40 PM on April 26, 2020: member

    Is this still an issue with a recent version of Bitcoin Core? If yes, what are the steps to reproduce?

  5. MarcoFalke closed this on Apr 26, 2020

  6. MarcoFalke locked this on Feb 15, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-01 06:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me