Tony

We will be performing an emergency reboot on the wdc006 server due to a but in the R1Soft backup kernel module. The system currently is unable to do backups as well as having stability issues as the module will not unload. We've consulted with R1Soft and have been advised to reboot the system in order to resolve this. We will be rebooting the server between 7:00pm EST and 7:30pm EST and we estimate the server will be down no more than 15 minutes. Date: 12/14/2011 Start time (EST): 7:00am End time (EST): 7:30pm Duration: 30 minutes Estimated Down Time: 15 minutes

This has been completed. We've doubled the amount of backups we're keeping on this server for now in case we missed any of the tables and users need them restored.

We're making good progress and should have this completed by some time tonight.

All the corrupt tables have been removed and we're working on restoring them now. Our estimate is this is going to take at least 24 hours to get them all done. There is no particular order they are being done in we're just doing it from a randomly generated list we made before starting the process.

Select the third option "I will update my nameservers on an existing domain Or I will register a new domain."

At this time Blackbird InnoDB based tables are unavailable due to corruption caused by the crash. We've exhausted all avenues of repairing the data that is currently there on the server. Since this issue only effects a small subset of users a full restoration of the MySQL databases does not make sense. What we are going to do is remove all the current innoDB tables as they're not usable and restore them one by one back onto the MySQL server. We estimate that this will take up to 24 hours to do. We're sorry about any inconvenience this may cause but recovering these tables is not an easy task while trying to make sure the rest of the server stays online.

Due to an unexpected power failure in our datacenter facility, we will be required to perform an emergency fsck on this server. We will update this thread as we progress. Please direct any questions to our helpdesk at https://support.hawkhost.com

There appears to be an outage of some kind in the Seattle facility. We have no further information at this time as we're waiting word from the datacenter what the issue is. This started about 10 minutes ago (7:16 PM PST)

At this time we only have reseller services in Dallas, Seattle and Washington. We're not sure when or if reseller accounts will be available in Amsterdam. The new locations are tricky due to IPv4 shortages as the way we do IP's in North America we just can't do the same elsewhere. So our reseller plans how they're structured will need to change to make it possible and we're not sure how this will effect people actually wanting reseller services. So those changes will probably come to North America first then out to the other continents once we know it's not going to suddenly make our reseller services undesirable.

I can't think of a solution here the CLI commands really should not be showing up for client user to begin with. The jail shell which we use would block those out as you get a virtual /usr of files we want to be available hence there being no mailman. I really don't think there is a good way to do this in a more automated fashion. I'm also not sure if it's a good idea to even allow people to make mailing lists it could be abused very easily.

This has been completed and the machine is now back online.

The machine has just been taken down to replace the memory.

The crash was due to bad memory based on our investigation. We will be replacing the memory early Tuesday morning and a maintenance topic has been opened:

On Tuesday November 8th between 1:00AM and 4:00AM CST we will be replacing the memory on the Cobra server. This is due to the fact the system crashed earlier today due to bad memory and to avoid further issues we're going to replace the memory early in the morning on Tuesday. We estimate there will be about 30 minutes of downtime to replace the bad stick of memory in the system. If you have any questions regarding this maintenance notice please do not hesitate to contact our systems administration department. Date: 11/08/2011 Start time (CST): 1:00am End time (CST): 4:00am Duration: 3 hours Estimated Down Time: 30 minutes

That is not possible as cPanel sets it up the primary domain must go to the public_html folder.

It's a symbolic link so the "[email protected]" actually goes to the firstphilec.com/username folder.

The sea005 server had crashed earlier today due to several sticks of memory failing on the system. Upon the server booting back up it was noted that the server was now reporting 16GB total memory opposed to the total 24GB. We've had four total sticks of memory fail which will need to be replaced. We will be replacing these on Sunday October 16th between 9am and 12pm PDT. This is the most off peak time for this server based on load average which is why we're doing it during this time. We estimate there will be about 30 minutes of downtime to replace the failed sticks of memory. If you have any questions regarding this maintenance notice please do not hesitate to contact our systems administration department. Date: 10/16/2011 Start time (PDT): 9:00am End time (PDT): 12:00pm Duration: 3 hours Estimated Down Time: 30 minutes

This has been completed.

We forgot to update this but it's well under way and we should have this completed on the 12th.

This has been completed and the new BBU is now charging.

The machine was just taken offline to replace the backup battery unit.

We've received RAID alerts that the BBU failed on this machine (non-service impacting). However to ensure the integrity of the RAID in case of a failure we're scheduling an emergency maintenance to get this replaced on Monday October 10th. If you have any questions or concerns please contact us via our support desk. Date: 09/16/2011 Start time (PDT): 1:00am End time (PDT): 4:00am Duration: 3 hours Estimated Down Time: 30 minutes

Starting on Monday October 10th we will be migrating Skyline server to new higher end hardware as well as better system configuration when being strictly a reseller only system. We feel this will benefit all users on the Skyline server as it will make it consistent with other reseller only servers we have. We estimate this will be completed no later than Wednesday October 12th. We expect no more than 5 minutes of downtime per reseller account as we will be moving accounts to the new server then re-routing the IP address to the new hardware. This means there will be no changes to DNS and as a result no dns progation issues. In our experience our migration method means the large majority of users will not even realize that they've switched servers. If you do however run into any issues do not hesitant to contact us as our system administrators are prepared to resolve any issues experienced. The new Skyline server will be matching what the majority of our servers currently are in specifications: Old Skyline: Dual Xeon E5450 12GB RAM 4x300GB Raid-10 New Skyline: Dual Xeon E5520 24GB RAM 4x300GB Raid-10 This is one of our former systems that is currently sitting idle as the number of users on the Skyline server it did not make sense to deploy excessively high end hardware which would go under utilized. This machine however is a pretty big upgrade over the old specifications and still high end by industry standards. It will be using CPU's which support hyper threading which will help with CPU abuse. It will also have double the amount of system memory which on most systems provides significant gains in speed. We also will be using a better designed operating system layout to better utilize the hard disks. Once the migration starts the current skyline system will be named oldskyline while the new one will become skyline this is one thing to keep in mind during the migration. If you have any questions regarding the maintenance do not hesitate to contact us. Our system administration department is available to answer any questions regarding this. Start Date: 10/10/2011 End Date: 10/12/2011 Estimated Down Time: less than 5 minutes Duration: 3 days

This has been completed.

We're still working on this and should have it completed later today