Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
I've seen the same issue in our logs and can confirm the same diagnosis: two files being generated by Plesk with the same configuration for the opcache.enable parameter. Although a warning, it is flooding our logs as it is logged for every invocation of PHP.
Thanks for this @tethis IT I had the same problem in AlmaLinux but in this Linux distribution I had to update the OPTIONS variable in /etc/sysconfig/named.
OPTIONS="-4 -c /etc/named.conf -u named -n 2"
I suspect it would be similar for RHEL/CentOS/Rocky Linux/etc.
Thanks, @Peter Debik - that was enough to point me in the right direction.
I figured out the table via the daily mysql dump. Then I first ran an update on the DB table to change the HTTPD_VHOSTS_D variable, followed by re-running the transvhosts.pl script ... this time there were no errors and...
@Peter Debik - here is the output of running the repair (where Plesk is set to the default vhosts directory of /var/www/vhosts) and then running the transvhosts.pl script:
# plesk repair web -y
Checking Plesk version .............................................. [OK]
Checking Apache...
Recently I am getting an error report after a Scheduled Backup runs using an S3 repository.
<?xml version="1.0"?>
<execution-result log-location="/usr/local/psa/PMM/sessions/2023-04-13-020202.335/migration.result" local-dump-created="true" export-dump-created="true"...
To recap again:
My GOAL (what I am tryng to achieve) is to move the vhosts from the default (/var/www/vhosts) to another drive (/mnt/data/vhosts).
I USED transvhosts.pl to make this move (see first comment in this thread).
The transvhosts.pl script did not change the DocumentRoot in Apache...
To recap:
I'm moving the HTTPD_VHOSTS_D from the default (/var/www/vhosts) to another drive (/mnt/data/vhosts).
I got an error with apache after running the provided transvhosts.pl script (this is the initial comment in the thread) because the DocumentRoot didn't exist.
You suggested...
Thanks, Peter. I did that and then ran the reconfigure script, but I still get errors:
# /usr/local/psa/admin/bin/httpdmng --reconfigure-all
Execution failed.
Command: httpdmng
Arguments: Array
(
[0] => --reconfigure-domains
[1] => example.com
)
Details: [2023-04-12 10:11:47.554]...
Moving vhosts to a new drive following the documentation. The result is that the Apache default DocumentRoot is not updated:
# plesk bin transvhosts.pl --dest-dir /mnt/data/vhosts/ --correct-scripts
Moving files to new directory...
Correct psa configuration file...
Correct passwd file...