eagleharbor.dcnsafe.com rebooting
9:45 AM: Resolved! (For now) The server has been rebooted, our login has been restored and we are running extensive testing to find and identify the remedies to all of the issues we experienced with the server this morning.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7:38 AM: Update — Next step… the server is back up & online, but unfortunately it is not allowing our remote techs to login to do root-level tech work. The root login will need to be reset, which is done by … rebooting the server.
Don’t give up yet! Yes, we’re wincing too. But, the good news is the fsck has finished and the server has come up successfully here in the past 10 minutes, and continues to chug along, so it should come back up after the root login is reset/re-activated. Once we have a working login we can continue to do tech work from our location and advise further on this server’s status & short-term future direction.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6:55 AM: Update — The primary drive is still running an FSCK. This is probably best described as the Linux equivalent to a Windows defrag. FSCK stands for File System ChecK. It is a normal Linux process and runs only when necessary; the on-site techs saw it was needed in order to bring the drive back up in a stable condition, so they have been running it. We will bring the server back up just as soon as the FSCK has been finished; it is not something that can be safely aborted or ignored, as doing so could destroy data.
Please rest assured we remain on top of this issue and will continue to provide updates as they are available!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5:52 AM: Update — The server has several issues going on.
The most pressing are drive errors which were reported via console while the techs were working on the server. The on-site techs have taken the server down to do a drive analysis, which unfortunately we know from previous experience can take hours to complete. Obviously that’s not an option to us. We’ve requested the drive be put back in the chassis and we will run our own tests from our location.
If drive work/replacement needs to be done, we will schedule it to be done overnight tonight. That is a big “if” — as it is not uncommon for cPanel servers to report drive errors erroneously. The S.M.A.R.T. system is quite aggressive, and usually wrong.
Two, we have an issue with script kiddies weaseling their way in through exploitable client scripts. We need clients to update their scripts immediately to plug these exploits and stop the illicit activity. So far the kiddies have not gained sufficient access to alter data, but they have nearly crashed the server at least once with extreme load, and tonight’s downtime may have been caused at least in part by this. It is only for everyone’s well being that client scripts be kept updated. Please update your scripts immediately once your website comes back online. If you do not know how to do this, please let us know and our technicians will be happy to update your scripts for a fee.
Thank you for your patience as we’ve worked on this for you. We will be staying closely tuned to this as the day progresses and we will post further updates here as things develop.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5:30 AM: Update — The technicians report they are bringing the server up now. We continue to investigate the cause of the outage and will report as we know more. Thank you! :)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The eagleharbor server appears to have gone down. Our technicians are working on bringing it back up and we will update you as soon as we know more.