\[solved\] FTC Wallet strangeness... \* Old client version
-
Hello :-)
I have a quick question concerning my feathercoin wallet.
There seems to be a problem… here are the symptoms:=> starts up normally, ‘out of sync’ … and begins to do the usual
Synchronizing with the network… updating it’s local copy of the blockchain=> However the block count doesn’t decrease towards zero.
The block count is getting bigger …and bigger… as if it’s eating the
blockchain and becoming more and more out of date.
(And it seems to do this very slowly).Here are some of the numbers
~12741 blocks remaining.
then later
~25483 blocks remaining.
then 2 minutes later
~25384 blocks remaining.
then 2 minutes later
~25385 blocks remaining.
and so on…All in all…it doesn’t look like the behaviour of a healthy wallet.
I presume that the blockchain is corrupt and the wallet is
running some routine to get back to the most recent valid
block … so it can rebuild it from there. (i’m guessing)
So … will this problem fix itself ?
Or … should i delete the blockchain and let the wallet rebuild it from scratch ?
(if so, where is it normally stored ?)The version of the wallet i’m using is: 0.6.4.3
I have a linux build, on ubuntu. 12.4Thanks to anyone that offers any suggestions or remedies.
catholic :-)
-
get version 6.4.4
that’s the one you need to have
also seems to sometimes connect to litecoin node
-
I just posted about the same problem in the noob section of the forum. Everything was fine until I upgraded to the lastest client. After that it gave me errors that the my copy of the blockchain was bad. I deleted the client/blockchain and downloaded everything again. After that the client worked fine for a couple of days, but stopped syncing again about 3-4 days ago. This time around I don’t have any corruption errors, but the block count that I am behind keeps increasing. None of my other currency wallets have had any trouble. I’m not sure what to do other than delete everything and reinstall a second time.
Chad
-
Update version to 6.4.4
-
I’m on the latest client and it still refuses to sync past some time a little over a week ago. I’ve had the client open with 8+ connections for three days now and the block count it is behind continues to increase. Any ideas what is going on here? Everything else is working fine.
Chad
-
I have heard a couple of people with similar errors one option is just to restart the client if it freezes like this.
Another is to use the rescan option via the command screen but I have never done this myself.