🚨Emergency🚨 Update for Steem-in-a-box (witnesses, seeds, and RPCs)

in #witness-category3 years ago (edited)

Attention all of you who operate a witness, seed, or RPC node

Earlier today, the network went offline due to a bug in 0.19.3. All witnesses are required to update to 0.19.5 immediately.

How to update my witness or seed?

As a lot of seeds may not be updated yet, it's highly recommended to add Steemit's own seeds to your config.ini

seed-node = seed-east.steemit.com:2001
seed-node = seed-central.steemit.com:2001
seed-node = seed-west.steemit.com:2001

Then, update using install

./run.sh install
./run.sh restart

Please be aware that there are mixed reports of replays being required. If you run into errors such as "Lock Timeout", which do not resolve themselves after running for 10-20 mins, please run the following to clear your shared memory and replay:

./run.sh stop
rm -rf /dev/shm/*
./run.sh replay

If you are running a full node (i.e. an RPC), use install_full instead of install.

If you continue to have issues, ask in #witness on https://steem.chat

GIF Avatar by @stellabelle

Do you like what I'm doing for STEEM/Steemit?

Vote for me to be a witness - every vote counts.

Don't forget to follow me for more like this.

Have you ever thought about being a witness yourself? Join the witness channel. We're happy to guide you! Join in shaping the STEEM economy.

Are you looking for a new server provider? My company @privex offers highly-reliable and affordable dedicated and virtual servers for STEEM, LTC, and BTC! Check out our website at https://www.privex.io


Thank you for this quick fix! Amazing as usual!

Thanks for the quick update @someguy123!

However, I was a bit startled of how to update steemd without docker, but @drakos shared these important lines:

cp -rpn ~/steem-docker/data/witness_node_data_dir/config.ini ~/steem-docker/data/witness_node_data_dir/config.ini.bak
sed -i ~/steem-docker/data/witness_node_data_dir/config.ini -r -e 's/required-participation = false/required-participation = 0/g'

echo -e "seed-node =\nseed-node = seed-east.steemit.com:2001\nseed-node = seed-central.steemit.com:2001\nseed-node = seed-west.steemit.com:2001\n$(cat ~/steem-docker/data/witness_node_data_dir/config.ini)" > ~/steem-docker/data/witness_node_data_dir/config.ini

cd ~/steem-docker ; ./run.sh stop ; cd ~/steem-docker/dkr ; docker build --no-cache -t steem .

# steps for a witness node only
cd ~/steem-docker ; ./run.sh start  ; docker logs --tail=30 witness -f # start when ready, wait for at least 128 blocks, then:

sed -i ~/steem-docker/data/witness_node_data_dir/config.ini -r -e 's/required-participation = 0/required-participation = false/g'

cd ~/steem-docker ; ./run.sh restart # final restart

Which was a way to update steemd without relying on your update.

The simple way is:

./run.sh stop
docker rmi someguy123/steem
docker rmi steem
./run.sh build
docker tag steem someguy123/steem:latest

then restart/replay as needed :)

Ah ok I see. Thank you! Yes, some lines were only for adding seed nodes etc.

I also did it this way and it worked for me. I had to replay the blockchain though.

@someguy123 you are the best, thank you for keeping the Steemit blockchain stable and updating the Steem-in-a-box for everyone!

Thank you for this... I am in the middle of 'replay' but didn't remove '/dev/shm'.... I hope everything is fine.

It will most likely be fine. Replay normally re-builds the /dev/shm, but to be safe it's always good to delete it anyway.

If you run into problems with the replay, you can try deleting it then, if not you're fine :)

Thank you for this, exactly what I'm looking for right now. Let's upgrade those servers now!

Thank you so much @someguy123 for releasing such a vital informantion.
We indeed will work with what you have released.
Just what I have been waiting for!

Yep! Some transaction was lost this night.. hope it is solved
Thanks for the alert

Thanks for this information @someguy123

Is it normal to get negative latency?

1130851ms th_a application.cpp:514 handle_block ] Got 42 transactions on block 23850830 by roelandp -- latency: -3148 ms

As always, timely action.

Well done.


steemchat is down.

I used steem in a box to install my witness server. where do I find config.ini to add steemits nodes

nano data/witness_node_data_dir/config.ini

thanks - got it I think

Good deal, you're welcome.

Hey @someguy123... you sure are some guy! always looking out for steemit. Nice call. I do hope those operating those nodes update them on time. Wish there was a faster way of disseminating information here on steemit to the right quarters.
Well i hope my resteem helps out. Done!

It went fine on my end without replay!

Awesome, thanks for being on the ball, updated and replaying now :)

Hi, I have a witness node, my account name is @exnihilo.witness. I have followed the post, I have cleared the shm and replayed but I am still in 19.3...
Does someone had the same issue?
Thank you

I did it again and it works fine now...

@someguy123 you were flagged by a worthless gang of trolls, so, I gave you an upvote to counteract it! Enjoy!!

Greetings, @someguy123,

Please pardon this 'off-topic' comment as coming from a Steemian who has followed and supported you with my witness vote for a long, long time.

I'm here to ask: When do you plan to adopt Steemit condenser version 19.10?

I encourage you to update your witness node to 19.10 at the earliest possible opportunity, so that its much needed and long awaited features might be released as soon as possible for our use and enjoyment.

Thank you kindly in advance for your prompt action in expediting this matter.

Your supporter,




Congratulations @someguy123! You have received a personal award!

2 Years on Steemit
Click on the badge to view your Board of Honor.

Do you like SteemitBoard's project? Then Vote for its witness and get one more award!