CLI stuck at "Loading banlist..."

[proletesseract]

Running Gitian built 4.6.0 on Debian 9.

navcoin.conf

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=<my username>
rpcpassword=<my password>
uacomment=bitcore

I bootstrapped the blocks and chainstate folder from my local data directory on OSX running self build 4.7.0 with the same config as debian. Removing the data and chainstate folders and starting the daemon works as expected.

1. start the daemon ./navcoind &
2. query the cli ./navcoin-cli getinfo

after the Rewinding Blocks message, it moves onto Loading Banlist but this message never goes away.

error code: -28
error message:
Loading banlist...

The logs show that it is actually past that and syncing, but the CLI get stuck at that message.

removing the banlist.dat and trying to get the wallet to recreate it results in the same series of events.

debug.log file:

2019-07-16 20:08:09 init message: Rewinding blocks...
2019-07-16 20:08:20 init message: Verifying blocks...
2019-07-16 20:08:20 Verifying last 288 blocks at level 3
2019-07-16 20:08:20 [0%]...[10%]...[20%]...[30%]...[40%]...[50%]...[60%]...[70%]...[80%]...[90%]...[DONE].
2019-07-16 20:08:21 No coin database inconsistencies in last 289 blocks (581 transactions)
2019-07-16 20:08:21  block index           38904ms
2019-07-16 20:08:21 init message: Loading wallet...
2019-07-16 20:08:21 nFileVersion = 4060000
2019-07-16 20:08:21 Keys: 103 plaintext, 0 encrypted, 103 w/ metadata, 103 total
2019-07-16 20:08:21  wallet                   92ms
2019-07-16 20:08:21 mapBlockIndex.size() = 3305420
2019-07-16 20:08:21 nBestHeight = 3275996
2019-07-16 20:08:21 setKeyPool.size() = 101
2019-07-16 20:08:21 mapWallet.size() = 0
2019-07-16 20:08:21 mapAddressBook.size() = 1
2019-07-16 20:08:21 init message: Loading addresses...
2019-07-16 20:08:21 Loaded 0 addresses from peers.dat  1ms
2019-07-16 20:08:21 init message: Loading banlist...
2019-07-16 20:08:21 torcontrol thread start
2019-07-16 20:08:21 UpdateTip: new best=0f02d8c8463f947981f3aa8036e479fac3d5fe546bef0a02cff36aa7fc229bd5 height=3275997 version=0x7131e1ff log2_work=73.028621 tx=6845968 date='2019-07-05 18:46:56' progress=0.973029 cache=0.0MiB(3tx)

and the block sync continues in the logs after this.

[mxaddict]

I'm guessing this is not related to #569

[proletesseract]

not as far as i can tell.

[mxaddict]

Closing as I can't replicate this issue anymore.