Eos: Faild to execute action eosio::init in eos v1.8.1

Created on 1 Aug 2019 · 2Comments · Source: EOSIO/eos

I am setuping a new genesis node directly with eos v1.8.1 , instead upgrade from lower version.
when I do action below, get a error.
it is sure that contract(eosio.token, eosio.system) has been deployed to account(eosio.token, eosio).
What could I do wrong.

$cleos set contract eosio /eos/contracts/v1.7.0-cdt1.6.2/eosio.system -p eosio@active
Reading WASM from /eos/contracts/v1.7.0-cdt1.6.2/eosio.system/eosio.system.wasm...
Publishing contract...
executed transaction: 77e24d886218909312a9082269cbe41a65b1eba12369b510c7c0a4312d927ed5  76376 bytes  33370 us
#         eosio <= eosio::setcode               {"account":"eosio","vmtype":0,"vmversion":0,"code":"0061736d01000000019c033b60000060047f7f7f7f006004...
#         eosio <= eosio::setabi                {"account":"eosio","abi":"0e656f73696f3a3a6162692f312e310053086162695f686173680002056f776e6572046e61...
warning: transaction executed locally, but may not be confirmed by the network yet         ] 


$cleos push action eosio init '[0,"4,SYS"]' -p eosio@active
Error 3050003: eosio_assert_message assertion failure
Error Details:
assertion failure with message: owner account does not exist
pending console output:

Source