Title: bitcoind seems stuck bringing a new node online Post by: stuman2 on September 27, 2017, 02:20:11 PM Bitcoin Core: Bitcoin version v0.15.0.0-g3751912e8e
OS: Linux 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Hardware: Acer Aspire 4270Z, 64 bit, Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz, 3gb memory 640GB hd at 82% Problem: Bringing a full node online and the progress has stopped at best chain: hashBestChain=00000000000000000044ac6ea4ac31650fb98bc030c741527bbaa7f0fa769208 height=478006 date=2017-07-28 19:25:00 progress=0.938731 Details: Debug.log supplies peer information, but never reaches another new best block. Peer information includes peer's block height>what I show above. I had network issues with my ISP last Saturday due to a storm, but have since gotten back online. This is the bitcoind daemon running on a non-gui Linux install, so there is no screen shot. I get a fair number of "connection refused" messages in the debug.log, but that seems normal as I was getting those when building up to this point. It just simply doesn't progress anymore, whether I have port 8333 open or not. (I see no need to open it until I have the entire blockchain downloaded, but I have tried both.) There are no transactions of mine involved, as this a "new" wallet instance. I won't put any coin into it until it is caught up. Some communication is happening as the progress was at one time 0.94xxxxx, but has dropped since more transactions have been added to the chain. This happened before at 68%, but I restarted the process by deleting all the blocks downloaded and re-indexing. Title: Re: bitcoind seems stuck bringing a new node online Post by: aleksej996 on September 27, 2017, 06:57:07 PM 2017-07-28 19:25:00 That is very close to the Bitcoin Cash fork. Maybe your node only has Bitcoin Cash nodes as peers, I don't know. Perhaps try deleting the peers.dat file in the data directory. Title: Re: bitcoind seems stuck bringing a new node online Post by: cr1776 on September 27, 2017, 07:33:37 PM Can you post the debug log?
Title: Re: bitcoind seems stuck bringing a new node online Post by: stuman2 on September 27, 2017, 10:27:25 PM It was cranking up until late July of this year, then stopped. I did a re-index, which resulted in a log of mostly "new best=" lines up to here.
... 2017-09-27 18:32:50 UpdateTip: new best=000000000000007dd4065aee391fe2e68862d060b495089e29596a9591af5c84 height=190200 version=0x00000001 log2_work=68.426662 tx=5188555 date='2012-07-22 08:10:39' progress=0.020077 cache=279.1MiB(2120132txo) 2017-09-27 18:32:50 ERROR: ConnectBlock: CheckQueue failed 2017-09-27 18:32:50 InvalidChainFound: invalid block=00000000000002e51eb56bc3dea3bb9229d6146f3beac71aa4d3777ee900fd30 height=190201 log2_work=68.426691 date=2012-07-22 08:12:36 2017-09-27 18:32:50 InvalidChainFound: current best=000000000000007dd4065aee391fe2e68862d060b495089e29596a9591af5c84 height=190200 log2_work=68.426662 date=2012-07-22 08:10:39 2017-09-27 18:32:50 ERROR: ConnectTip(): ConnectBlock 00000000000002e51eb56bc3dea3bb9229d6146f3beac71aa4d3777ee900fd30 failed 2017-09-27 18:32:50 InvalidChainFound: invalid block=00000000000002e51eb56bc3dea3bb9229d6146f3beac71aa4d3777ee900fd30 height=190201 log2_work=68.426691 date=2012-07-22 08:12:36 2017-09-27 18:32:50 InvalidChainFound: current best=000000000000007dd4065aee391fe2e68862d060b495089e29596a9591af5c84 height=190200 log2_work=68.426662 date=2012-07-22 08:10:39 2017-09-27 18:32:50 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired 2017-09-27 18:35:01 connect() to [2001:0:9d38:90d7:38a2:121f:acf4:666c]:8333 failed: Network is unreachable (101) 2017-09-27 18:35:10 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=487221, us=174.71.159.134:45046, peer=24 2017-09-27 18:40:30 connect() to [2001:0:9d38:6abd:28f4:fbff:e0e7:888]:8333 failed: Network is unreachable (101) 2017-09-27 18:41:16 connect() to [2001:470:28:193::2]:8333 failed: Network is unreachable (101) 2017-09-27 18:45:51 connect() to [2001:980:a510:1:c5e7:56f7:9d:ab36]:8333 failed: Network is unreachable (101) 2017-09-27 18:48:11 connect() to 5.157.38.35:8333 failed after select(): Connection refused (111) 2017-09-27 18:51:28 connect() to [2804:14d:78e2:80ae:e426:3dd3:cdb9:e0e6]:8333 failed: Network is unreachable (101) 2017-09-27 18:52:38 connect() to 212.92.123.65:8333 failed after select(): Connection refused (111) 2017-09-27 18:53:41 connect() to [2001:0:4137:9e76:1c2d:3a57:abb5:9ddc]:8333 failed: Network is unreachable (101) 2017-09-27 18:57:37 connect() to [2a02:168:5829:0:a336:5bbf:c83b:94f8]:8333 failed: Network is unreachable (101) 2017-09-27 19:01:16 connect() to [2a02:1205:505c:2190:8972:54b2:2eb:db89]:8333 failed: Network is unreachable (101) 2017-09-27 19:05:46 receive version message: /Satoshi:0.14.1/: version 70015, blocks=487223, us=174.71.159.134:37164, peer=25 2017-09-27 19:14:49 receive version message: /Satoshi:0.14.1/: version 70015, blocks=487223, us=35.164.37.18:8333, peer=26 2017-09-27 19:15:30 connect() to [2400:2413:c140:2200:1013:d724:ab9b:76b9]:8333 failed: Network is unreachable (101) 2017-09-27 19:15:55 connect() to [2003:ca:a3e4:7600:66:b8d7:17b1:9e35]:8333 failed: Network is unreachable (101) 2017-09-27 19:19:32 connect() to [2001:0:9d38:6ab8:2414:763:d143:ed98]:8333 failed: Network is unreachable (101) 2017-09-27 19:29:29 connect() to 180.164.43.124:8333 failed after select(): Connection refused (111) 2017-09-27 19:29:53 connect() to 185.16.85.56:8333 failed after select(): Connection refused (111) 2017-09-27 19:45:09 connect() to [2601:681:4e00:eff6:8530:c749:e12d:8040]:8333 failed: Network is unreachable (101) 2017-09-27 19:49:13 connect() to 170.254.171.172:8333 failed after select(): Connection refused (111) 2017-09-27 19:57:05 connect() to 109.252.91.43:8333 failed after select(): Connection refused (111) 2017-09-27 20:06:14 connect() to [2003:75:2e17:b642:1948:f863:827d:af9e]:8333 failed: Network is unreachable (101) 2017-09-27 20:09:54 connect() to [2a01:e35:8b4c:8490:978:9281:1dd1:2e07]:8333 failed: Network is unreachable (101) 2017-09-27 20:12:29 connect() to [2605:a601:4170:e000:cce2:6423:6eff:47ae]:8333 failed: Network is unreachable (101) 2017-09-27 20:16:55 connect() to 109.69.8.115:8333 failed after select(): Connection refused (111) 2017-09-27 20:17:00 connect() to [2001:0:9d38:78cf:30ce:18ac:ab50:89ec]:8333 failed: Network is unreachable (101) 2017-09-27 20:19:08 connect() to [2003:73:8f3c:fe00:806:874f:4e91:b3bd]:8333 failed: Network is unreachable (101) 2017-09-27 20:24:24 connect() to [2003:c8:83ca:4d00:c93e:ecd3:c7ca:aecf]:8333 failed: Network is unreachable (101) 2017-09-27 20:27:16 connect() to [2605:a601:a91:e00:b961:fc22:3bfd:65b7]:8333 failed: Network is unreachable (101) |