ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0009531 | ClearOS | system-mariadb | public | 2016-07-07 15:13 | 2016-08-11 08:20 |
| Reporter | user2 | ||||
| Assigned To | user2 | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | 7.2.0 Updates | Fixed in Version | 7.2.0 Updates | ||
| Summary | 0009531: Make sure database repair happens on a reboot | ||||
| Description | It is difficult to predict the boot order in systemd, so find a way to run the database repair script (/usr/clearos/apps/system_database/deploy/repair) on boot. Gotchas: - Database must be running - Since the repair can take a few minutes on large databases, the script cannot be part of the systemd startup routine | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2016-07-07 15:13 | user2 | New Issue | |||
| 2016-07-07 15:13 | user2 | Assigned To | => user2 | ||
| 2016-07-07 15:13 | user2 | Status | new => confirmed | ||
| 2016-07-13 08:52 | user2 | Category | app-system-database - System Database => system-mariadb | ||
| 2016-07-13 08:52 | user2 | Status | confirmed => resolved | ||
| 2016-07-13 08:52 | user2 | Fixed in Version | => 7.2.0 Updates | ||
| 2016-07-13 08:52 | user2 | Resolution | open => fixed | ||
| 2016-08-11 08:20 | user2 | Status | resolved => closed | ||
| There are no notes attached to this issue. |