• 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

Issue Plesk Onyx 17.5.3 Upgrade Failed

KaranlikNotalar

New Pleskian
Hi,

I have a problem.

I can not upgrade.Please help.

OS: CentOS 6.9
Current version: Plesk Onyx 17.0.17 #28

İnstall Log:
(regen obsoletes cache)

===> 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: /usr/local/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'
Incorrect datetime value: '0000-00-00 00:00:00' for column 'received' at row 1

**** Product prep-install started.

===> Checking for previous installation ... found.
Create user 'psaadm' and group 'psaadm'
Checking for the group 'psaadm'...
Group 'psaadm' already exists

Checking for the user 'psaadm'...
User 'psaadm' already exists

Create group swkey-data
Checking for the group 'swkey-data'...
Group 'swkey-data' already exists

Checking for the group 'swkey-data'...
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create Mail accounts
Checking for the group 'popuser'...
Group 'popuser' already exists

Checking for the user 'popuser'...
User 'popuser' already exists

Checking for the user 'mhandlers-user'...
User 'mhandlers-user' already exists

Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done
Trying to resolve hostname 'vps242044.ovh.net' and validate its IP address... done


===> Checking for the necessary system accounts
Checking for the system groups and users necessary for admin server...
Checking for the group 'psaadm'...
Group 'psaadm' already exists

Checking for the user 'psaadm'...
User 'psaadm' already exists

Checking for the group 'psaserv'...
Group 'psaserv' already exists

Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Checking for the group 'psacln'...
Group 'psacln' already exists

Checking that /usr/local/psa/bin/chrootsh registered as login shell...
/usr/local/psa/bin/chrootsh already registered as a login shell


===> Performing safe prep-install database actions


===> Upgrading database

Trying to start service mysqld... mysqld (pid 1660) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 017000017
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.17.0.17-17.5.3.20170709-184417.dump.gz
Trying to allow INNODB engine... done
Restarting mysql Trying to restart service mysqld... mysqld (pid 1660) is running...
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
done
===> Cumulative APS controller database (apsc) upgrade has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.17.0.17-17.5.3.20170709-184425.dump.gz
===> Cumulative upgrade of APS controller database has been completed.
===> 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: [ OK ]
Starting sw_engine service... done
Starting sw_cp_server service... done
Starting mysql service... already started
Starting named service... already started
Starting mailer service... done
Starting spamfilter service... not installed
Starting drweb service... unused
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.
Bootstrapper has finished action (exec time: 70 sec.): parent_name='panel', sequence='prep', stage='execute', sequence_order='0', operation='install', exec_cmd='/usr/local/psa/bootstrapper/pp17.5.3-bootstrapper/bootstrapper.sh prep-install BASE'', m_arch='', output: Changing shell for popuser.
Shell not changed.
Changing shell for mhandlers-user.
Shell not changed.
is running
Stopping sw_engine service... done
Applying migrations from: /usr/local/psa/bootstrapper/pp17.5.3-bootstrapper/migrations/
Migration 17.5.0/2016-12-16-10-20-39_change_dns_recs_val_length.php applied

**** Product prep-install started.

===> Checking for previous installation ... found.
Create user 'psaadm' and group 'psaadm'
Checking for the group 'psaadm'...
Group 'psaadm' already exists

Checking for the user 'psaadm'...
User 'psaadm' already exists

Create group swkey-data
Checking for the group 'swkey-data'...
Group 'swkey-data' already exists

Checking for the group 'swkey-data'...
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create Mail accounts
Checking for the group 'popuser'...
Group 'popuser' already exists

Checking for the user 'popuser'...
User 'popuser' already exists

Checking for the user 'mhandlers-user'...
User 'mhandlers-user' already exists

Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done
Trying to resolve hostname 'vps242044.ovh.net' and validate its IP address... done


===> Checking for the necessary system accounts
Checking for the system groups and users necessary for admin server...
Checking for the group 'psaadm'...
Group 'psaadm' already exists

Checking for the user 'psaadm'...
User 'psaadm' already exists

Checking for the group 'psaserv'...
Group 'psaserv' already exists

Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Checking for the group 'psacln'...
Group 'psacln' already exists

Checking that /usr/local/psa/bin/chrootsh registered as login shell...
/usr/local/psa/bin/chrootsh already registered as a login shell


===> Performing safe prep-install database actions


===> Upgrading database

Trying to start service mysqld... mysqld (pid 1660) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 017000017
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.17.0.17-17.5.3.20170709-184417.dump.gz
Trying to allow INNODB engine... done
Restarting mysql Trying to restart service mysqld... mysqld (pid 1660) is running...
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
done
===> Cumulative APS controller database (apsc) upgrade has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.17.0.17-17.5.3.20170709-184425.dump.gz
===> Cumulative upgrade of APS controller database has been completed.
===> 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: [ OK ]
Starting sw_engine service... done
Starting sw_cp_server service... done
Starting mysql service... already started
Starting named service... already started
Starting mailer service... done
Starting spamfilter service... not installed
Starting drweb service... unused
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.

[2017-07-09 18:45:26.860563] Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_17_5_3', sequence='prep', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; rm -f /var/lock/parallels-panel-upgrade-failure.flag; /etc/init.d/psa restart; :'', m_arch='', output: ~empty
[2017-07-09 18:45:26.869978] Execute command /usr/local/psa/admin/bin/send-error-report install --version 17.5.3
[2017-07-09 18:45:26.909772] Error: Kurulum PREP eylemlerini gerçekleştirme sırasında bir hata oluştu (ayrıntılar günlüğüne bakın). Kurulum geri alındı.
Uyarı! Tüm paketler yüklenmedi.
Lütfen sistem hizmetlerinizin çalışıp çalışmadığını kontrol edin.
Lütfen bu sorunu çözün ve paketleri kurmayı tekrar deneyin.
Sorunu kendiniz çözemiyorsanız, destek için ürün teknik desteğiyle irtibata geçin.
 
Seems like you have either upgraded MySQL manually or modified /etc/my.cnf (or /etc/mysql/my.cnf) MySQL strict mode is enabled and prevents Plesk from upgrade. Check /etc/my.cnf (or /etc/mysql/my.cnf) file and remove the line with sql_mode parameter (or you can comment it out using ";" semicolon symbol). Don't forget to restart MySQL server. Then try to use "plesk db" command to log into MySQL console and try to run the following query:
UPDATE `APSCatalogUpdates` SET `received` = '1970-01-01 00:00:00' WHERE `received` = '0000-00-00 00:00:00';
If everything is ok, you will receive no errors and you can try to upgrade Plesk once again.
 
Seems like you have either upgraded MySQL manually or modified /etc/my.cnf (or /etc/mysql/my.cnf) MySQL strict mode is enabled and prevents Plesk from upgrade. Check /etc/my.cnf (or /etc/mysql/my.cnf) file and remove the line with sql_mode parameter (or you can comment it out using ";" semicolon symbol). Don't forget to restart MySQL server. Then try to use "plesk db" command to log into MySQL console and try to run the following query:
UPDATE `APSCatalogUpdates` SET `received` = '1970-01-01 00:00:00' WHERE `received` = '0000-00-00 00:00:00';
If everything is ok, you will receive no errors and you can try to upgrade Plesk once again.


Thank you. Disable strict mode and work.
 
Back
Top