Apache on Linux gurus, I need your help

[TheFishingGeek]

My latest adventure will consist of running Apache v 1.3.27 on a RAID 5 array that I have spun up at home. I've got Apache working just fine using /var/www/html as the default document directory, but when I try and use the mount that the RAID is located on (/mnt/array/www/html) and restart Apache I get a "You don't have permission to access (pagename) on this server".

I tried to replicate the file ownership and read/write permissions from /var/www/html to the new directory, same problem. Everything in the /mnt/array/www directory is owned by apache.apache, and out of desperation I chmodded everything 777 (I won't keep it there, just did it for troubleshooting). Still gave me the same error after a forced page reload. When I change the document root back to /var/www/html everything is fine.

Another attempt was to create a Virtual Server, but I had the same problem so I killed that one.

So what am I missing? Is there something else to change other than the Default Document Directory that I'm missing? Or should I just zap the /var/www/html directory and remount the RAID array at /var/www/html, and would that work?

Thanks for the help, as always.

 

[Soybomb]

did you just chmod the uppermost directory? If you just changed the directory without the -R option the file might have permission problems even if the directory doesn't. Be sure the file you're trying to view has at least 644

 

[TheFishingGeek]

I -R'ed the whole lot of them. I just did a chown -R apache.apache /mnt/array/www and a chmod -R 755 /mnt/array/www and still had the same 403 Forbidden come up. Frustrating little devil.

 

[TheFishingGeek]

Here's how I fixed this one. It was interesting:

The first thing that I did was go ahead and mount my array as /var/www after blowing away the original /var/www directory. While the mount worked fine, it still wasn't allowing cgi's to run. After some frustrating misdirections I discovered that when Mandrake was mounting that array that it was adding a special flag that kept code from being allowed to be executed on that array. Well, after turning off that flag and remounting the drive, everything worked great. CGIs are running happily now, and now I can go find something else to break.

 

[Barnaby W. Füi]

Ah, noexec

You're on quite a roll lately

 

[TheFishingGeek]

I simply couldn't let that RAID 5 array just sit there and add 5°F to my house temperature without it doing something meaningful, and as I'm tired of getting those daily alerts from Dixiesys that the combined total of my website and the backups are over the 200 meg limit I figured that this would be a good thing to do with it.

I'll probably go and install Gallery for my "family photos" (did you know that I have roughly 150 sisters in the adult erotica business? Yep!)