[SOLVED] BitUSD stuck in limbo

Started by Method-X, September 03, 2014, 04:57:27 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

tonyk

It was using 25% of my processor when I last ran one of those commands.
Which version are you on btw. You can try (at your risk the 0.4.11-RC2), the 32bit windows version is pretty stable in my opinion. And works batter than anything from before it. Including reducing/eliminating such 'lost' funds/accounts in the furure.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Method-X

Ok it did something!

Says this:  Transaction scanning progress is -100%

Negative 100 percent?
[url="https://edabit.com"]https://edabit.com[/url]

tonyk

I do not know then. It takes mine about one hour. And I use 42 not 100 for obvious reasons. Did you give it enough time to calculate?
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Method-X

Quote from: tonyk on September 04, 2014, 02:31:09 AM
wallet_recover_accounts 100

>> wallet_recover_accounts 100

0


It's just outputting null.  ???
[url="https://edabit.com"]https://edabit.com[/url]

tonyk

Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Method-X

@Riverhead

Thanks for the help!

Do I input this into the console exactly:

wallet_recover_accounts methodx

What do I input for number of attempts?
[url="https://edabit.com"]https://edabit.com[/url]

Riverhead

Have you tried this?



wallet_recover_accounts


Usage:
wallet_recover_accounts <accounts_to_recover> [maximum_number_of_attempts]                            Attempts to recover accounts created after last backup was taken and returns number of successful recoveries. Use if you have restored from backup and are missing accounts.
Attempts to recover accounts created after last backup was taken and returns number of successful recoveries. Use if you have restored from backup and are missing accounts.


Parameters:
  accounts_to_recover (int32_t, required): The number of accounts to attept to recover
  maximum_number_of_attempts (int32_t, optional, defaults to 1000): The maximum number of keys to generate trying to recover accounts


Returns:
  int32_t

Method-X

[url="https://edabit.com"]https://edabit.com[/url]

Method-X

>> wallet_account_vote_summary methodx

10 assert_exception: Assert Exception
oaccount_rec.valid():
    {}
    bitshares  wallet.cpp:5632 get_account_vote_summary

    {}
    bitshares  wallet.cpp:5661 get_account_vote_summary

    {}
    bitshares  common_api_client.cpp:1507 wallet_account_vote_summary

    {"command":"wallet_account_vote_summary"}
    bitshares  cli.cpp:481 execute_command
[url="https://edabit.com"]https://edabit.com[/url]

xeroc

Quote from: MeTHoDx on September 03, 2014, 07:17:29 PM
Should also note I'm getting this error when accessing my account:

RPC Server Error: In method 'wallet_account_vote_summary': Assert Exception (10)

could you run wallet_account_vote_summary in the console and give us the full output?

Method-X

Should also note I'm getting this error when accessing my account:

RPC Server Error: In method 'wallet_account_vote_summary': Assert Exception (10)
[url="https://edabit.com"]https://edabit.com[/url]

Method-X

#1


Under the edit tab in my account, it looks like I've got 100 USD trapped in limbo. What do?

SOLVED!

I imported the very first backup I created. I first attempted restoring my latest backup but that resulted in all the same errors with voting and transaction scanning. It would appear this is an issue with the way backups were / are made.

Once the blockchain was synced, I input the following into the console:

wallet_regenerate_keys methodx 1000

All keys were regenerated and within 10 minutes of the scan, I had access to all funds again.

Finally I can start playing the markets! :D
[url="https://edabit.com"]https://edabit.com[/url]