Check our services status at a glance
| Title | mysql1 is down |
| ID | Operation #148 |
| State | completed |
| Beginning date | 11/21/2013 5:49 p.m. |
| End date | 11/22/2013 11:44 p.m. |
| Affected servers |
|
| 11/21/2013 5:49 p.m. |
We’re investigating. |
| 11/21/2013 5:52 p.m. |
The server is frozen. We’re restarting it. |
| 11/21/2013 5:59 p.m. |
The server has restarted, MySQL is now recovering. |
| 11/21/2013 6:08 p.m. |
It’s still recovering. As there are many databases, it takes some time. |
| 11/21/2013 6:12 p.m. |
The recovery is done, the kernel has been upgraded. MySQL is (slowly) starting responding requests again. |
| 11/22/2013 12:43 p.m. |
The RAID reconstruction causes an increased latency on the server. It is expected to take 4 more days. |
| 11/22/2013 10:34 p.m. |
The server has frozen again. |
| 11/22/2013 10:46 p.m. |
We’ll install another kernel, but we suspect a hardware failure. MySQL is recovering. |
| 11/22/2013 10:54 p.m. |
We’ve stopped the RAID reconstruction for now. We’ll need to know more about the freezes. |