Open HarryMarch opened 4 years ago
Could you run verify:db it seems like you have to restart the sync, I have been running node on pruning and it works pretty well.
If that doesn't work try sync:db
Try deleting the state entry in db.collections.state.
Yes, that is also true, try removing the state, I think it should be automatically restarted once it's gone stale.
Try deleting the state entry in db.collections.state.
I deleted the entire of database, but nothing changed
I am facing same issue running prune mode ? can anyone help ?
We've had some recent changes to the p2p library, that could be related to the Connected, Not Connected issue. I'll check into this today
To answer the question about prune, bitcore-node can sync without txindex.
Our production node for api.bitcore.io is talking to a pruned btc node.
We've had some recent changes to the p2p library, that could be related to the Connected, Not Connected issue. I'll check into this today For me it was working fine with regtest but now as I am trying to connect with mainnet I am facing connect disconnect issues
To answer the question about prune, bitcore-node can sync without txindex.
Our production node for api.bitcore.io is talking to a pruned btc node.
Hi, which bitcore version is it?
Due to slow sync with mainnet from block 300,000, so I decided to run btc full node in the prune mode (and I need to turn off -txindex for prune mode), deleted all synced data in bitcore database (mongo) and started bitcore again. But something weird happened to
bitcore-node
server. The console log isAnd there was no synced data at all. So Can I run
bitcore-node
with prune mode?