• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Upgrading 17.0.17 to 17.5.3 - database scheme problem

Flexy

New Pleskian
I've got problems with upgrading from 17.0.17 to 17.5.3
Maybe it's because I'm using MySQL 5.7.18?
Can anyone help me? Thx!

Code:
===> Cumulative Plesk database upgrade (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).
 Trying to set psa database version to 017005003... done
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.

===> Plesk database scheme was not upgraded completely. See installation log for details.

 * Stopping sw-cp-serverd sw-cp-server
   ...done.
Starting sw_engine service... done
Starting sw_cp_server service... done
Starting mysql service... already started
Starting named service... done
Starting mailer service... already started
Starting spamfilter service... not installed
Starting drweb service... not installed
Starting tomcat service... not installed
Starting apache service... already started
Starting xinetd service... already started
*****  problem report *****
===> Plesk database scheme was not upgraded completely. See installation log for details.

ERROR: An error occurred during performing of installation PREP actions (see log for details). Installation was rolled back.
Warning! Not all packages were installed.
Please check if your system services are operable.
Please resolve this issue and try to install the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.
exit status 1
 
Last edited:
Good evening Flexy,

What does the autoinstaller3.log shows?

One thing you can try to do is restart the server and then run the following command:

Code:
mysql_upgrade -uadmin -p`< /etc/psa/.psa.shadow `

That will attempt to upgrade the database again.

You can always run plesk repair installation to let plesk scan and repair the whole installation but without seeing the full logs it's hard to say what's the actual issue is.
 
Back
Top