Feathercoin 0.8.5 Client
-
I’ve found a bug in upgrading some clients. I haven’t found the cause.
It happens on Kubuntu 13.10 with a standard [guide] Virtualbox Linux compile and my PC, upgrade 0.6.4.4 or import a 0.6.4.4. backup.
My Wallet receive address and database field labels got mismatched after upgrade. 6i1B~ is my mining address and the label was blank before the upgrade, now say Bit-message the wrong label (See image 2.)
This is how it used to look - Mining n/a
(see image 3.)I couldn’t easily find a .DAT file generic viewer to see why there might be a field match…
When testing previous Beta versions of 0.8.5 I got the field mismatch but mined coins showed up, ok.
Notes
I didn’t compile it as Qt5 (see image 1)Both databases were Berkelay5.1
[attachment deleted by admin]
-
Wrapper, is that 64bit or 32bit Kubuntu?
So you get the same problem if you create a new 0.6.4.4 wallet to import?
I’m wondering if you get the same problem if you create a new wallet, import your private keys and then import that to 0.8.5. Perhaps your .dat file is unhappy.
I will setup a VM and try to recreate the problem, let me know if it is 32 or 64 bit.
-
[quote name=“Bushstar” post=“44175” timestamp=“1387011581”]
Wrapper, is that 64bit or 32bit Kubuntu?
So you get the same problem if you create a new 0.6.4.4 wallet to import?
I’m wondering if you get the same problem if you create a new wallet, import your private keys and then import that to 0.8.5. Perhaps your .dat file is unhappy.
I will setup a VM and try to recreate the problem, let me know if it is 32 or 64 bit.
[/quote]It is 64bit. I don’t have my 0.6.4.4 wallet as I thought my backups were the same and just upgraded it. I was doing a Virtualbox compile first, which was slow, so I just went ahead. Then the same happened in the VirtualBox test .
Previously, I think I was testing new installs not upgrades, done a lot, exact detail hazy.
I can reproduce small databases from my initial FTC wallet backup then send that to you, should make mode of failure obvious?. +Test Upgrade works on very old wallet backups?
Sorry for delay, just found “notify me of relpies” in “Attachments and other options”
-
[quote name=“wrapper0feather” post=“44051” timestamp=“1386985708”]
I’ve found a bug in upgrading some clients. I haven’t found the cause.It happens on Kubuntu 13.10 with a standard [guide] Virtualbox Linux compile and my PC, upgrade 0.6.4.4 or import a 0.6.4.4. backup.
[/quote]So, I installed VirtualBox on my Arch system and loaded up an install of Kubuntu 13.10, upgraded all the packages, and downloaded FTC-qt sources from git so I could try to recreate this issue. I’ve started to download all the dependencies, but I see that libdb4.8-dev and libdb4.8+±dev have no packages available on a default Kubuntu… could that be why you are getting db errors??
*EDIT*
Nevermind, I see libdb5.1+±dev has an install candidate. I’ll try with that, since you said you were using Bdb 5 anyway :) -
Brilliant, I’m going mad here thinking its just me. I’ve duplicated it many times but need a database viewer to see why the fields are out of sync, we can analyse my files if any one can suggest the tools I need…
P.S it still remotely be a glitch with keys, an extra key from a failed bare (test) install, might be knocking it (restored backup) out of sync…?? just my only last idea, it shouldn’t be, I tried to avoid doing that as I identified as something to specifically test, later.
Bare install then upgrade my “real install,” I just updated the client the first wallet it saw was my old wallet, so that should rule that out though…
Most of my tests, were in clones of a fresh install virtual box, 0.8.5 which the source and Qt folders were deleted, i.e: clone from github and recompile in Qt-creator. I did both for the upgrade test, straight to old wallet, replace bare install, with old wallet.
VirtualBox - Kubuntu 13.10 Feathercoin0.8.5Beta - Test compile guide.
[url=http://forum.feathercoin.com/index.php/topic,4566.0.html]http://forum.feathercoin.com/index.php/topic,4566.0.html[/url] -
Well, this experiment has shown at least two deps in the qt readme file need to be updated :)
the libdb5.1+±dev needs to replace libdb4.8+±dev on modern Ubuntu installs, and the dependency libminiupnpc-dev needs to be added if one is to compile it themselves. -
Yes, I was just going through that (cross checking the readme), then support and new members went mad.
I’m sure I researched the data base issue, It should be ok to be 5.1, you just couldn’t go back? to 4.8.
I haven’t been able to test the extracting keys, as I’ve never done that yet, more work…
-
Well, I can’t reproduce your situation, because everything went perfectly for my test.
I did use a 32bit install of Kubuntu 13.10 on VirtualBox, however, and I did not try cloning the vdi as you did. I just built 0.6.4.4 from the git repo with QT Creator using DB 5.1 as we discussed, downloaded the blockchain (took forever!), and sent a few transactions from and to my main wallet. Then I downloaded the 0.8.5 from git and built that with QT Creator as well. The DB reindex just finished and I see the correct labels on the two transactions made.
I dunno? -
[quote name=“wrapper0feather” post=“44442” timestamp=“1387061633”]
Yes, I was just going through that (cross checking the readme), then support and new members went mad.I’m sure I researched the data base issue, It should be ok to be 5.1, you just couldn’t go back? to 4.8.
I haven’t been able to test the extracting keys, as I’ve never done that yet, more work…
[/quote]
I’ve extracted the private keys from my 0.8.5.0 Wallet and imported on another VM without problems.
Didn’t try to export on 0.6.4.4 and import on 0.8.5.0 -
[quote name=“Wellenreiter” post=“44521” timestamp=“1387094490”]
[quote author=wrapper0feather link=topic=4885.msg44442#msg44442 date=1387061633]
Yes, I was just going through that (cross checking the readme), then support and new members went mad.I’m sure I researched the data base issue, It should be ok to be 5.1, you just couldn’t go back? to 4.8.
I haven’t been able to test the extracting keys, as I’ve never done that yet, more work…
[/quote]
I’ve extracted the private keys from my 0.8.5.0 Wallet and imported on another VM without problems.
Didn’t try to export on 0.6.4.4 and import on 0.8.5.0
[/quote]That’s good news. If we never have to get out that python hank and I wrote to convert broken WIF keys again to make importing work, it’ll be too soon.
-
Wrapper, I am unable to recreate the problem on Kubuntu. I tested a heavily used 0.6.4.4 wallet and dropped it into the Feathercoin datadir and ran 0.8.5. Everything has come across without error.
I am wondering if your wallet.dat is corrupt.
Let’s do “wallet surgery”. We will dump your private keys and import them back into a 0.6.4.4 wallet to try the test over again.
Go to the console in the Qt client and do the following.
If you’ve encrypted your wallet you’ll need to unlock it
[b]walletpassphrase [passphrase] 1000[/b]
Then enter in dumpprivkey and your public address. This will generate the private key for your public key, make a note of this key.
[b]dumpprivkey [feathercoin address][/b]
Once you have all the private keys exported close the client down, backup and remove your wallet.dat from the Feathercoin datadir. Run the program to generate a new wallet.dat and then run the following to import your private keys.
[b]importprivkey [feathercoin private key][/b]
The client will freeze a little while it rescans the blockchain. Once all keys have been imported you will have a brand new shiny wallet.dat file ready to import to 0.8.5. I hope it works this time round :)
-
Wellenreiter, I have tested your change to the QR dialogue box and have now pulled it into 0.8.5. Thanks for that :)
Hopefully Wrapper’s issue is just a local one.
[attachment deleted by admin]
-
Cheers for the info Peter.
I’m trying to get round to that (private key extraction), ASAP…
I need to learn how to do that anyway…
Did you find a Database viewer that works with the wallet.dat or blockchain database? (for support / help )
- I added a “Trying to go Backwards in wallet versions”… - “mode of failure” in Support Docs
-
I do not have any visualisers for wallet.dat or the blockchain. I know that people have tried making such things in the past for Bitcoin though I’m not sure how well they stack up.
Does anyone know of any good tools that could be ported to Feathercoin?
-
The password timer went out on my wallet private key extraction. Which is what Peter kindly told me error -4 means.
I’ve now done the main (key extraction), so that is a work around for update glitches… I’ll test import next…
Otherwise it’s working fine in my “sanity / breaking” tests. Once I get the keys extracted I’ll do another test compile / import.
Do we have a potential release date?
Tomorrow? So we can fix bugs, Before the potential - Christmas / holiday rush, or after?
-
I am happy with tomorrow. I will ask Wellenreiter to update the version on his Feathercoin Linux distro page.
-
Just finished the import of Private keys, it took 2 hours, 20 keys…
I suppose I could of sped it up, by just typing them all in and letting is scan once at the end? I needed my wallet working, so didn’t think/risk till after I finished.
I noticed after import keys, my descriptions were lost, there are no receive addresses…
I’m gonna have to import a wallet old style in Virtualbox and copy the descriptions back out to my wallet.
I’ll add a note to support FAQ, to get your “address descriptions” before the, “private key export / import”.
-
Latest versions for Linux are packaged and available at
[url=http://software.opensuse.org/package/feathercoin]http://software.opensuse.org/package/feathercoin[/url]
-
“cant open database file wallet.dat error” before several other errors and client crashing during block chain update, whats going on here?
i did copy my wallet.dat file into the roaming folder before opening the client, was this incorrect? am i supposed to create a new wallet with each new qt update?
EDIT:
problem is fixed however my client now crashes when i close, the error i get says…
"A fatal error occurered. Feathercoin can no longer continue safely and will quit.
EXCEPTION: St13runtime_error
CDB() : can’t open database file wallet.dat, error -30974
directory\feathercoin-qt.exe in Runaway exceptiondebug log:
opencon thread interrupt
addcon thread interrupt
dumpaddr thread stop
msghand thread interrupt
net thread interrupt
Shutdown : In progress…
Flush(false)
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended 0ms
StopNode()
Flushed 12626 addresses to peers.dat 38ms************************
EXCEPTION: St13runtime_error
CDB() : can’t open database file wallet.dat, error -30974
C:\Program Files (x86)\Feathercoin\feathercoin-qt.exe in Runaway exceptionEnvShutdown exception: DB_RUNRECOVERY: Fatal error, run database recovery (-30974)
-
qwertybo
Did you fix your upgrade?. Mode of failure 3 in support has instruction to copy out you private keys, in an emergency.Can you tell the forum some more details? what versions from where?
restore your 0.6.4.4 system, and wallet.dat. Export your receive addresses, export your private keys.
Re-name 0.8.5 wallet, restart to build a new wallet. Import your private keys.
With any database system there is a slight chance of corruption, especially during upgrade. Any further information you can glean may help others…
