• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved [Plesk Repair Utility] Unable to repair incorrect permissions

Justin

New Pleskian
Hi guys,

I encounter these errors on one of my servers when I used the Plesk Repair Utility to repair permissions on some of the domains.

I did:
Code:
#plesk repair fs -verbose

Outputs on domains with permission errors:
#There are incorrect permissions on some items in the system

directory for the domain 'domain.com' ........................ [ERROR]

- Failed to stat

/var/www/vhosts/system/domain.com/conf/httpd.conf: No such

file or directory

Failed to stat

/var/www/vhosts/system/domain.com/conf/nginx.conf: No such

file or directory

Do you want to repair incorrect permissions? [Y/n] Y

Repairing incorrect permissions ................................. [FAILED]

- openat 'conf' failed: Too many levels of symbolic links

Failed to open safely

/var/www/vhosts/system/domain.com/conf: Too many levels of

symbolic links

open_basedir_with_nofollow: opeat failed: `conf', Too many

levels of symbolic links

open_basedir_with_nofollow failed

Failed to open safely

/var/www/vhosts/system/domain.com/conf/httpd.conf: Too

many levels of symbolic links

open_basedir_with_nofollow: opeat failed: `conf', Too many

levels of symbolic links

open_basedir_with_nofollow failed

Failed to open safely

/var/www/vhosts/system/domain.com/conf/nginx.conf: Too

many levels of symbolic links

Outputs on one of the domain:
Failed to stat /var/www/vhosts/domain2.com/httpdocs/./data/VERSION: Permission denied

Failed to stat /var/www/vhosts/domain2.com/httpdocs/./data/EMPTY: Permission denied

I tried using the transvhost.pl to correct the symbolic link stated in one of the plesk documentation [don't remember link].

I did:
Code:
perl transvhosts.pl --dest-dir /var/www/vhosts/ --correct-scripts

Output:
Code:
server is already configured.

How can I resolve this?

Any help would be greatly appreciated!
 
Geez, Peter, you saved the day again! That one sentence of yours inspired me to dig around and fixed the problem!

After digging around /var/www/vhosts/system/ for a while, I realized the 'conf' folder in all the domains became symbolic links instead of a real directory. The reason why this might have happened is that I used transvhosts.pl and moved the vhosts to the 'home' partition but then I moved it back to /var/www/vhosts/system/.

I move it back because all my production sites went down with a 500 Internal error. So I freaked out and moved everything back. Then it caused a whole new set of problems from corrupted vhosts structures to messed up permissions. The permission of the "system" folder in vhosts somehow changed to a user on one of my sites instead of root. (e.g jason:jason instead of root:root) Crazy stuff!

So I did
chown -R root:root /var/www/vhosts/system/

and

delete all 'conf' symbolic links and move the 'conf' folder from 'home' partition to each domain.

cd /home/www/vhost/system/domain.com/
mv * conf /var/www/vhosts/domains.com/

then

plesk repair fs -verbose

Everything is fixed!

Thanks, Peter! It was a good learning experience.
 
Last edited:
Back
Top