Block log was not setup properly with genesis information. #3545
Comments
master is not stable, may be you should try released version |
well, I have tried dawn-v4.2.0, however, same error. |
I have the same error. |
I use macos. clear folder ~/Library/Application Support/eosio/data can solve this problem |
@wh2000292 Any idea about ubuntu ? |
@wh2000292 Any idea about ubuntu ? In Ubuntu16.04 delete this folder |
clear this folder |
clear this folder as in remove the data folder altogether. rm -rf ~/.local/share/eosio/nodeos/data |
@Michael2008S were you able to solve this? |
Same issue on macOS, solved it by cd-ing into ~/Library/Application Support/, 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. |
@ycryptx yes. |
Please use the latest version and clean up the old block log and shared mem. |
Yes, just use the latest version. I suspect there's a hardfork change at that time that is incompatible with your previous block log |
@stanishev works for me. thanks! |
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. |
I get this error when I run
./nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin
.In this version:
The text was updated successfully, but these errors were encountered: