How to use @abit's SHM fix for Steem-in-a-box (STEEM-DOCKER)
This article is intended for witnesses. It explains a fix laid out by another witness (@abit) applied to a different scenario (Steem-in-a-box), which is a method of running STEEM made by myself.
As docker is a little bit different to running it on the host machine, the fixes laid out in @abit's article are applied differently.
1. Stop your witness
./run.sh stop
2. Increase the SHM size on the host
mount -o remount,size=14G /dev/shm
3. Copy the existing shared memory file to /dev/shm
cp data/witness_node_data_dir/blockchain/shared_memory.* /dev/shm/
4. Set the shared directory in your config.ini file to /shm/
shared-file-dir = /shm/
5. Modify the run.sh file
Find and replace the following line:
docker run $DPORTS -v "$DATADIR":/steem -d --name $DOCKER_NAME -t steem
With this:
docker run $DPORTS -v /dev/shm/:/shm -v "$DATADIR":/steem -d --name $DOCKER_NAME -t steem
6. Delete your old witness container
docker rm {witness,witness_bak,seed}
7. Start the witness again
./run.sh start
Finally:
Check that your witness is functioning. You should see some of the the following messages when you run the logs:
./run.sh logs
...
116547ms th_a main.cpp:196 main ] Started witness node on a chain with 7808435 blocks.
...
675728ms th_a application.cpp:488 handle_block ] Got 2 transactions from network on block 7809007
This post has been ranked within the top 50 most undervalued posts in the second half of Dec 22. We estimate that this post is undervalued by $9.30 as compared to a scenario in which every voter had an equal say.
See the full rankings and details in The Daily Tribune: Dec 22 - Part II. You can also read about some of our methodology, data analysis and technical details in our initial post.
If you are the author and would prefer not to receive these comments, simply reply "Stop" to this comment.
Protip: use 4 tags until the 5=1 bug is resolved. Right now, you are only listed in witness-category. Thanks for your work. Peace.
Thanks!
I've removed the
steem-help
tag. Seems like a stupid buggood one, thanks :)