Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

block_log::open faults if log has no head #6348

Closed
tbfleming opened this issue Nov 19, 2018 · 3 comments
Closed

block_log::open faults if log has no head #6348

tbfleming opened this issue Nov 19, 2018 · 3 comments
Labels

Comments

@tbfleming
Copy link
Contributor

  • Replay and truncate mainnet block log. Other block logs might also work.
    • rm -rf data config
    • mkdir -p data/blocks
    • cp ...../blocks.log data/blocks
    • ~/eos/build/programs/nodeos/nodeos -d ./data --config-dir ./config --plugin eosio::http_plugin --plugin eosio::producer_api_plugin --hard-replay-blockchain --truncate-at-block 1000
  • Generate snapshot:
    • curl http://127.0.0.1:8888/v1/producer/create_snapshot | json_pp
  • Stop nodeos
  • Replay from snapshot without block log. Change id below:
    • rm -rf config data/blocks* data/state
    • ~/eos/build/programs/nodeos/nodeos -d ./data --config-dir ./config --snapshot data/snapshots/snapshot-000003e8ddc03486114e6a1c764f0f78dab559ed18519802b4399a8d89e48264.bin
  • Stop nodeos
  • Restart nodeos
    • ~/eos/build/programs/nodeos/nodeos -d ./data --config-dir ./config
@tbfleming tbfleming added the bug label Nov 19, 2018
@ramtej
Copy link

ramtej commented Jan 14, 2019

Same issue here. An idea when it will be possible to do a complete offline restore from a snapshot WITHOUT the need to get 1+ block from the network?

@heifner
Copy link
Contributor

heifner commented Apr 23, 2019

@tbfleming is this fixed by: #7188 ?

@tbfleming
Copy link
Contributor Author

yes

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants