|
|
Line 19: |
Line 19: |
| === UNPLANNED CS SERVICE OUTAGES === | | === UNPLANNED CS SERVICE OUTAGES === |
| | | |
− | ==== Slow Access To Various CS IT Services====
| + | :None at this time. |
− | | |
− | :'''4/30/18 6:30am:'''
| |
− | | |
− | ::We are experiencing very slow access to various CS IT services, including web, DNS, and mail (sending, possibly receiving as well), perhaps some others. We are investigating now.
| |
− | | |
− | :'''UPDATE 8:30am'''
| |
− | | |
− | ::''We located an issue causing the delays, and we have instituted what we think is a fix for the problem. At the moment, all operations should be back to normal. However, we are monitoring in case of a recurrence of the problem.
| |
− | | |
− | :'''UPDATE 9:50am'''
| |
− | | |
− | ::Problem has reoccurred, but, we're able to get diagnostics data we weren't able to get before. The fix we tried earlier is not working, but with this new data, we're trying to hone in on the root cause of the issue.
| |
− | | |
− | :'''UPDATE 10:05am'''
| |
− | | |
− | ::With the additional diagnostic capability we regained, we were able to determine the root cause to be a process on one of our servers. We're restarted the process and are checking to see if it becomes problematic again. In the meantime, our services are back up and running again. But, we'll be monitoring the systems for a recurrence.
| |
− | | |
− | :'''UPDATE: 12noon'''
| |
− | | |
− | ::The process that is causing the server delays is still being problematic, and we are looking into further options to stabilize it.
| |
− | | |
− | :'''FINAL UPDATE: 4:30pm'''
| |
− | | |
− | :: '''''Problem solved!''''' We found the offending process and why it was crashing and have made a configuration change earlier this afternoon. So, far, we haven't noticed any further issues.
| |
− | <!--:None at this time.-->
| |
| <br> | | <br> |
| <br> | | <br> |