Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

cleos get info error #3976

Closed
blocksbarcelona opened this issue Jun 9, 2018 · 7 comments
Closed

cleos get info error #3976

blocksbarcelona opened this issue Jun 9, 2018 · 7 comments

Comments

@blocksbarcelona
Copy link

blocksbarcelona commented Jun 9, 2018

Version v1.0.2 - node: eosbarcelona on Jungle tesnet

Installed new node. Account created. Connected to Jungle. Staked eos. Everything works but get account

./cleos.sh get account eosbarcelona
3345141ms thread-0   main.cpp:2659                 main                 ] Failed with error: unspecified (0)
unknown key

cleos.sh

CLEOS=/home/eos/eos-source/build/programs/cleos/cleos
$CLEOS -u http://127.0.0.1:8888 --wallet-url http://127.0.0.1:55553 "$@"
@vivekmarakana
Copy link

+1

@bt-cryptomancer
Copy link

bt-cryptomancer commented Jun 9, 2018

confirmed this error is not specific to Jungle testnet. Upgraded my node to https://github.com/EOS-Mainnet/eos/tree/launch-rc-1.0.2 on the 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5 chain (BIOS Boot) and got same error:

./cleos.sh get account ge3tegenesis
54336ms thread-0 main.cpp:2659 main ] Failed with error: Assert Exception (10)
itr != structs.end(): Unknown struct self_delegated_bandwidth

Interestingly no problem if you lookup the account by public key instead:

./cleos.sh get accounts EOS6WdawGE1Cega9sCW97WBjE4YgeggWWf5RsqrSVR5QY8A7cp8T3
{
"account_names": [
"ge3tegenesis"
]
}

Info about my node:

{"server_version":"1c560d2f","chain_id":"579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5","head_block_num":578429,"last_irreversible_block_num":578428,"last_irreversible_block_id":"0008d37c059304a301dc4e4307625895392f866cd4435c4c09cb909f8c49a0db","head_block_id":"0008d37d75a74c2e96dc2defa2ad632648732b78b1bd0f3b5d814d0e3095194b","head_block_time":"2018-06-08T22:52:12","head_block_producer":"eosio","virtual_block_cpu_limit":200000000,"virtual_block_net_limit":1048576000,"block_cpu_limit":199900,"block_net_limit":1048576}

@Heejaejoo
Copy link

From what I investigated from eosio code, I found this is a bug related to the recent change.
According to line 1003~1042 of chain_plugin.cpp, cleos initializes abi_serializer( abi_serializer abis( abi ))
) with a contract from eosio account, which definitely should be the eosio.system contract.
Then, cleos loads self_delegated_bandwidth struct from the abi(eosio.system) in line 242 of abi_serializer.cpp, which has no struct named self_delegated_bandwidth and causes the error.

@JohnnyZhao
Copy link

same here, is there fix on the way?

@livc
Copy link

livc commented Jun 12, 2018

same here...

1 similar comment
@realSinged
Copy link

same here...

@wanderingbort
Copy link
Contributor

this seems to be resolved by 843ed64

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants