Topic: Synchronizing with network... - page 3. (Read 4418 times)
screw it... re-downloading the chain...
Running from the command line and passing -rescan might work.
If not, you can download a latest set of the block*.dat files and use the -reindex command line option.
Typically, one of those fixes it for me. I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it If not, you can download a latest set of the block*.dat files and use the -reindex command line option.
Typically, one of those fixes it for me. I go in that order, because the first might work without requiring downloading of anything.
delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
Running from the command line and passing -rescan might work.
If not, you can download a latest set of the block*.dat files and use the -reindex command line option.
Typically, one of those fixes it for me. I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it If not, you can download a latest set of the block*.dat files and use the -reindex command line option.
Typically, one of those fixes it for me. I go in that order, because the first might work without requiring downloading of anything.
Running from the command line and passing -rescan might work.
If not, you can download a latest set of the block*.dat files and use the -reindex command line option.
Typically, one of those fixes it for me. I go in that order, because the first might work without requiring downloading of anything.
If not, you can download a latest set of the block*.dat files and use the -reindex command line option.
Typically, one of those fixes it for me. I go in that order, because the first might work without requiring downloading of anything.
Best and fastest solution gets a reward. can deliver reward to USA Only.
can some plz tell me why this happens (gets stuck):
how do I resolve this QUICKLY, without re-downloading the whole block chain again?
This happens often enough to really be an annoyance... I have to grab the wallet and open it on another workstation while re-downloading the blockchain on the effected system...
it's the latest qt wallet.
how do I resolve this QUICKLY, without re-downloading the whole block chain again?
This happens often enough to really be an annoyance... I have to grab the wallet and open it on another workstation while re-downloading the blockchain on the effected system...
it's the latest qt wallet.
Jump to: