Final Update:
The bot is back online.
I was not able to recover the database. My only try was with testdisk and when it said the data in /home directoy is lost I moved on.
On the Pi I went with their recommended image of Raspberry Pi OS which is a Ubuntu based Linux. On the Laptop I went with Linux Mint. Unfortunately Linux Mint has a different approach to handling a Python installation, taking away all the independence of pip managing the Python packages with apt in a python3-xyz scheme, which of course does not include beem or hiveengine. As a workaroung I did a manual installation of these packages from the github repositories. Thankfully 
Now all that's left to do is ordering a new sd card and getting the old setup back online. That process should be brief enough with no inconvenient downtime.
Wishing you all a nice weekend. 🤗
Update:
The Pi is dead.
Well, it's the sd card. It's at the end of its life-cycle and for data protection it went into read only mode but that means the OS cannot boot since it needs to also write data while booting. I just checked and I originally bought and set it up in 2015. What a long time ago.
The Hardware (Raspberry Pi 2 Model B) seems to be ok but I don't have any spare sd card around so I need to order a new one and set it up again.
In the meantime I'm currently working on getting things running on an old laptop. This one is from 2010, yippie 🤣
Linux Mint is almost finished installing and then I can set up the python environment and hopefully recover the data so the statistics won't be lost.
But I don't worry too much about that. As mentioned before, the last block number is known so a seamless transition of processing the calls is not in question, just a matter of time. The code is saved in the cloud so that's no problem.
Original Posting:
The raspberry pi on which hug.bot is running stopped responding. Does not even start anymore. I will have a look into it but from the last error messages it sent to discord it seems the sd card running the file system went into read-only mode.
I'll have a look into what happened and how to fix it this evening. In the meantime to prepare for the worst case scenario an old laptop is already installing a fresh linux mint to take over until I got the raspberry pi fixed.
According to the logs the last block processed was #92542570.
All the calls since then will be processed once I got things running again so no call will be lost. With the last code update I also switched to block timestamp instead of local timestamp, i.e. the call limits will count to the date and time on which the call was made, not when it was processed. So no worries about exceeding your limits due to late processing.
I am sorry for the inconvenience.
Further updates will be edited into this posting.
Thank you for your patience.
Your 
Header image created with AI at deepai.org
