Good morning ....
I moved the whole .gz file over to the destination server. Then I untarred the file on the destination server. No FTP was involved, so I know all the files are there.
I am running Apache/PHP as root ... this is a development shared server that no one else is using ... so no one gets hurt. ;-) Since I installed Apache/PHP with mysql support via packages ... things are a little all over the place. Believe it or not ... the Apache document root turned out to be: /var/www/html and drupal is installed under /var/www/html/drupal .... (where I untarred it) All these files then should be owned by root ... I will change that and then check permissions.
I gotta tell ya ... since Resin has a ready web-server and PHP implemented via Java. Getting Resin/Drupal and the database setup took no more than 10 minutes. And I thought I was making great head-way ....
Anyway, I'll make these changes and try again ... I'll let you know how I make out now that Apache/PHP is out of the way.
Thanks again! Tom
sander-martijn wrote:
Did you untar drupal on the server or untar it locally and then ftp the files up? I've had errors like this because I did the latter and ftp timed out on some of the files. You can do it through ftp but you might have to go through directories and make sure all the files are there.
Also check permissions, make sure you hae something like 775 on directories and 644 on files and that the files and folders are in the same group as php runs as.
.s
Tom Holmes Jr. wrote:
updated memory issue ... but I get this error before I can even logon:
PHP Fatal Error: Call to undefined function: user_access() in /var/www/html/drupal/modules/block/block.module on line 68 .....
sander-martijn wrote:
Yeah that could very well be a memory issue.
you saw this page i assume? http://drupal.org/node/29268
Tom Holmes Jr. wrote:
The Drupal database screen came up .... the Advanced Options did work for Apache (doesn't in resin causing you to change the db_url in settings.php manually). The settings.php did update to the correct db_url and accordinly change permissions on the file.
The result was the "white screen of death" ... no problem ... I'll research this myself ... It seems like it maybe some kind of memory issue set in php.ini .... If anyone wants to help, that's great ... just ask me for any information. Otherwise I will continue to research .....
Thanks! Tom
Tom Holmes Jr. wrote:
Yeah ... I took this completely off the list ... I figured installing Apache/PHP with MySql support is NOT a Drupal issue. I thought that was appropriate ... Yep, I was googling for "Apache MySQL PHP Centos" to find a link that gave me that kind of information.
I did find your link helpful, I don't have direct access to the CentOS machine since that machine is in a data-center altogether. I did run through the instructions from that link on page 5 for apache/php. And now I have the Apache 2.0.x with PHP 4.3.9 installed.
This type of installation seems to install data/apps ALL over the place ... but that is an issue with CentOS and not Drupal. I'm used to not installing Apache/PHP on my Linux systems with the install because of that. I like to install apps where I want them to be. And kinda keep the apps together neatly. So I usually download and install the OS is installed.
I am testing out the PHP now anyway ... and it seems to work: index.php looks like; <? phpinfo() ?> And I get all the php information displayed .... including all the way down that mysql support is enabled. Now I can copy over the latest install of Drupal 5.3.
Thanks .....
Anton wrote:
On 06/12/2007, Tom Holmes Jr. tom@tomholmes.net wrote:
> Oh yeah, I forgot about 'yum' ... i usually do yast2 on my Suse systems > at home, but this server machine is CentOS. > > > > There is this tutorial, but it's pretty long winded and overkill in terms of the packages installed - you'll probably want to skip over the non PHP/Apache/MySQL parts.
http://www.howtoforge.com/perfect_server_centos4.5
Section 9 & 11 should be enough for you. Even then they install more packages that you really need, but I wouldn't worry about that for now.
It's best to just stick to the versions Centos installs rather than compiling your own.