Eos: Block log was not setup properly with genesis information.

[Michael2008S]

I get this error when I run ./nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin.

➜  nodeos git:(master) ./nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin
1875208ms thread-0   chain_plugin.cpp:151          plugin_initialize    ] initializing chain plugin
1875209ms thread-0   main.cpp:113                  main                 ] 10 assert_exception: Assert Exception
version > 0: Block log was not setup properly with genesis information.
    {}
    thread-0  block_log.cpp:470 extract_genesis_state

In this version:

commit 07a6798584d053ed6061bd892879c6c886ba104e
Merge: a609496 3588c5c
Author: Greg Lee <[email protected]>
Date:   Sun May 27 19:32:19 2018 -0400

[fulanto]

master is not stable, may be you should try released version

[fulanto]

well, I have tried dawn-v4.2.0, however, same error.

[jhtsing]

I have the same error.

[wh2000292]

I use macos. clear folder ~/Library/Application Support/eosio/data can solve this problem

[fulanto]

@wh2000292 Any idea about ubuntu ?

[maheshnama]

@wh2000292 Any idea about ubuntu ? In Ubuntu16.04 delete this folder
/root/.local/share/eosio/nodeos/data ,start this command it should work
nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin

[2efPer]

clear this folder
Mac OS: ~/Library/Application Support/eosio/nodeos/data
Linux: ~/.local/share/eosio/nodeos/data

[stanishev]

clear this folder as in remove the data folder altogether.

rm -rf ~/.local/share/eosio/nodeos/data

[ycryptx]

@Michael2008S were you able to solve this?

[cs4026]

Same issue on macOS, solved it by cd-ing into ~/Library/Application Support/,
and running "rm -rf eosio".

This deleted everything related to the chain. Running nodeos after this reset my eosio folder with a fresh config.ini.

I updated the config.ini and ran "nodeos --delete-all-blocks ", waited for it to clear pressed "ctrl-c" and ran nodeos again and it's working fine now.

[Michael2008S]

@ycryptx yes.

[taokayan]

Please use the latest version and clean up the old block log and shared mem.

[andriantolie]

Yes, just use the latest version. I suspect there's a hardfork change at that time that is incompatible with your previous block log

[mosjin]

@stanishev works for me. thanks!