Cancel it and increase either your physical RAM or your virtual RAM (swap). If you don't have at least 6-8GB total with both combined, then you might have issues compiling. I learned that later on ;) Give yourself 8GB of swap and it will work after, I'm pretty sure ;) GL
You are viewing a single comment's thread from:
I get past that now after adding 8GB of swap and another 8GB of RAM for the ubuntu setup on VMWare. Thanks a lot! However, I am stuck at about 33% for many hours now when doing --replay-blockchain.
I already restarted my machine once after being stuck there for the first yesterday. How long normally does this procedure completes?
You got the blockchain data downloaded, the config setup, and then it should run it's course. It can take many hours, 12h, depends. Stuck at 33%, I would say retry if you can't get past it.
Looks like I get past 33% after a number of hours. It's now at 34% -- 4600000 of 13492873. The first 30% is faster. Is it normal for the rest of the percentages to be this slower?
What about CPU? Maybe that's the problem?
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% .
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.