• 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 Plesk 17.0 -> 17.5 upgrade fails on database prep

Joost de Bruijn

New Pleskian
I tried to upgrade my current Plesk Onyx 17.0 (running on Ubuntu 16.04.2, MySQL 5.7.17-0ubuntu0.16.04.1). installation to Plesk Onyx 17.5. However, during the preparation stage of the upgrade via the both the cli installer as the web interface, an error occured:

Code:
Installation started in background
Controleren of de onderlinge afhankelijkheid van pakketten is vastgesteld.
Bezig met installatie van pakketten
is running
Stopping sw_engine service... done
===> Cumulative APS controller database (apsc) upgrade has been started.
===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp17.5.3-bootstrapper/migrations/
Migration 17.5.0/2016-12-16-10-20-39_change_dns_recs_val_length.php applied
Migration failed: 17.5.0/2016-12-26-09-56-48_change_dates_default_value.php
Query failed: UPDATE `APSCatalogUpdates` SET `received` = '1970-01-01 00:00:00' WHERE `received` = '0000-00-00 00:00:00

However, the table is empty. How can I resolve this problem and continue the upgrade?
 
Last edited:
Do you have any related errors in mysql log?
Have you tried 'plesk repair db' before upgrade?
 
Hi,
I have the same error, how was solved?

Code:
Migration failed: 17.5.0/2016-12-26-09-56-48_change_dates_default_value.php
Query failed: UPDATE `APSCatalogUpdates` SET `received` = '1970-01-01 00:00:00' WHERE `received` = '0000-00-00 00:00:00'
Incorrect datetime value: '0000-00-00 00:00:00' for column 'received' at row 1
 
I get the same Error.

I run 'plesk repair db' several times, everything seems to be ok.

Does it have anything to do with it being MySQL 5.7?

Any help is appreciated!

Thanks in advance.

Kind regards,
Emini
 
Back
Top