I am running an Ubuntu on VMWare on my windows 10 workstation which is i7, with 1TB HD and 16GB RAM. I set Ubuntu to have 8GB RAM and setup an 8GB swap file as well.
The farthest distance I've reached on the blockchain replay was at 34% .
You are viewing a single comment's thread from:
Well I have a less powerful i5-2550k, and my tests on my VM can compile with 8gb physical RAM. I don't get why you have issues. I would stay start all over? Try from scratch again, I have no clue :\ sorry
Thanks for the response @krnel. I have started from scratch again. And with minimal config file, I reach 94% on the blockchain replay. That's after about 38 hours. But then power went out on our area and I had to start from scratch again.
Does steemd really to start reindexing blocks from scratch all over again after a power interruption? I am wondering if there's way to run steemd to resume replay from where it stops before the power interruption?
Any help will be appreciated.
The replay starts all over.
Thanks for the confirmation @krnel. Even if we gracefully exit a running steemd replay, the next time we run steemd again, it will still start all over, correct?
Yup...
38.0168% 5200000 of 13678146 (27367M free)
38.7479% 5300000 of 13678146 (27349M free)
I did ctrl+c to copy, but in my screen on my putty connection and killed the restart of my witness lol. Gotta start all over now. It's a bummer indeed.
So it is also taking days for you to get the replay complete? I think I am almost done with the replay when I get past 60%. However, when I reached the 94% mark, it get stuck again. I have recorded the timings and found out that it took almost 12 hours to move from 12700000 to 12800000. And it's already 10 hours and it has not get past 12800000.
My only question is that if it's normal even if you have minimal config.ini settings as posted by @jesta on this comment which others confirmed to be a great help on their end.
It doesn't take that long for me. Did you grab the block_log from dl or sync yourself? gtg's block_log from the link in this guide has been corrupted it seems:
https://github.com/steemit/steem/issues/1255
I've been resyncing the normal way and it's on day 3 now:
1738492ms th_a application.cpp:484 handle_block ] Syncing Blockchain --- Got block: #12190000 time: 2017-05-23T20:37:21