System Status Report
Monday, June 24th 2013
The Main Server had trouble for 8 hours, 50 minutes
At 4:13am on June 24th, 2013, the primary hosting server performed mandatory updates as per requested on a semi-daily basis. Shortly after the updates were installed, the server went through a mandatory reboot to ensure the updates were installed correctly.
During the reboot process, an error occurred which dealt specifically with the network interface for the server. In short: the network interface would not come online.
The server would respond to requests through a direct console, but would not respond to any internal or external network commands. Overall, the situation became very puzzling very fast.
In order to access and repair the server, clearance access was needed to access the necessary files and sections on the server that could be modified. After searching through all of the data and error logs for the server, and trying many different scenarios, the issue was determined to be a mismatched set of unnecessary DNS records on the operating local nameserver which caused the network interface to encounter an error upon initializing. When these troubling DNS records were removed from the processing procedure, reboot commands would complete with success.
Upon five continuous reboots, the problem had been declared fixed. Testing of the network interface performed as expected, and the server is processing the nameserver records as expected. Therefore, our expectation is that this problem should not occur again.
As of 1:56pm on June 24th, 2013, the primary hosting server is online and operating as expected.02:05 pm EST
« Back to Q5 Industries Status