Tony

All our fix scripts have finished running. If you have any problems please open a support ticket.

All scripts our fix scripts have now been run on Mercury. If you have any problems feel free to make a support ticket.

Well the problem was nothing to do with the rebuild just the php.ini was not formated properly. I didn't pick up on this either but you need to have register_globals = On Just like you would in a ini file not just var then space value.

A quick update here PHP4 is now built against the MySQL 5 system and is working fine. if you have any other issues please open a ticket or use our live chat system.

PHP4 should be on the right mysql version in about 10 minutes. Sorry about that, it seems our build script from our other servers did not play nice with the Mars server unfortunately.

We found an issue with the PHP4 install that did not show up at the start. PHP4 mysql implementation was built against the wrong version. We're currently rebuilding it so it will work fine with MySQL5. I'll update when that is completed.

Upgrade to Apache 2.2 is now done. The fix scripts are now running and I'll update the topic again when they've completed running.

The scripts are going to run in the background for some time. The big part of the upgrade is done. Since your error will not be fixed by the scripts you should make a ticket.

The server is running Apache 2.2 with the new setup now. Our scripts are running to fix common problems. However the issue you're having is not one of the problems that is common.

Please open a ticket But I can tell you right now php_flags will cause internal errors. The other issue I'm not sure just open a ticket.

The scripts to fix permissions and other issues that may have come up. I'll update this thread again when all the scripts have completed running.

The upgrade is taking longer than we had expected. I'll update the topic as it moves along.

It should not cause any problems. The only issue that would come up is if you have a .htaccess file that is modifying php flags. In which case you'll want to use a php.ini file instead.

On Friday December 21st at 11am EST we will be upgrading the Mercury server's apache version to 2.2 from the currently running 1.3 branch. We expect this migration to take about an hour to do. We do not expect any down time during this migration. We've been running Apache 2.2 on our Venus server for over a month now without issue. It has brought much better performance and made our management of the server much easier. We'll also be switching to suPHP which will make things much less complicated with regards to permissions of files. 777 files permissions will no longer work and 755 will be the maximum needed for php scripts to access files on your sites. Here is a quick summary of the new features and any problems you may encounter. Apache 2.2 Apache 2.2 has much better resource management. As a result it can much better serve static content. Static content would be things like images, files ect. This should not be confused with PHP or CGI scripts which are not static at all. As for problems this may cause we do not expect any at all. suPHP suPHP is a much more secure PHP setup. It has all PHP scripts running as the user. This means that there are no issues with uploading of content and another user owning the files. It also restricts the acceptable permissions for files which is where we expect the majority of problems to come from. Here are the acceptable permissions in this new setup: PHP Scripts: 644 Directories: 755 For the most part this should not be an issue unless you've been changing permissions of folders when it was unnecessary. We will be running scripts to attempt to fix permissions. With that we'll also be logging all errors relating to permissions in hopes of solving any that are popping up. The other issue with suPHP is you can no longer change php configuration values (such as register_globals) in a .htaccess. This will now need to be done by placing a php.ini in the folder that this change needs to be made. You will also use standard PHP notation opposed php_flags that can be used in .htaccess files. If you have any questions do not hesitate to contact support. Date: 12/21/2007 Start time (EST): 11:00am End time (EST): 12:00pm Duration: 60 minutes

On Friday December 21st at 10am EST we will be upgrading the Mars server's apache version to 2.2 from the currently running 1.3 branch. We expect this migration to take about an hour to do. We do not expect any down time during this migration. We've been running Apache 2.2 on our Venus server for over a month now without issue. It has brought much better performance and made our management of the server much easier. We'll also be switching to suPHP which will make things much less complicated with regards to permissions of files. 777 files permissions will no longer work and 755 will be the maximum needed for php scripts to access files on your sites. Here is a quick summary of the new features and any problems you may encounter. Apache 2.2 Apache 2.2 has much better resource management. As a result it can much better serve static content. Static content would be things like images, files ect. This should not be confused with PHP or CGI scripts which are not static at all. As for problems this may cause we do not expect any at all. suPHP suPHP is a much more secure PHP setup. It has all PHP scripts running as the user. This means that there are no issues with uploading of content and another user owning the files. It also restricts the acceptable permissions for files which is where we expect the majority of problems to come from. Here are the acceptable permissions in this new setup: PHP Scripts: 644 Directories: 755 For the most part this should not be an issue unless you've been changing permissions of folders when it was unnecessary. We will be running scripts to attempt to fix permissions. With that we'll also be logging all errors relating to permissions in hopes of solving any that are popping up. The other issue with suPHP is you can no longer change php configuration values (such as register_globals) in a .htaccess. This will now need to be done by placing a php.ini in the folder that this change needs to be made. You will also use standard PHP notation opposed php_flags that can be used in .htaccess files. If you have any questions do not hesitate to contact support. Date: 12/21/2007 Start time (EST): 10:00am End time (EST): 11:00am Duration: 60 minutes

The easiest way is to login to 1and1 and and find the option to change name servers. From there simply put in: ns1.hawkhost.com ns2.hawkhost.com If you're looking to transfer the domain registration to us then you'd need an authorization code if it's a .com or .net and you should be asked for that at the order form.

This has been completed.

On Wednesday November 27th between 5pm and 7pm EST (GMT -5) we will be performing maintenance on our Bosco server which contains backups for all servers. During this time pre made backups will be unavailable as the server will be off line. We're sorry about any inconvenience this may cause. If you have any concerns please contact support. Date: 11/27/2007 Start time (EST): 5:00pm End time (EST): 7:00pm Duration: 120 minutes

The Mars server kernel has been upgraded. It took slightly longer than expected as the machine wanted to due a simple fsck on the drives once it rebooted. This was most likely due to it not shutting down fully as a result it had to check it's files. No data was lost during the fsck so it simply meant it took 12 minutes to reboot opposed to 5 minutes.

The Mercury server is now running the latest kernel. It took about 10 minutes to fully reboot and have all services running again. We're very sorry about the incorrect estimation on the amount of time it would be down.

On Monday November 5th between 10:30am EST and 11:00am EST we will be upgrading the kernel of the Mars server. We expect this to take under 30 minutes to complete with about 5 minutes of down time while we reboot the server. The reason for the kernel upgrade is for the machine to receive the latest performance increases, bug fixes, feature enhancements and security fixes. If you have any questions or concerns about this maintenance do not hesitate to contact our support department. Date: 11/05/2007 Start time (EST): 10:30am End time (EST): 11:00am Duration: 30 minutes Expected Down Time: 5 minutes

On Monday November 5th between 9:30am EST and 10:00am EST we will be upgrading the kernel of the Mercury server. We expect this to take under 30 minutes to complete with about 5 minutes of down time while we reboot the server. The reason for the kernel upgrade is for the machine to receive the latest performance increases, bug fixes, feature enhancements and security fixes. If you have any questions or concerns about this maintenance do not hesitate to contact our support department. Date: 11/05/2007 Start time (EST): 9:30am End time (EST): 10:00am Duration: 30 minutes Expected Down Time: 5 minutes

This work has been completed.

Date: 11/1/2007 Start time (EDT): 5:00am End time (CDT): 7:00am Services affected: Level3 Backbone Location: cer01.dal01 Duration: 2 hour ------------------------------------------------------------------------- Level (3) Communications - Network Change Control (NCC) Clarify Case#: 2155595 GCR #: CHG000000165672 Primary Dates: 1 Nov 2007 04:00:00 - 1 Nov 2007 06:00:00 Central Location of Maintenance: Dallas, TX Summary Description of Maintenance: Upgrade - Code - Router Customer Impact: Level 3 will upgrade routers which will cause an outage to customers and peers while unit reloads. Services Impacted: Softlayer 10G Dallas circuit -------------------------------------------------------------------------- During Level3's router maintenance, network technicians will shut down BGP to avoid service interruption which will cause routing to shift to our other providers. Once they have concluded their network maintenance, Engineers will turn BGP back on the them thus restoring full connectivity. If you have any problems after this time frame with regard to connectivity, or if you have any questions regarding the maintenance at any point, please open a support ticket. We appreciate your patience during this work and welcome any feedback.

At this point it only provides interface via gui due to the fact it installs the modules on your account opposed to globally. As for if it works in cPanel it should be working fine.