Eos: cleos get accounts gets error "Account History API plugin is not enabled"

Created on 9 May 2018  路  5Comments  路  Source: EOSIO/eos

"cleos get accounts" returns error "Error 3110003: Missing Account History API Plugin".

config.ini has history_plugin and history_api_plugin enabled. Attached test will reproduce issue
tests/nodeos_run_test.py -v --only-bios --dont-kill

https://app.zenhub.com/files/87335980/dbe4b2f1-f13d-4f36-bac7-a2230864ecee/download

Launcher patch for adding history_plugin:
+++ b/programs/eosio-launcher/main.cpp
@@ -1009,6 +1009,7 @@ launcher_def::write_config_file (tn_node_def &node) {
cfg << "plugin = eosio::mongo_db_plugin\n";
}
cfg << "plugin = eosio::chain_api_plugin\n"

  • << "plugin = eosio::history_plugin\n"
    << "plugin = eosio::history_api_plugin\n";
    cfg.close();
    }
bug slim

Most helpful comment

The current history plugin does not currently generate or populate a key-cache to answer the question "what accounts are controlled by my keys".

Is this something that will be integrated into the new history_plugin? This was a highly useful feature for users. Without that functionality users will have to know both their keypair and their account name to make use of their accounts, whereas before users could just import their private key and select from a list of accounts bound to it along with the permissions.

For genesis, users will have to search through the snapshot to find their own randomized name.

All 5 comments

Account History Plugin is the old and defunct plugin and has a distinct endpoint / different API from History Plugin.

The current history plugin does not currently generate or populate a key-cache to answer the question "what accounts are controlled by my keys".

The current history plugin does not currently generate or populate a key-cache to answer the question "what accounts are controlled by my keys".

Is this something that will be integrated into the new history_plugin? This was a highly useful feature for users. Without that functionality users will have to know both their keypair and their account name to make use of their accounts, whereas before users could just import their private key and select from a list of accounts bound to it along with the permissions.

For genesis, users will have to search through the snapshot to find their own randomized name.

Yes

Fixed in #3253

Was this page helpful?
0 / 5 - 0 ratings

Related issues

christola picture christola  路  3Comments

williamleecn picture williamleecn  路  3Comments

yashbhavsar007 picture yashbhavsar007  路  3Comments

Npizza picture Npizza  路  3Comments

ResponsiveWebApps picture ResponsiveWebApps  路  3Comments