Snowman
23-07-2005, 01:56 PM
Due to security reasons we will be upgrading apache and PHP on all machines over the next week, commencing Monday night.
PHP will be changed to a CGI Module and will be running PHPSuexec.
There may be a minmal downtime of around 5-10 minutes during the upgrade.
All servers will be done one at a time with the planned schedule being:
THREDBO - Monday Night
PERISHER - Wednesday Night
HOTHAM - Thursday Night
BULLER - Saturday Night
FALLS CREEK - Sunday Night
ASPEN - Monday Night (following week)
A post will be placed in each server forum shortly about the upgrade, and notices will be posted prior to and after the completion of the upgrade of each server.
IMPORTANT NOTICE
The reason for php running as a cgi rather than apache module is to increase security with running your php applications.
PHP as a cgi with phpsuexec - What is the difference?
Most sites will not be affected with the change, running php as a cgi with suexec. Phpsuexec works in much the same way that cgi with suexec does, all applications being run under your account user name, rather than in php's case as an apache module, the user "nobody".
This simply means that rules that apply to .cgi + .pl files on your current server, apply to php files also - The maximum permissions permitted on directories and .php files is 755. Failing to have have permissions set to a maximum of 755 on php files and their installation paths, will result in a 500 internal server error, when attempting to execute them.
If you have php applications/scripts that have directories set to 777, (required to write to them under php/apache module), they would need to be changed - Also we would need to change ownerships of all files owned by user nobody to the user name for your account.
.htaccess
You cannot manipulate the php.ini settings with .htaccess when running php as a cgi/phpsuexec.
If you are using .htaccess with php_ entries within it, you would receive an internal server 500 error when attempting to access the scripts. All php values should be removed from your .htaccess files to avoid this issue.
We will be running through and changing incorrect permissions on php files and ownerships on "nobody" owned php files files for you also - There may be a few cases where you may need to submit a helpdesk ticket if you need ownerships of files changing to your account user name.
We thank for your understanding and co operation during this upgrade and migration to php running with phpsuexec.
If you have any further questions, please feel free to ask about them in this discussion.
PHP will be changed to a CGI Module and will be running PHPSuexec.
There may be a minmal downtime of around 5-10 minutes during the upgrade.
All servers will be done one at a time with the planned schedule being:
THREDBO - Monday Night
PERISHER - Wednesday Night
HOTHAM - Thursday Night
BULLER - Saturday Night
FALLS CREEK - Sunday Night
ASPEN - Monday Night (following week)
A post will be placed in each server forum shortly about the upgrade, and notices will be posted prior to and after the completion of the upgrade of each server.
IMPORTANT NOTICE
The reason for php running as a cgi rather than apache module is to increase security with running your php applications.
PHP as a cgi with phpsuexec - What is the difference?
Most sites will not be affected with the change, running php as a cgi with suexec. Phpsuexec works in much the same way that cgi with suexec does, all applications being run under your account user name, rather than in php's case as an apache module, the user "nobody".
This simply means that rules that apply to .cgi + .pl files on your current server, apply to php files also - The maximum permissions permitted on directories and .php files is 755. Failing to have have permissions set to a maximum of 755 on php files and their installation paths, will result in a 500 internal server error, when attempting to execute them.
If you have php applications/scripts that have directories set to 777, (required to write to them under php/apache module), they would need to be changed - Also we would need to change ownerships of all files owned by user nobody to the user name for your account.
.htaccess
You cannot manipulate the php.ini settings with .htaccess when running php as a cgi/phpsuexec.
If you are using .htaccess with php_ entries within it, you would receive an internal server 500 error when attempting to access the scripts. All php values should be removed from your .htaccess files to avoid this issue.
We will be running through and changing incorrect permissions on php files and ownerships on "nobody" owned php files files for you also - There may be a few cases where you may need to submit a helpdesk ticket if you need ownerships of files changing to your account user name.
We thank for your understanding and co operation during this upgrade and migration to php running with phpsuexec.
If you have any further questions, please feel free to ask about them in this discussion.