• 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 Trouble upgrading Onyx 17.5.3 to 17.8.x on Centos

Paul Larson

Basic Pleskian
I've been trying to upgrade to the latest available Onyx on a CentOS machine hosted at Digital Ocean.

Centos release:
CentOS Linux release 7.5.1804

Upon upgrading, it seems to be able to complete everything except the MySQL->MariaDB.

Is MariaDB a required component to make the upgrade to 17.8?

Upon attempting the upgrade, I got this banner/warning in the Panel:

Upgrade failed. To remove this notice, remove the file /var/lock/parallels-panel-upgrade-failure.flag from the server.

When I download the log, the tail end is below.

Question: Is this normal? Do I go through the MariaDB upgrade process, and attempt the Plesk upgrade afterwards?

================================================
================================================

******************************************************************
A MySQL or MariaDB server package (MariaDB-server-10.1.30-1.el7.centos.x86_64) is installed.

Upgrading directly from MySQL 10.1 to MariaDB 10.2 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

- Ensure that you have a complete, working backup of your data and my.cnf
files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages. Usually this command will
list the packages you should remove:
rpm -qa | grep -i '^mysql-'

You may choose to use 'rpm --nodeps -ev <package-name>' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by MariaDB Foundation
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program

This is a brief description of the upgrade process. Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************
error: %pre(MariaDB-server-10.2.16-1.el7.centos.x86_64) scriptlet failed, exit status 1
Verify: 1/2: MariaDB-server.x86_64 0:10.2.16-1.el7.centos - u
Verify: 2/2: MariaDB-server.x86_64 0:10.1.30-1.el7.centos - ud
processTransaction event: 10 (Downloading Packages)
processTransaction event: 11 (unknown)
processTransaction event: 20 (Check Package Signatures)
processTransaction event: 30 (Running Test Transaction)
processTransaction event: 40 (Running Transaction)
Traceback (most recent call last):
File "/usr/local/psa/bin/yum_install", line 239, in <module>
main()
File "/usr/local/psa/bin/yum_install", line 234, in main
installer.perform(to_install, opts.remove, opts.tries)
File "/usr/local/psa/bin/yum_install", line 173, in perform
self._perform(to_install, to_remove, pt_callback)
File "/usr/local/psa/bin/yum_install", line 194, in _perform
raise Exception("Scriptlet or other non-fatal errors occurred during transaction.")
Exception: Scriptlet or other non-fatal errors occurred during transaction.
Plesk is down, performing full restart.
Starting sw_engine service... done
Starting sw_cp_server service... already started
Starting mysql service... already started
Starting named service... already started
Starting mailer service... already started
Starting spamfilter service... not installed
Starting drweb service... not installed
Starting apache service... already started
Starting xinetd service... already started
Bootstrapper has finished action (exec time: 2 sec.): parent_name='PLESK_17_8_11', sequence='pkgs', 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; touch /var/lock/parallels-panel-upgrade-failure.flag; /etc/init.d/psa restart; :'', m_arch='', output: Plesk is down, performing full restart.
Starting sw_engine service... done
Starting sw_cp_server service... already started
Starting mysql service... already started
Starting named service... already started
Starting mailer service... already started
Starting spamfilter service... not installed
Starting drweb service... not installed
Starting apache service... already started
Starting xinetd service... already started

[2018-06-27 18:18:31.946463] Error: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please contact product technical support.
 
Is my situation that unique, though?

It's merely a default 17.5.3 install (a recent one in fact), with very little efforts to customize things beyond the norm.
 
Hi Paul,

not unique, no, wouldn't think so. Just that the use of MariaDB 10.2 on a Plesk server is uncommon as it states here and here, that there may be issues.
CentOS 7 comes by default with MariaDB 5.5

Would downgrading to 10.1 be an option? Not sure about the implications though...

Cheers,
Tom
 
Thanks Tom!

Just seems odd that installing the latest Stable Centos and Plesk, at the time, has created a situation where I can't upgrade without gutting the MySQL engine. That, or I'm missing something.

Can hold off on the upgrade of course. But is the next revision of Plesk simply going to bring this MariaDB issue to the fore again?
 
MariaDB 10.1 is supported, MariaDB 10.2 basically works but is not officially supported. According to your excerpt from above, a yum installation routine tries to upgrade the database server. That upgrade is not obligatory by Plesk. Plesk 17.8 works on MariaDB 5.5 as well as on 10.1.

You can try to disable the MariaDB yum repository and upgrade Plesk without doing any database server or client updates. Afterwards you can enable the repository again. Make sure to create a full database dump before experimenting with the database.
 
Back
Top