Qube! stores all job-related information (with the exception of the job logs) in a set of MySQL databases on the supervisor. When the supervisor host crashes, is powered off without being gracefully shut down, or runs out of disk space, individual tables in these databases can become corrupt and need to be repaired. In most cases, Qube! will continue to run with these databases in a corrupt state, but supervisor performance will be impaired.
There are 2 operations available from within the QubeGUI to aid a Qube! administrator in database maintenance: a health check, and a repair. Both operations can be performed while the supervisor is running, but your users may experience slowdowns if you run these during periods of peak load.
Both operations are performed from the QubeGUI->Administration menu, and are accomplished via the MySQL mysqlcheck command-line utility.
The following conditions must be met before these menu items are enabled and available to be run:
- There must be a running MySQL server on the local machine.
- There must be a database named "qube"
- If there is a database_password defined in the qb.conf, it must not be an encrypted 64-character hash, but instead stored in plaintext.
The mysqlcheck command being run is printed in the QubeGUI Log Panel prior to the check/repair starting. Progress of either the Health Check or the Repair is printed to the QubeGUI Log Panel as the operation is running.