Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block log was not setup properly with genesis information. #3545

Closed
Michael2008S opened this issue May 29, 2018 · 15 comments
Closed

Block log was not setup properly with genesis information. #3545

Michael2008S opened this issue May 29, 2018 · 15 comments
Assignees

Comments

@Michael2008S
Copy link

@Michael2008S Michael2008S commented May 29, 2018

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 <greg.lee@block.one>
Date:   Sun May 27 19:32:19 2018 -0400
@fulanto
Copy link

@fulanto fulanto commented May 29, 2018

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

Loading

@fulanto
Copy link

@fulanto fulanto commented May 29, 2018

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

Loading

@jhtsing
Copy link

@jhtsing jhtsing commented May 29, 2018

I have the same error.

Loading

@arhag arhag added this to the Version 1.1 milestone May 29, 2018
@wh2000292
Copy link

@wh2000292 wh2000292 commented May 30, 2018

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

Loading

@fulanto
Copy link

@fulanto fulanto commented May 30, 2018

@wh2000292 Any idea about ubuntu ?

Loading

@maheshnama
Copy link

@maheshnama maheshnama commented May 30, 2018

@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

Loading

@2efPer
Copy link

@2efPer 2efPer commented May 30, 2018

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

Loading

@stanishev
Copy link

@stanishev stanishev commented Jun 2, 2018

clear this folder as in remove the data folder altogether.

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

Loading

@ycryptx
Copy link

@ycryptx ycryptx commented Jun 4, 2018

@Michael2008S were you able to solve this?

Loading

@cs4026
Copy link

@cs4026 cs4026 commented Jun 4, 2018

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.

Loading

@Michael2008S
Copy link
Author

@Michael2008S Michael2008S commented Jun 5, 2018

@ycryptx yes.

Loading

@taokayan
Copy link
Contributor

@taokayan taokayan commented Jun 21, 2018

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

Loading

@wanderingbort wanderingbort removed this from the Version 1.1 milestone Jul 9, 2018
@wanderingbort wanderingbort added this to the Version 1.2 milestone Jul 9, 2018
@wanderingbort wanderingbort removed this from the Version 1.2 milestone Aug 14, 2018
@andriantolie
Copy link
Contributor

@andriantolie andriantolie commented Oct 30, 2018

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

Loading

@mosjin
Copy link

@mosjin mosjin commented Jun 5, 2019

@stanishev works for me. thanks!

Loading

@vikas-sawant-rwaltz
Copy link

@vikas-sawant-rwaltz vikas-sawant-rwaltz commented Mar 10, 2021

If you are using docker setup then run the nodeos without --hard-replay-blockchain at the start. It will work for you.

In my case I was trying docker nodeos setup with --hard-replay-blockchain, and when I removed it's start working.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet