Hi Søren Jessen,
Good day!
I am sorry to know that you didn't think our support was up to the mark. Please allow me to explain the chain of events briefly.
You would probably agree that this is the first downtime during the time you are with us.
This was InnoDB corruption. If it were a simple service crash or database failure, it would have been resolved within minutes.
When we noticed the issue, the indexes got corrupted along with a few databases and MariaDB system files. System files often get corrupted during cPanel or CloudLinux updates, and they are developed and managed by cPanel and CloudLinux. So it was best to ask them to check if there was any known remedy to these issues before we tried anything.
We contacted cPanel right away. We are a certified cPanel partner, which means we get priority support compared to regular partners. They responded quickly but singled out the system file corruption and suggested taking it to CloudLinux because they maintain the repositories of those system files. In other words, there was no simple fix.
When two software vendors are involved in any troubleshooting, it can become a lengthy process to come to a resolution. We didn't want to try that and were investigating logs and evaluating potential routes to apply fixes. We had to reinstall MariaDB and delete and restore the databases to fix corruption. This took a longer period of time.
While we were troubleshooting, we were posting updates via your support ticket, live chat, and on our server status page to keep you and everyone else informed.
We have also extended your service for two additional months for the downtime caused.
I can assure you that we tried everything we possibly could to resolve this issue as soon as we could. But unfortunately, downtime was inevitable due to the complexity of the issue. If you still have any concerns or questions, please feel free to get in touch with us, and we will try our best to answer your questions.