Sync stops at some point for mainnet and testnet

[jooray]

I tried to start spruned several times, both on mainnet and testnet (I added some testnet servers, see the patch). But in both cases the blockchain gets stuck at some pretty low block number and does not proceed any further.

2019-07-15 09:52:46,242 - p2p - INFO - Bootstrap: saved block 00000000000000000013f868046353ee20bf51f61dbd11e8966c472d26740417 (496/500)
2019-07-15 09:52:46,705 - p2p - INFO - Bootstrap: saved block 0000000000000000000604275f91b1ea6351ec467c1c65ad62cd63c1fa34ffa3 (497/500)
2019-07-15 09:52:47,538 - p2p - INFO - Bootstrap: saved block 000000000000000000061042ff5f41d53c9035425a2734545af414fa14c4b9ec (498/500)
2019-07-15 09:52:47,883 - p2p - INFO - Bootstrap: saved block 0000000000000000001e34763d1e50570e4202da499566c6cbffb7959997f382 (499/500)
2019-07-15 09:52:57,227 - p2p - INFO - Bootstrap: saved block 00000000000000000000f596e6aa72ad89217df0ecb0e6ee3c55e75c71b172fa (500/500)
2019-07-15 09:52:57,530 - p2p - INFO - Bootstrap: No blocks to fetch.
2019-07-15 09:53:05,221 - p2p - INFO - Connected to peer 92.117.63.177:8333 (Satoshi:0.17.1)
2019-07-15 09:53:05,570 - p2p - INFO - Connected to peer 47.75.218.1:8333 (Satoshi:0.16.3)
2019-07-15 09:56:15,456 - p2p - INFO - Connected to peer 66.216.225.64:8333 (Satoshi:0.18.0)
2019-07-15 09:56:18,352 - spruned.dependencies.connectrum - DEBUG - Error response: '{'code': 1, 'message': 'height 585,500 out of range'}'

2019-07-15 09:59:02,161 - cache - INFO - Cache is ok, size: 0, limit: 2048000000

{
  "chain": "main",
  "warning": "spruned 0.0.10, emulating bitcoind v0.16",
  "blocks": 585499,
  "headers": 585499,
  "bestblockhash": "00000000000000000001bcf2c0b1eeb0aa808a3c34176e22e70ec4b2b64265aa",
  "difficulty": 0,
  "chainwork": "0000000000000000000000000000000000000000000000000000000000000000",
  "mediantime": 1563183918,
  "verificationprogress": 100,
  "pruned": false
}

Is there a way to tell spruned to try to fetch newer block or somehow force resync?

[gdassori]

It could be related to some nodes that doesn't respond to segwit blocks requests.
Good news is that it is reproducible.
Bad is I don't have enough time to debug it yet: the whole development is a bit stalled atm.

[gdassori]

Ok, let's fix this s***.

[gdassori]

#112