• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Plesk Onyx and Centos 7: transvhost.pl breaks all of my websites

Paul Larson

Basic Pleskian
OS: CentOS Linux 7.4.1708 (Core)‬
Plesk: Onyx Version 17.5.3 Update #23, last updated on Sept 30, 2017 02:04 PM

Installed CentOS on an office PC to try a local Plesk. I'm within the 15 day trial, in case that means anything.

Everything is great!

However, I realized the 80gb drive won't be enough for our local website testing. So I mounted an XFS partition at

/vhost-drive/, and ran the transvhost.pl script as follows.

perl transvhosts.pl --dest-dir /vhost-drive/ --correct-scripts

Short version: When I run transvhost, the web vhost files are moved and the script reports success. But websites simply do not work, and spew out the following errors. (I'm sanitizing domain names with "Example.com")

my.plesk.server systemd[1]: Starting The Apache HTTP Server...
my.plesk.server httpd[8153]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 7 of /etc/httpd/conf.d/zz010_psa_httpd.conf: Could not open configuration file /etc/httpd/conf/plesk.conf.d/vhosts/example.com.conf: Permission denied
my.plesk.server systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
my.plesk.server kill[8155]: kill: cannot find process ""
my.plesk.server systemd[1]: httpd.service: control process exited, code=exited status=1
my.plesk.server systemd[1]: Failed to start The Apache HTTP Server.
my.plesk.server systemd[1]: Unit httpd.service entered failed state.
my.plesk.server systemd[1]: httpd.service failed.

Stranger still, if I re-run transvhost.pl and move files back to the standard location of /var/www/vhosts, *everything* works perfectly again.

Even verifying permissions, is there a reason Plesk vhosts shouldn't work from another volume or partition?
 
Perhaps that problem may be related to mount options which could affect some permissions, etc.
Also 'plesk repair fs' could be useful there.
 
Mount options seem identical, e.g.

/dev/mapper/centos-root / xfs defaults 0 0
/dev/mapper/centos-home /home xfs defaults 0 0
/dev/mapper/centos-swap swap swap defaults 0 0
/dev/sdb1 /vhost-drive xfs defaults 0 0

I did try `plesk repair fs` when I noticed the issue as well to no avail.
 
Back
Top