Cody R.

The machine is currently online and booting services. Please allow a few minutes for it to stabilize / warm caches. We will also be replacing a hard drive in this machine shortly however we anticipate no downtime doing this as all of our machines have hot swappable bays.

The file system checks are now completed. The machine is rebooting now.

The /var partition is finished and we're now starting on /usr. It's currently at 50% completed.

The machine is online and booting all services. Please allow a few minutes for the machine to warm up (caches, etc).

The machine is booting now.

We're at 85%

The filesystem check is currently at 45%

This has been successfully mitigated. We'll be leaving this ticket open for a few hours while we monitor the server. Everything is online and responsive.

Due to an ongoing DDoS there is intermittent connectivity issues. We're in the midst of attempting to mitigate it and anticipate this should be resolved shortly.

We were able the boot the rescue OS and access it via a KVM. The filesystem check is now underway.

It appears the server isn't PXE booting. We're seeing if we can simply bypass that for the time being to get the file system check underway and the machine online ASAP. *EDIT* Clarification - the PXE booting is for the rescue OS which is what we would typically use to issue the file system check.

The machine is having issues booting into the rescue operating system. We're having data center technicians manually console into the machine to diagnose the issue. We'll update this thread as we get more information.

We're booting into the rescue mode now. Once it boots into that we'll be running the file system check on the /home partition. We anticipate this to take between 30-45 minutes.

Mercury went read only around 1:35AM so we're forced to take the server offline to run a filesystem check on the partition in question.

It appears this was a result of several factors exhausting the servers resources in a rapid manner crashing the machine. We've taken corrective actions against the user(s) who caused the spike and believe the issue is now resolved.

The machine is online and is starting all of the services. Websites should be available at this time. We'll post an update once we investigate the cause.

Phantom became unresponsive at 3:15PM EST. We're in the midst of rebooting it and will evaluate the cause once it's up.

I would simply ignore blacklists such as this - it appears to be nothing but a random operator that takes results from other DNSBL's and such. In the future please contact us to get the IP removed and don't do it on our behalf as without a doubt it stated that you must be the owner / operator of the IP in question.

Yes, the latest of the PHP5.2.X branch is 5.2.14 (what we run). The latest stable of PHP5.3 is 5.3.3 (which we'll be offering as an option soon). This is significantly newer than PHP5.2.4+ specified and should work fine .

Oh dear - this is a legacy DNS entry that was used during some large network maintenance awhile ago. The URL had a simple status page that was hosted outside of SoftLayer facilities (TechieMedia) so it would be unaffected. Unfortunately it appears this IP was re-provisioned and the DNS entry still existed - hence the redirect. This should be removed in a few hours for everyone (DNS takes a bit to propagate). **EDIT** I removed the direct hyperlink / added a NSFW warning as to avoid any issues. Hopefully it's a non issue

That shouldn't be an issue . For future reference you may have a faster reply if you submit a ticket via our support system (https://support.hawkhost.com).

This isn't a charge from Hawk Host but your banking institution. Since Hawk Host is based in Canada some banks consider it "foreign" and charge a "Foreign Transaction Fee" (https://support.hawkhost.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=95). Unfortunately this is out of our hands and is at the discretion of your bank.

I'll be replying shortly - I had a very long reply and wistfully hit ctrl-w some reason making it go poof.

Fabian is stealing the limelight! Thanks for the awesome review.. very in-depth and seeing from your past posts (we frequent WHT) I know you're very pragmatic / detail oriented so I'm somewhat surprised we passed with flying colors. Any recommendations on how to improve? Anything you would like to see?

A quick update regarding this maintenance