Had observium running on a system for a bit under ubuntu 20.04. Had a power issue where it seemed to screw the pooch on the server. don't see filesystem errors that I can detect, however do find that the mysql instance doesn't want to start back up.
When trying to do a repair on the database, get the following:
(edited my.cnf with innodb_force_recovery so as to get mysqld to run)
mysqlcheck -u root -p --auto-repair --all-databases
---cut
observium.slas OK observium.snmp_errors OK observium.status OK observium.storage To be repaired, cause follows: Server issued Warning : InnoDB: The B-tree of index PRIMARY is corrupted. Warning : InnoDB: Index index_unique is marked as corrupted Warning : InnoDB: Index device_id is marked as corrupted error : Corrupt observium.syslog OK observium.syslog_alerts OK
---cut
Only the observium.storage table seems to be messed up (or only one throwing errors at least at this point). Now this is thankfully not the main deployment this is in my test lab (reason why it didn't have good power backup). So I /could/ just re-do the entire deployment, that being said, I would like, if possible to be able to recover this just to save about a years worth of data in the lab, and to see how to do this in case it actually happened on the production system.
anyone have suggestions?
If not, second question would be has anyone tested the install scripts with ubuntu 22.04 yet? If I have to do it from scratch may as well use the newer version.
Thanks
steve