BitShares Forum
Main => Technical Support => Topic started by: pollux on May 04, 2015, 02:59:21 pm
-
Wallet fails to load on OSX, the only meaningful message I can find in the logs are 20 instances of:
2015-05-04T14:48:35 bitshares:? load_generic_record ] Unknown wallet record type: 6 wallet_db.cpp:63
Completely locked out of my funds. Haven't done anything but upgrade versions and occasionally deleting the chain directory due to forks and crashes.
-
You can try reimport from a backup. They are located in "wallets/.backups" in the config folder (see http://wiki.bitshares.org/index.php/BitShares/Config)
-
Wallet fails to load on OSX, the only meaningful message I can find in the logs are 20 instances of:
2015-05-04T14:48:35 bitshares:? load_generic_record ] Unknown wallet record type: 6 wallet_db.cpp:63
Completely locked out of my funds. Haven't done anything but upgrade versions and occasionally deleting the chain directory due to forks and crashes.
That line in the log is just a warning and shouldn't be causing any failure.
When you say the wallet fails to load, how does it fail?
-
Vikram, it does go through the "startup" steps in the GUI, shows some status, then prompts for password.
I can generate the following error in p2p.log by entering my password in that screen (which doesn't change after submitting):
2015-05-04T18:00:03 th_a:?unnamed? log_message ] Message from GUI: rpc error: Assert Exception (10)
account.owner_key != public_key_type():
(500)
getStackTrace@app.js:35:5176
○ request@app.js:41:12198
○ open@app.js:41:48264
○ submitForm@app.js:37:46041
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253 Utilities.cpp:36
-
bump.
Still locked out of funds.
-
Still locked out of my funds.
-
You can try reimport from a backup. They are located in "wallets/.backups" in the config folder (see http://wiki.bitshares.org/index.php/BitShares/Config)
-
You can try reimport from a backup. They are located in "wallets/.backups" in the config folder (see http://wiki.bitshares.org/index.php/BitShares/Config)
Yes, can you try importing the most recent backup you can find and see if anything changes?
-
(http://i.imgur.com/32XOmTI.png)
-
The good news is that I was able to hack the wallet json file to remove an entry and re-import it... successfully!
The bad news is that I have no idea whether the thing I removed was bad to remove. I don't appear to have lost funds (after re-scanning).
I removed this:
{
"type": "key_record_type",
"data": {
"index": 11,
"account_address": "BTSX[...]",
"public_key": "BTSX1111111111[...]",
"encrypted_private_key": "[...]",
"memo": null
}
},
If the exact data is important, please let me know and I'll pass it along in a less public way.
-
Does that public key really consist of mostly 1's? That looks suspiciously like a null key. If it is, you haven't removed anything of importance.
-
There were quite a few more 1s in the key (though not all 1s), to the point where I figured that if I did in fact have funds on it, I should probably find out.
In any case, I'd recommend that if a wallet contains something that fails to be parsed, it should not cause the software to silently fail to unlock but rather to quarantine any newly failing keys and continue. At the very least, it should identify the key in an error message.