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

Got error on slicing blogs.log with eosio-blocklog #179

Open
zhopen opened this issue Jul 13, 2020 · 0 comments
Open

Got error on slicing blogs.log with eosio-blocklog #179

zhopen opened this issue Jul 13, 2020 · 0 comments

Comments

@zhopen
Copy link

zhopen commented Jul 13, 2020

Docker image is boscore/bos:v3.0.4
Got error on slicing blogs.log with eosio-blocklog.
But after stopping and starting nodeos, run normally。

root@test-inspur56:/eos/data-dir# eosio-blocklog -o block1-100.log --last 100
info  2020-07-13T11:33:28.703 thread-0  block_log.cpp:134             open                 ] Log is nonempty
info  2020-07-13T11:33:28.703 thread-0  block_log.cpp:165             open                 ] Index is nonempty
info  2020-07-13T11:33:28.703 thread-0  main.cpp:47                   read_log             ] existing block log contains block num 1 through block num 34019400
error 2020-07-13T11:33:28.703 thread-0  main.cpp:64                   read_log             ] database dirty flag set (likely due to unclean shutdown): only block_log blocks are available
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant