Difference between revisions of "15 July 2019"
| Line 9: | Line 9: | ||
The server was completely swapped for a different server, then data was restored from the old server. There was ~1.5 hours of down time. For the afternoon, user and app streaming (notifications) were choked up by a previously-existing bug, and were not restored until the evening. | The server was completely swapped for a different server, then data was restored from the old server. There was ~1.5 hours of down time. For the afternoon, user and app streaming (notifications) were choked up by a previously-existing bug, and were not restored until the evening. | ||
| + | |||
| + | Times in CDT: | ||
| + | |||
| + | # 10:22 in, readying power | ||
| + | # 10:25 backup | ||
| + | # 10:29 shut down services | ||
| + | # 10:30 backup | ||
| + | # 10:33 swap servers | ||
| + | # 10:48 server in place | ||
| + | # 11:11 restart test | ||
| + | # 11:18 services live | ||
Latest revision as of 20:24, 16 July 2019
-@33MHz, Mon Jul 15 17:34:01 2019
@33MHz is bringing the Pnut server down to swap the whole server for another one.
Server Maintenance
The server was completely swapped for a different server, then data was restored from the old server. There was ~1.5 hours of down time. For the afternoon, user and app streaming (notifications) were choked up by a previously-existing bug, and were not restored until the evening.
Times in CDT:
- 10:22 in, readying power
- 10:25 backup
- 10:29 shut down services
- 10:30 backup
- 10:33 swap servers
- 10:48 server in place
- 11:11 restart test
- 11:18 services live
