Cody R.

Connectivity has been restored at this time. We'll be keeping this ticket open for 24 hours in case there are any further issues.

There is currently an ongoing network issue at the data center which is affecting the Hornet machine causing the public network to have no connectivity.

Thank you for the recommendations. I'm going to be posting your questions in a cleaner format for other potential customers and will be including a Google translation to Chinese. Hopefully it's clear / works okay. Interpreted Quote: We have a large Chinese customer base and would like to cater to them more (primarily translations on the website / customer support) - the issue is Hawk Host is a smaller company and we simply cannot afford to offer bilingual support at this time. We hope this can be changed in the 2012 year and be able to support multiple languages by 2013 although it's uncertain. The auditing portion of accounts we're working on expediting and should be near instant shortly - in the interim the biggest issues we see from our international customers that cause delays in account setups are the following: Invalid account information - name, address, etc Signing up with an unregistered domain - we require the domain you sign-up with to be registered Signing up via a proxy / VPN - we require all orders to be placed via a normal line / non-open relay Please let us know if you have any further suggestions - we now support AliPay due to our Asia customer base asking for it! Thanks! ---------- Chinese translation via Google ------------ 谢谢你的建议。我会被张贴在您的问题，为其他潜在客户的清洁格式将包括一个Google翻译成中文。希望它很清楚/工作没关系。 解释引用 (English)： 我们有一个大型的中国客户群，并想满足他们更多的（主要是翻译网站/客户支持） - 问题是鹰主机是一个规模较小的公司，我们根本无法承受在这个时候提供双语支持。我们希望能在2012年一年的改变，到2013年能够支持多国语言，虽然它是不确定的。 帐目审计部分，我们正在加快，应该不久附近瞬间 - 在此期间，我们看到从我们的国际客户的帐户设置，导致延误的最大问题是以下： 无效的帐户信息 - 姓名，地址，等等。 未经注册的域名与签约 - 我们需要您注册的域名进行登记 通过代理/ VPN签约 - 我们要求所有的订单可以通过正常的行/非开放中继 请让我们知道，如果您有任何进一步的建议 - 我们现在支持支付宝，由于它要求我们的亚洲客户群！ 谢谢！

Everything is back online, we'll be posting more information shortly.

Everything is back online, we'll be posting more information shortly.

From the data center -- At approximately 14:11 UTC on 28-FEB-2012 the Network Operations Center detected service issues with frontend customer router fcr01.sjc01 and at 14:12 UTC the router's secondary management module crashed, taking the secondary chassis offline. All customer servers behind fcr01.sjc01 experienced a brief traffic disruption as the primary chassis took over. Servers behind aggregate switches fas01.sr01.sjc01, fas02.sr01.sjc01, fas10.sr01.sjc01, and fcs71.sr01.sjc01 experienced an extended traffic disruption due to software-related port channeling troubles resulting from the crash. By 14:57 UTC, network engineers completed the restoration of public connectivity to all remaining customers. We have opened a case with the router's manufacture to assist in determining the root cause of the issue. --

From the data center -- At approximately 14:11 UTC on 28-FEB-2012 the Network Operations Center detected service issues with frontend customer router fcr01.sjc01 and at 14:12 UTC the router's secondary management module crashed, taking the secondary chassis offline. All customer servers behind fcr01.sjc01 experienced a brief traffic disruption as the primary chassis took over. Servers behind aggregate switches fas01.sr01.sjc01, fas02.sr01.sjc01, fas10.sr01.sjc01, and fcs71.sr01.sjc01 experienced an extended traffic disruption due to software-related port channeling troubles resulting from the crash. By 14:57 UTC, network engineers completed the restoration of public connectivity to all remaining customers. We have opened a case with the router's manufacture to assist in determining the root cause of the issue. --

Would you mind submitting a ticket for this and reference this post? I suspect this is due to how cPanel creates the web server configs and may not be possible. We may be able to give you an alternative URL however.

You could be getting limited on a single database due to excessive resource usage - if you can PM me your ticket ID I'll take a peak for you .

We upgraded PHP 5.3 to 5.3.10 on every machine when this was first disclosed. It may be worth mentioning by default we run PHP 5.2.17 (latest stable of that branch) which was not affected by this. Thanks for keeping us on our toes

We upgraded MySQL on the lightning server this evening however the accumulative downtime was less than a minute however it was likely that. If you experience any further issues please submit a ticket and let us know

The maintenance has been finished so this will conclude the maintenance window.

This maintenance window will be starting shortly.

Due to a bug in this existing kernel we'll need to perform a full kernel upgrade Monday 02/13/2012 to resolve the issue. Date: 02/13/2012 Start time (PST): 06:00pm End time (PST): 08:00pm Estimated Down Time: 10 minutes

Unfortunately not - you'll need to give them your cPanel login. You could upload your own version of PHPMyAdmin but if you do make sure you lock it down with a password (it has an option in the config).

The FSCK has completed and the machine is online booting services. Please allow 10 minutes for service speeds to return to normal.

The FSCK is 90% complete at this time.

The FSCK is 80% complete at this time.

The FSCK is 50% complete at this time.

The FSCK is 20% complete at this time.

The FSCK is 15% complete at this time.

The Spitfire server had a kernel panic which we believe was caused by bad memory. Unfortunately we're forced to do a FSCK on a few partitions so we'll be providing updates in this thread as it progresses. Please direct any questions to our helpdesk at https://support.hawkhost.com

Technically chat scripts aren't allowed on our hosting (against the AUP) because they're generally resource intensive and cause issues. You're more than welcome to try to use one however if we notice it causing issues we'll kindly ask you to remove it from your web space.

It's just a generic 500 error which generally means there is an error in your configuration (interpreter: PHP, ASP, etc)

We'll look into it however Spam Assassin has treated us pretty well - we also shy away from a lot of the bayesian filtering stuff and opt for a simpler DNSBL approach which seems to curb the majority of spam. If you notice a large amount of spam in your inbox let us know and we can look into it further .