Installation, Configuration, & Upgrades  :: 
can't get past the CHMOD Check on install
 Top

  • Apache/2.0.52 (Fedora) Server
    PostNuke-0.750.tar
    /var/www/html


    -rw-rw-rw- 1 root root 3900 Apr 13 2004 config-old.php
    -rw-rw-rw- 1 root root 3917 Jan 30 16:43 config.php
    but I still get the CHMOD Check errors....


    I believe this is an environment variable path problem, since in the httpd
    error_log I see
    [Sun Jan 30 21:18:13 2005] [error] [client 192.168.1.101] File does not exist: /var/www/html/favicon.ico

    and I would think favicon.ico should be preceeded by the land subpath..

    I fixed the magic_quotes problem by turning magic_quotes_gpc = On in
    php.ini

    what can I do next?
    I can't get past CHMOD Check to complete the install...


    >>Not Good! magic_quotes_gpc is Off.
    >>This can often be fixed using a .htaccess file with the following line:
    >>php_flag magic_quotes_gpc On
    >>CHMOD Check
    >>
    >>We will first check to see that your file permissions are correct in order for the script to
    >>write to the file. If your settings are not correct, this script will not be able to encrypt
    >>your data in your config file. Encrypting the SQL data is added security, and is set by
    >>this script. You will also not be able to update your preferences from your admin once
    >>your site is up and running.
    >>
    >>Please change permissions on config.php to 666 so this script can write
    and encrypt the DB data (HINT: use "chmod")

    etc....
  • pnWannb


    I believe this is an environment variable path problem, since in the httpd
    error_log I see
    [Sun Jan 30 21:18:13 2005] [error] [client 192.168.1.101] File does not exist: /var/www/html/favicon.ico

    No, certain browsers look for favicon.ico in the root directory. I bet you use firefox :)

    anyway who owns the rest of /var/www/html? is it apache, root, www-data, or something else entirely?

    try chown'ing the configs.php
  • Firefox yes,
    you quiero Firefiox....

    who should the owner be?
    this is just freaky...

    -rw-r--r-- 1 root root 3724 Aug 22 20:56 admin.php
    -rw-r--r-- 1 root root 6249 Aug 23 11:01 backend.php
    -rw-r--r-- 1 root root 16610 Jun 1 2004 banners.php
    -rw-rw-rw- 1 root root 3900 Apr 13 2004 config-old.php
    -rw-rw-rw- 1 root root 3917 Jan 30 16:43 config.php
    drwxr-xr-x 2 root root 4096 Sep 1 19:31 docs
    -rw-r--r-- 1 root root 3819 Aug 14 15:18 error.php
    -rw-r--r-- 1 root root 3638 Jun 9 2004 favicon.ico
    -rw-r--r-- 1 root root 3403 Aug 10 12:16 footer.php
    -rw-r--r-- 1 root root 70 Jan 30 16:19 getpnsak
    -rw-r--r-- 1 root root 5137 Aug 17 14:38 header.php
    -rw-r--r-- 1 root root 29 Jan 30 14:22 .htaccess
    drwxr-xr-x 12 root root 4096 Sep 1 19:31 images
    drwxr-xr-x 7 root root 4096 Sep 1 19:32 includes
    -rw-r--r-- 1 root root 4512 Aug 22 20:03 index.php
    drwxr-xr-x 5 root root 4096 Jan 30 15:09 install
    -rw-r--r-- 1 root root 16423 Apr 22 2004 install.php
    drwxr-xr-x 3 root root 4096 Sep 1 19:32 javascript
    drwxr-xr-x 3 root root 4096 Sep 1 19:32 language
    -rw-r--r-- 1 root root 1401 Apr 22 2004 mainfile.php
    drwxr-xr-x 51 root root 4096 Sep 1 19:32 modules
    -rw-r--r-- 1 root root 381 Mar 25 2004 modules.php
    drwxr-xr-x 2 root root 4096 Jan 30 18:44 nuke
    -rw-r--r-- 1 root root 67766 Sep 1 15:19 Phoenix-0.7.5.0.sql
    -rwxr-xr-x 1 root root 18 Jan 30 18:45 phpinfo.php
    drwxr-xr-x 12 root root 4096 Sep 1 19:32 pnadodb
    -rw-r--r-- 1 root root 44999 Apr 22 2004 pntables.php
    drwxr-xr-x 10 root root 4096 Sep 1 19:32 pnTemp
    drwxr-xr-x 2 root root 4096 Jan 30 14:48 PostNuke-0.750
    -rw-r--r-- 1 root root 10743 Aug 17 13:28 print.php
    -rwxr-xr-x 1 root root 15292 Jan 30 16:37 psak.php
    -rwxrwxr-x 1 brian brian 15346 Jun 16 2003 psak.php.orig
    -rw-r--r-- 1 root root 4532 Aug 20 16:50 referer.php
    -rw-r--r-- 1 root root 276 May 12 2004 robots.txt
    drwxr-xr-x 9 root root 4096 Sep 1 19:32 themes
    -rw-r--r-- 1 root root 3664 Aug 22 20:21 user.php
    -rw-r--r-- 1 root root 1723 Apr 22 2004 xmlrpc.php
    [root@sinkhole HTML]#

    tried
    apache root
    and
    apache apache

    but get same error
  • $cat /etc/apache/httpd.conf | grep User
    $cat /etc/apache/httpd.conf | grep Group

    (replace /etc/apache/httpd.conf with whereever your httpd.conf file is)
  • right
    apache apache ....
    didn't help.. crap...

    [root@sinkhole /]# cat /etc/httpd/conf/httpd.conf | grep User
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # . On SCO (ODT 3) use "User nouser" and "Group nogroup".
    User apache
    # UserDir: The name of the directory that is appended onto a user's home
    # UserDir is disabled by default since it can confirm the presence
    UserDir "disable"
    # directory, use this directive instead of "UserDir disable":
    #UserDir public_html
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%{User-agent}i" agent
    [root@sinkhole /]# cat /etc/httpd/conf/httpd.conf | grep Group
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # . On SCO (ODT 3) use "User nouser" and "Group nogroup".
    # NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
    # when the value of (unsigned)Group is above 60000;
    # don't use Group #-1 on these systems!
    Group apache
    [root@sinkhole /]#
  • does apache have to have an account?
    This path shows promise, but I restarted httpd and everything..
  • Xanthia needs some chmods too
  • [root@sinkhole Xanthia]# ls -la
    total 448
    drwxr-xr-x 11 root root 4096 Sep 1 19:32 .
    drwxr-xr-x 51 apache apache 4096 Sep 1 19:32 ..
    -rw-r--r-- 1 root root 0 Aug 16 16:08 index.html
    drwxr-xr-x 3 root root 4096 Sep 1 19:32 plugins
    -rw-r--r-- 1 root root 103100 Aug 16 16:08 pnadminapi.php
    -rw-r--r-- 1 root root 146335 Aug 26 12:43 pnadmin.php
    drwxr-xr-x 2 root root 4096 Sep 1 19:32 pnblocks
    drwxr-xr-x 2 root root 4096 Sep 1 19:32 pnclasses
    drwxr-xr-x 4 root root 4096 Sep 1 19:32 pndocs
    drwxr-xr-x 2 root root 4096 Sep 1 19:32 pnhtml
    drwxr-xr-x 2 root root 4096 Sep 1 19:32 pnimages
    -rw-r--r-- 1 root root 31016 Aug 16 16:08 pninit.php
    drwxr-xr-x 3 root root 4096 Sep 1 19:32 pnlang
    drwxr-xr-x 2 root root 4096 Sep 1 19:32 pnstyle
    -rw-r--r-- 1 root root 9075 Aug 16 16:08 pntables.php
    drwxr-xr-x 3 root root 4096 Sep 1 19:32 pntemplates
    -rw-r--r-- 1 root root 25595 Aug 16 16:08 pnuserapi.php
    -rw-r--r-- 1 root root 2433 Aug 16 16:08 pnversion.php
    [root@sinkhole Xanthia]# chmod 666 *

    no change in behavior of CHMOD Check
  • /var/www/html/pnTemp apache:apache
    ./var/www/html/modules/Xanthia apache:apache
    chmod 666
    restart
    no change in behavior...
  • uhh, try chmod 777
  • duh... cool, I didn't like the 666 anyway... that's a microsoft number.
    ok, I'll try 777.. and in the mean-time, is there any install.log or way to trace install or turn up verbosity?
    It would be nice to see exactly which command is failing and in what context..
  • shoot... I was hoping that was it.
    nope.
    I tried it slectively, no good.
    then I did it recursively,
    no good
    /var/www/html/modules/Xanthia
    chmod -R 777 *
    /var/www/html/pnTemp
    chmod -R 777 *
    restart httpd
  • Found the solution!
    And I see that others using Fedora Core 3 with SELinux are having the same problem.
    So now I must just ensure my network is very secure and turn off SELinux to get PostNuke to work.

    http://fedora.redhat.com/docs/selinux-faq-fc3/index.html#id2825232
    One method is to use system-config-securitylevel to change the policy
    and set the file system to relabel.

    Following is the manual procedure:

    1. Edit /etc/selinux/config and change the type of policy to
    SELINUXTYPE=policyname.
    2. To ensure that you can return from a reboot, set the mode
    to SELINUX=permissive. This way SELinux will be running under the
    correct policy, but will let you login if there is a problem such as
    incorrect file context labeling.
    3. Tell the init scripts to relabel the system on reboot with
    the command touch /.autorelabel.
    4. Reboot the system. A clean restart under the new policy
    allows all system processes to be started in the proper context, and
    reveals any problems in the policy change.
    5. Confirm your changes took effect with the command sestatus
    -v. With the new system running in permissive mode, check
    /var/log/messages for avc: denied messages. These may indicate a
    problem that needs to be solved for the system to run without trouble
    under the new policy.
    6. When you are satisfied that the system runs stable under
    the new policy, enable enforcing by changing SELINUX=enforcing. You
    can either reboot or run setenforce 1 to turn enforcing on in real
    time. icon_lol icon_lol icon_lol
This list is based on the users active over the last 60 minutes.