fedora core 3 out of the box, chmod 777, but.. - Page 2 fedora core 3 out of the box, chmod 777, but.. - Page 2
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

fedora core 3 out of the box, chmod 777, but..

Started by kugelmoped, February 08, 2005, 02:35:20 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Joachim Müller

whoa, next time you post such a large file as your config, please just attach it to your posting instead of copying the contents into several postings - this clutters the thread and the db...

Joachim

vanders

Hey, vanders here, I just set up a webserver using the latest fedora core, 3. I'm having exactly the same problem here, just confirming that this poor guy isn't the only one out there who is confused... has anything been resolved?

pacman

i am installing coopermine fiirst time here too and i had this problem with fedora 3  but i updated the system and now it works fine.  ;D

meios4us

I got this problem for 2 days :)
I don't know if this will help you solve it but for me it worked fine. I run Fedora Core3 with apache 2.0 and php4.3.10.
After chmod-ing to 777 and tryed 755 as manual say, i made a test.php as someone suggested here and saw that permissions wasn't correctly read by php.

My solution:

# service httpd restart

I dont know very well why this solved the issue but now i am happy. :) Everything is ok.

grapesmc

#24
Sure enough, I have the same exact problem. Permissions set to both 777 and 775 - I even removed the "test" part of the install.php to see what would happen, and although I can get past it then, it still can't write to include/ .
Fedora Core 3
php-4.3.11-2.4
httpd-2.0.52-3.1
owner/group is apache/apache which is what the server runs as.
If anyone finds an actual answer, I'd love to hear it. I am running plenty of other PHP-MySql-based things with no issues.

-- UPDATE
ok, so it was selinux that was causing the issue. I haven't learned how to tweak it to work properly, but you can disable it on the httpd daemon.

First run sestatus, you should see this line:

httpd_disable_trans     disabled

then edit:
/etc/selinux/targeted/booleans

and change the line: httpd_disable_trans=0 to httpd_disable_trans=1

run sestatus again you should see

httpd_disable_trans     active

Ok-  you're almost there. Now restart apache

/sbin/servicec httpd restart

now go to the install.php page and you should be golden. If I figure out how to run selinux with httpd properly I'll let everyone know. Also, there was a  link above that led to a good post that led me to the selinux config issue and said to disable with the GNOME gui that Fedora includes. Since like many of you I don't run a GUI on the server and only have console abilities (I know I could export X and use the GUI tools, but hey) I wanted to detail what to edit. If you have access to the GUI, you can just adjust the policy with that and it will do the same exact thing I assume.

redtroll

I had the exact same problem as above, and as grapesmc said - it is SELinux that is the problem.
The above solution did not help me, I had to disable SELinux:

Add SELINUX=disabled to your /etc/sysconfig/selinux file (which may be a link to "/etc/selinux/config"), the reboot.

goodnight2

Just as a followup, you can truly fix the problem without disabling SELinux.  Simply use restorecon:

[root@server]# restorecon -R /var/www/