Tony

For the curious ones out there the console of the machine when it crashed:

You'll need to use the add-on domain feature then. You'll set the document root to the folder that you wish to be displayed when visiting the domain. So remove it as a parked domain then add it back as an add-on domain.

If the domain you're redirecting is hosted on your account you should use the parked domain feature. If it's not then no way around this other than actually pointing this domain at the other machine and having them add entries for it. If you did park it and it's redirecting then the script you're running is redirecting or it's being done in your .htaccess file.

This has been completed.

I think there is a simple explanation here. You are using login details that can't work when your domain resolves somewhere else. So your domain is http://www.ahaseeb.com/ and you're putting the ftp information with us as ftp.ahaseeb.com. This won't work since it resolves to your other host: http://www.intodns.com/ahaseeb.com So you need to use the temporary ftp ip address if your domain does not resolve to our servers. I'm looking at the ticket and quick reading suggests we mentioned this as well. Though looks like you're still trying to use ftp.ahaseeb.com which is going to continue to point to your old host as long as you have the name servers set to them. I don't know if it's a language barrier that is providing the confusion here as to how this ticket kept going back and forth for so long.

It was which is why more hardware is coming online

This has been completed.

We'll be performing a kernel upgrade on on Tuesday December 28th between 8:00am and 9:00am PST. This upgrade will allow us enhanced resource tracking to help address resource abuse issues. We estimate the server will be down for about 10 minutes while the machine is rebooting to the new kernel. Date: 12/28/2010 Start time (PST): 8:00am End time (PST): 9:00am Duration: 1 hour Estimated Down Time: 10 minutes

We'll be performing a kernel upgrade on on Monday December 27th between 10:00am and 11:00am EST. This upgrade will allow us enhanced resource tracking to help address resource abuse issues. We estimate the server will be down for about 10 minutes while the machine is rebooting to the new kernel. Date: 12/27/2010 Start time (EST): 10:00am End time (EST): 11:00am Duration: 1 hour Estimated Down Time: 10 minutes

Yeah you can purchase additional accounts and use the coupon there is no restriction there.

Well you won't be the only one who will ask. The promotions though we could not offer them on a daily basis and it's reflective of that. So doing it on renewals for example would greatly effect the quality of our services. We simply have a lot of extra capacity right at the moment and we're going to make use of it. Then hopefully in a years time a lot of the users are happy and pay the normal fee for their services.

They can be used for new hosting orders. They cannot be used for upgrades of accounts or renewals.

If you ever emailed us or opened a ticket via email the account already exists. Use the forgot password option and it'll reset your password for you.

Exactly. Right now they are not integrated several bugs made it even more confusing when it was integrated. This will be changed when we switch to a newer version of the support software that allows for easier integration between the software.

We just finished some improvements on another server which had similar issues. Once the fix was in place no longer did the backup system cause random slowness spikes. So we have reason to believe Voodoo will not have any issues either when it does it's backup tonight. Though we'll keep an eye on it but pretty confident our fix has done the job. It also has mitigated other aspects that could cause spikes and slowdowns. So now everything should be typical speedy with single users being unable to slow down an entire server with intensive scripts. They just have their own site slow down.

We're working out a kink it seems some machines when our backup system runs it causes i/o lockups. It didn't happen at Frog Host and did not happen on other Hawk Host servers running it. So it's causing a tiny i/o timeout then it goes away. We think we know how to fix it though just a matter of making a fix for it. Seems no matter the amount of testing you do with enough servers you find new issues and bugs.

1. This is per account usage and it represents how much of your allocation of CPU you're currently using. 2. Concurrent number of connections you're currently using on the web server. Part of the CloudLinux push we're doing. We're still working out some random kinks though.

This has been fine for some time so closing this now.

The server just finished rebooting and services are now starting back up. It'll take a bit to be at optimal speed while caches rebuild.

Everything has been optimal for a bit of time now so going to go ahead and close this.

The machine just finished rebooting it is now just loading all applications back up. There might be a little bit of slowness until the caches are warm.

The machine is now available again to restore backups and is also making backups once again.

The machine is finally back online but backups are not yet available. We're just checking some raid health related aspects before turning everything back on.

We are still working on this. What happened was the old raid card was failing so we were replacing it to resolve that problem. Once we replaced it the new raid card would boot it's internal kernel then panic. We then proceeded to try the older raid card again and it unfortunately did not function very well as it was failing and was extremely slow. We are working on figuring out why the new raid card is not functioning. As soon as we have more information it'll be provided in this topic.

We've ran into issues after swapping the raid card. We're working on resolving them still.