Bitcoin ABC stucked on 530361 block

[Uniex]

I have upgraded my Bitcoin ABC daemon to 0.17.2 version and got stuck on block 530361

In debug.log

2018-06-13 18:00:54 connect() to 222.86.198.242:8333 failed after select(): Connection refused (111)
2018-06-13 18:01:07 receive version message: [[2604:a880:400:d0::5c1:6001]:8333] /Bitcoin ABC:0.17.1(EB32.0)/: version 70015, blocks=534530, us=[2a01:4f8:211:2914::2]:48890, peer=10
2018-06-13 18:01:16 connect() to 31.10.28.224:8333 failed after select(): No route to host (113)
2018-06-13 18:01:35 connect() to 114.218.100.135:8333 failed after select(): Connection refused (111)
2018-06-13 18:01:46 receive version message: [47.93.123.193:8333] /Bitcoin ABC:0.17.1(EB32.0)/: version 70015, blocks=534530, us=136.243.15.148:53640, peer=12
2018-06-13 18:01:53 connect() to 159.65.5.161:8333 failed after select(): Connection refused (111)
2018-06-13 18:02:02 connect() to 174.94.73.166:8333 failed after select(): Connection refused (111)
2018-06-13 18:02:03 connect() to 121.236.133.101:8333 failed after select(): Connection refused (111)
2018-06-13 18:02:42 receive version message: [101.132.26.64:8333] /Bitcoin ABC:0.17.1(EB32.0)/: version 70015, blocks=534530, us=136.243.15.148:34920, peer=14
2018-06-13 18:04:14 connect() to [2001:8003:54fa:a700:d9:efe0:6702:c27d]:8333 failed after select(): Connection refused (111)

Any ideas ?

[1715556189]

1715556189

[1715556189]

1715556189

[1715556189]

1715556189

[jackg]

Maybe an antivirus or firewall is blocking it. Do you have any of these? If so manually configure it to allow connections to be recieved by whitelisting the application.

[hopebit]

I have upgraded my Bitcoin ABC daemon to 0.17.2 version and got stuck on block 530361

Any ideas ?

Me too. I was running Bitcoin ABC 0.16.1 and it got stuck on block 530361 (same on two different installations).
I've read somewhere that the network protocol changed after block 530361.
Then I downloaded the latest 17.3.0  but it still doesn't work.

However I'd need to keep 0.16.1 because - as to my knowledge - later versions don't work with Armory.

Anybody knows how to get it un-stuck from block 530361 ?

[Uniex]

I have upgraded my Bitcoin ABC daemon to 0.17.2 version and got stuck on block 530361

Any ideas ?

Me too. I was running Bitcoin ABC 0.16.1 and it got stuck on block 530361 (same on two different installations).
I've read somewhere that the network protocol changed after block 530361.
Then I downloaded the latest 17.3.0  but it still doesn't work.

However I'd need to keep 0.16.1 because - as to my knowledge - later versions don't work with Armory.

Anybody knows how to get it un-stuck from block 530361 ?

You should run command to reconsider block that was stuck. See here for details https://github.com/Bitcoin-ABC/bitcoin-abc/issues/213

[jackg]

I have upgraded my Bitcoin ABC daemon to 0.17.2 version and got stuck on block 530361

Any ideas ?

Me too. I was running Bitcoin ABC 0.16.1 and it got stuck on block 530361 (same on two different installations).
I've read somewhere that the network protocol changed after block 530361.
Then I downloaded the latest 17.3.0  but it still doesn't work.

However I'd need to keep 0.16.1 because - as to my knowledge - later versions don't work with Armory.

Anybody knows how to get it un-stuck from block 530361 ?

You should run command to reconsider block that was stuck. See here for details https://github.com/Bitcoin-ABC/bitcoin-abc/issues/213

I'd suggest you delete/rename the blocks and chainstate command just to see if that does anything.
I don't think it'll do much though as it looks like there is just a connection issue caused somewhere - but if you both have it maybe it will.