What is the output of the command:
# ls -la /var/log/plesk/install/plesk_18.0.27_repair*
?
Below is the output:
plesk repair installation
Reconfiguring the Plesk installation
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.
Finishing up upgrade procedures and rerunning previously failed upgrade actions ...
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp18.0.27-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
IP addresses were reread from the system. Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...
Fixing permissions on Panel packages files
error: rpmdbNextIterator: skipping h# 1472 region trailer: BAD, tag 1560948000 type 1533440861 offset -543323250 count 1718827552
ERROR:Expected and actual types of file '/usr/local/psa/admin/htdocs/domains/databases/phpMyAdmin/libraries/classes/Controllers/Setup/ServersController.php' do not match: file != directory .
Changing permissions on /var/run/dovecot/login to 0755
Bootstrapper repair finished.
Errors occurred while performing the following actions: fix Plesk packages permissions.
Check '/var/log/plesk/install/plesk_18.0.27_repair.log' and '/var/log/plesk/install/plesk_18.0.27_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.