2

When I tempt to start nodeos using this command:

nodeos --delete-all-blocks --genesis-json genesis.json --plugin eosio::chain_plugin --plugin eosio::http_plugin --plugin eosio::history_api_plugin --plugin eosio::chain_api_plugin

almost everything goes correct except for one line that I paid attention to recently. It says:

2018-11-01T00:17:03.006 thread-0 controller.cpp:1380 startup ] No head block in fork db, perhaps we need to replay

This line shows in red. I noticed there's an open issue on this exact error that at the end asked to write any further question to here. Any help?

Improve this question
3
  • Did you try a replay?
    – Marcel
    Commented Nov 1, 2018 at 19:36
  • I get the same error. Did you soved this error.
    – xiuyoung
    Commented Feb 19, 2019 at 9:29
  • @xiuyoung Nope :(
    – Said A. Sryheni
    Commented Mar 4, 2019 at 0:58

1 Answer 1

Reset to default
0

Append --hard-replay to replay

Improve this answer
3
  • Adding that doesn't do anything, everything (including the error) stays the same.
    – Said A. Sryheni
    Commented Nov 2, 2018 at 3:07
  • and --mongodb-wipe --hard-replay-blockchain ? Delete your nodeos 'state' folder as well, if that doesn't work, delete also your blocks folder. You can find the state folder using $ sudo find / -name state
    – Marcel
    Commented Nov 3, 2018 at 14:34
  • I added --mongodb-wipe --hard-replay-blockchain, deleted state and blocks folder, but the error still pops up. The server starts anyways, but I'm not sure how much does this error affects the server later.
    – Said A. Sryheni
    Commented Nov 5, 2018 at 23:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.