Firstly, sorry for not posting too many of these Liotes Hive Witness updates... As the node was working perfectly, without any issues, we didn't find valid reasons to post these updates... Of course, we do have regular weekly updates about our project, but this one will be about our Liotes Hive Witness node only!
Created in Canva.com
Secondly, we would like to thank everyone who voted for our witness and supported us! All your support pushed us to the 76th place of all active nodes! THANK YOU! 🙏
Now, let's go to techie stuff... We are running the HIAB (Hive In A Box) version of the Hive Witness node, and we were running the 1.27.4 version until today! The next two versions aren't mandatory and Hive node was compatible with the newest version, but it was time for an upgrade...
For those who are using HIAB, the upgrade operation should be easy... According to the official documentation, it should be literally three commands to run!
git pull
./run.sh install
./run.sh restart
You can guess... It wasn't like that... 😃 I encountered a few issues during the process and I had to find out how to solve it... Luckily, I had the help of two fellow witnesses, @louis88 and @hivetrending! Thanks, guys!
This is how it looks when your node is working as it should:
As this upgrade needed the replay of the blockchain, when I followed those instructions and ran it to replay, it looked like he was doing it... And it looked like this...
When it finished, it dropped the error that looked something like this... and exited the replay...
Luckily, or unfortunately, the above-mentioned guys had the same issue as me, but it looks like they had different solutions... But, they had a solution! 🙂
Firstly, I tried one solution that was running the
./run.sh fix-blocks
command, which looks scary as it will cut out parts of the chain, trying to fix the issue... If you are a newbie, maybe you shouldn't try this first, but rather as an "ultimate try"...
While I was doing that, I spotted an error...
rm: cannot remove '/dev/shm/shared_memory.bin': Operation not permitted
That smells fishy...
The second possible solution was to run
./run.sh clean shm
command, which was doing the same thing as the step that threw an error in the first solution... Do we have a bingo?
Yes, we do! For some reason, I had to add the SUDO command at the beginning, and it finally cleaned the shared memory!!!
sudo ./run.sh clean shm
After that, I run the replay command:
./run.sh replay
and the script did what it had to do!!!
Not every upgrade needs REPLAY, but this one does! So, when you run it, you can go out and relax for a couple of hours, or maybe even a full day... At our machine, it lasted around 20 hours, which isn't that bad...
After ENABLING your node, when you sign the first block, the number of the node version should change to the latest! So, don't freak out if it doesn't show it right away after enabling...
Hope that this short troubleshooting post will help someone who encounters the same issue...
Thanks for supporting Liotes Hive Witness!
👉 Vote for Liotes HIVE Witness HERE 👈
Liotes
A project run by @ph1102 and @achim03
Good ol' @hivetrending! Always dependable in the PIZZA server and just about everywhere else on HIVE too! 😜
Cheers!
I wonder if it is profitable to run a node in those positions.
You can check daily/weekly earnings by yourself at the website created by @primersion
https://primersion.com/earnings
No, it is not. But it is a good position.
In this position we are very close to cover the costs of running the server. With every gained rank, the income gets bigger. If we manage to climb a bit in the ranking, we could even make a small profit that goes 100% back into the liotes project as hive power on the liotes account. This hive power is delegated to the liotes.voter account and generates daily LEN dividends. These dividends are then burnt. The more the account grows, the more value we can burn every week and help increase the value of the token.
Updates are always annoying, but I am glad you were able to solve it. All those command line prompts remind me of college. Writing code sucks when things don't work properly and you got to debug.
Hahaha... What you said was my main reason not to go into coding and programing... I like to debug and troubleshoot things, but that would kill me... I can't stop thinking about the issue until I solve it... and that's the 0-24h job when you are a programmer... 😃
Happy to help
Thank you for the update!
Wow this is so technical. All the best!
I still don't know about all this tech stuff, but it sure sounds like good news. :)