1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Reset /var/www permissions

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by dbasch, Aug 6, 2011.

  1. dbasch

    dbasch Guest

    0
     
    I did something less than smart and changed the permissions on the /var/www directory.

    I managed to fix the permissions on the vhost subfolders using vhostmng.

    I don't know how to fix the non-vhost /var/www permissions though.

    This obviously causes problems with things like cgi_wrapper, atmail, etc..

    Anyone know how to reset the non-vhost /var/www/* permissions?

    Thanks!
     
  2. matt-clements

    matt-clements Guest

    0
     
    Is this just the permissions? Or owners as well?

    What version of Plesk are you using, and the OS?
     
  3. dbasch

    dbasch Guest

    0
     
    Sorry, I should have given more information

    I changed the permissions and the owner.

    I am running Plesk 9.3.0 on Linux Cent OS.

    Thanks for the help!
     
  4. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
  5. dbasch

    dbasch Guest

    0
     
    Hi Igor,

    Unfortunately, that only restores the owners and permissions for the individual virtual host directories.

    My problem is the /var/www directory.

    Cheers,
    Derek
     
  6. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Find a packet to which files or directories belongs with

    # rpm -qf /var/www/some_file

    for example and then set all default permissions for files from this package with

    # rpm --setperms package_name.rpm
    # rpm --setugids package_name.rpm
     
  7. dbasch

    dbasch Guest

    0
     
    I gave the rpm package permissions a try, but the files are not owned by a package:

    file /var/www/cgi-bin/cgi_wrapper/cgi_wrapper is not owned by any package

    file /var/www/atmail/reademail.php is not owned by any package

    Thanks for all the help everyone.

    Hopefully I can get this fixed.
     
  8. dbasch

    dbasch Guest

    0
     
    I have more information on my problem.

    I believe that I have now fixed the owner and permissions on the /var/www directory and non vhost subdirectories.

    I still get suexec FCGI errors.

    I am trying to execute PHP files from a subdomain with the default Apache configuration:
    This is the suexec error:
    Executing the root vhost CGI test file of http://example.com/cgi-bin/test/test.cgi works correctly. It does not use the CGI wrapper:

    I have tried the fixes listed here but they did not work:
    http://kb.odin.com/en/430

    This seems to be a problem specific to executing PHP files that use the CGI wrapper.
     
    Last edited by a moderator: Aug 9, 2011
  9. dbasch

    dbasch Guest

    0
     
    I did a lot of research and it appears I am having a common problem:

    http://kb.odin.com/article_52_430_en.html

    I tried all of the fixes listed here but nothing seems to work.

    I think I will have to do a full reinstall to fix the problem :(
     
  10. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    What about contacting Parallels Support Team instead of reinstallation?
     
  11. dbasch

    dbasch Guest

    0
     
    My license key does not offer support. I will try to submit it to my host.
     
  12. dbasch

    dbasch Guest

    0
     
    My host could not fix the problem either. I was forced to start fresh with a new Plesk 10.1 instance. Frustrating.
     
Loading...