Hi All,
I am currently am responsible for maintaining a website built on Apache 2, running on some CentOS 4 (64 bit version) boxes. Thus far, the website has comprised a few HTML pages, and some dynamic pages generated by perl scripts. The CentOS install is pretty vanilla -- the only departure I've made from the default server install is to install awstats from the rpmforge repositories.
This week, I tried to install Wordpress, and have run into a brick wall that several days of experimentation and deep consultation with Google have been unable to get me over.
Here's the situation: I installed the mysql, mysql_server, and php packages, unpacked the Wordpress tarball into a "blog" directory, and make the necessary changes to wp-config.php. The MySQL database works just fine, and when I visit the blog directory, index.php runs and informs me that I need to surf over to install.php to complete the WordPress configuration, which is expected.
But when I try to browse to install.php, Firefox gives me the option to save it, or run it locally -- it doesn't seem to want to run as a server side script, for some reason.
I don't see any obvious issues with my php installation that would cause this -- /etc/httpd/conf.d/php.conf is in place, is loading module_php4, and has added a php application type to the apache setup. I did remember to restart the http daemon after installing php. I don't see any errors in the logs -- all I see in the apache logs is a GET request for install.php.
The really confusing thing is that one php script -- index.php -- works just fine, while another php script -- install.php -- does not.
Has anybody run into a similar problem with WordPress, or with php4 in general? It feels like I'm running afoul of some bit of overzealous security that's trying to stop php from doing Bad Things to the system, but, sans error messages, it's been difficult to figure out what bit of security might be responsible, and how I might go about coaxing CentOS into allowing me to run WordPress.
And so I have come here to tap into the wisdom of the mailing list. Might anybody here have some hints as to what I might do to solve this puzzle?
Thank you,
have you created a virtual server in apache yet?
frnakly? I would install the rpmfogre repo and then yum instlal webmin. Then goto webmin.com and dlownload and install virtualmin. Virtualmin will tlel you what errors you ahve in your setup and fixing them is usually yum install <whatever>
petevg@gmail.com wrote:
Hi All,
I am currently am responsible for maintaining a website built on Apache 2, running on some CentOS 4 (64 bit version) boxes. Thus far, the website has comprised a few HTML pages, and some dynamic pages generated by perl scripts. The CentOS install is pretty vanilla -- the only departure I've made from the default server install is to install awstats from the rpmforge repositories.
This week, I tried to install Wordpress, and have run into a brick wall that several days of experimentation and deep consultation with Google have been unable to get me over.
Here's the situation: I installed the mysql, mysql_server, and php packages, unpacked the Wordpress tarball into a "blog" directory, and make the necessary changes to wp-config.php. The MySQL database works just fine, and when I visit the blog directory, index.php runs and informs me that I need to surf over to install.php to complete the WordPress configuration, which is expected.
But when I try to browse to install.php, Firefox gives me the option to save it, or run it locally -- it doesn't seem to want to run as a server side script, for some reason.
I don't see any obvious issues with my php installation that would cause this -- /etc/httpd/conf.d/php.conf is in place, is loading module_php4, and has added a php application type to the apache setup. I did remember to restart the http daemon after installing php. I don't see any errors in the logs -- all I see in the apache logs is a GET request for install.php.
The really confusing thing is that one php script -- index.php -- works just fine, while another php script -- install.php -- does not.
Has anybody run into a similar problem with WordPress, or with php4 in general? It feels like I'm running afoul of some bit of overzealous security that's trying to stop php from doing Bad Things to the system, but, sans error messages, it's been difficult to figure out what bit of security might be responsible, and how I might go about coaxing CentOS into allowing me to run WordPress.
And so I have come here to tap into the wisdom of the mailing list. Might anybody here have some hints as to what I might do to solve this puzzle?
Thank you,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
petevg@gmail.com wrote:
I don't see any obvious issues with my php installation that would cause this -- /etc/httpd/conf.d/php.conf is in place, is loading module_php4, and has added a php application type to the apache setup. I did remember to restart the http daemon after installing php. I don't see any errors in the logs -- all I see in the apache logs is a GET request for install.php.
What about permissions? Are all of the permissions ok in the directory? I run Wordpress on CentOS, but it's been forever since I did an install. When I did, though, I don't remember any issues with the install.php script. I frequently upgrade as well.
Let me know if there is anything I can compare on my installation with yours.
Regards, Max
On 6/8/07, petevg@gmail.com petevg@gmail.com wrote:
But when I try to browse to install.php, Firefox gives me the option to save it, or run it locally -- it doesn't seem to want to run as a server side script, for some reason.
What Content-Type is associated with each HTTP response? What do you handler directives look like? Are they enclosed in a Location or Directory stanza? Are the permissions set correctly on the files and directories?
I did remember to restart the http daemon after installing php. I don't see any errors in the logs -- all I see in the apache logs is a GET request for install.php.
You can get additional information by setting the Apache LogLevel to debug and by adjusting the php.ini display_errors directive.
- Ryan
On 6/9/07, Matty matty91@gmail.com wrote:
You can get additional information by setting the Apache LogLevel to debug and by adjusting the php.ini display_errors directive.
Okay, so sometimes I'm an idiot. Here's the error message that I got after turning debugging on:
"PHP Fatal error: Allowed memory size of 8388608 bytes exhausted "
The solution was ridiculously simple: increase the "memory_limit" in /etc/php.ini from 8M to 12M, and restart the http daemon.
Thank you all for the quick and detailed responses to my question :-)
-
Matty -
Max Hetrick -
petevg＠gmail.com -
William Warren