Home»Time Entries Audit loading ... [hide int notes] generated 8/8/2026 at 8:38:08 pm took 0.95 seconds version: b85cbb8 helpers: v1
Territory: BMS Month: « Jun 2026 » Company: all Ticket: 76486 [x] User: all Type: all Role: all Bill: all Timesheet: all 6/1 6/8 6/15 6/22 6/29 Board: all Entry Status: all Ticket Status: -Closed [x] Issue: all [reset] Progress: 100% (1 of 1)
| row | id | Terr | Company | User | Date | Day | Start | End | Actual | Billed | Deduct | Inv Amt | Work Type | Work Role | Bill | Timesheet | Board | Entry Status | Ticket Status | Ticket # | Ticket Summary | Int Notes | Audit Done | Audit Notes | Notes | # issues | all issues | errors | warnings | notices |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 41115 | BMS | OMNI | fdrewett | 6/3 | 7:30 am | 11:30 am | 4.00 | 4.00 | 0 | 500.00 | Remote | Standard Technician | Billable | 6/1 | Help Desk 2.1 | Billed | -Closed | 76486 | AMR SERVER DOWN | 1 | 7/26 CS long notes ok | **omni-docker01 MySQL crash incident - RESOLVED 11:36 AM** Production MySQL on omni-docker01 \(Omni POS at the AMR location\) entered a crash loop after this morning's automatic update bumped MySQL from 8.4.8 to 8.4.9. Omni POS and menu services were unavailable from approximately 07:57 until 11:36. Root cause: the MySQL config referenced an orphaned encryption keyring plugin left over from a July 2025 install. The new 8.4.9 binary failed to load that stale plugin and crashed on startup before reaching the database. After five failed restarts, the service gave up. Because the server uses encryption at rest, the obvious quick fix \(removing the bad config line\) would have made the encrypted data unreadable. Identified the correct path instead: migrating to MySQL's supported replacement keyring component, which uses the same on-disk format so no data loss or re-encryption is required. Engagement was read-only diagnostics on our side. Walked Kevin Adams \(Omni's server lead\) through the root cause and remediation plan. Kevin applied the migration during the incident, preserved all encrypted tables, and confirmed resolution at 11:36 AM. Also audited the server's automatic-update policy and found it would likely trigger the same class of failure on future updates. Drafted a configuration override to address that. Deliverables: full migration runbook, single-page remediation cheatsheet, and a self-contained incident writeup in the shared OMNI\_Docs vault for the Omni team. | 1 | Notices: Notes: Notes longer than 500 characters | Notes: Notes longer than 500 characters |
Legend:
(hover over fields for details)
Notices
| Field | Message | Count |
|---|---|---|
| Notes | Notes longer than 500 characters | 1 |
| Total | 1 | |