How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.0/10.1/10.2 on Linux?

Updated March 09, 2020 05:37

Applicable to:

Plesk for Linux

This article provides instructions for upgrading MySQL 5.5 to 5.6/5.7 and MariaDB 5.5 to 10.0/10.1/10.2 on Linux.

Note: Upgrade can be performed in a command-line interface with the instructions below at your own risk. This task is supposed to be performed by a system administrator.
If you are not familiar with Linux system administering and would like our professionals to handle this task on your behalf, contact Professional Services team at https://www.plesk.com/professional-services/.

To find out your Linux distribution, run:

# plesk version | grep "OS version"

Or:

# cat /etc/*-release

Warning: MariaDB 10.3 is supported starting from Plesk Obsidian. Previous versions (Onyx and older) do not support MariaDB 10.3 and there are no plans to implement it currently.

Warning: MariaDB 10.4 is not currently supported by Plesk.

Warnings:
Direct upgrade from MySQL 5.1 to MySQL 5.6/5.7 will break tables structure. The instructions for upgrading MySQL from 5.1 to 5.5 on Linux are available here: How to upgrade MySQL from 5.1 to 5.5 on Linux

It is strongly recommended to create a server snapshot (full backup) before upgrading. Perform MySQL upgrade at your own risk.

Before starting a MySQL upgrade, stop the WatchDog service if it is used on a server. Check its status with the service watchdog status command.

Notes: MySQL will not be upgraded on CentOS/RHEL-based operating systems if it was installed from the Webtatic Yum repository:

# rpm -qa | grep -i mysql
mysql55w-server-5.5.57-1.w6.x86_64

To start an upgrade of MySQL/MariaDB, connect to a server via SSH as root/superuser and follow the instructions for your operating system:

Plesk on CentOS 7 / RHEL 7

By default, CentOS 7 is shipped with MariaDB 5.5. MariaDB 10.x version is a drop-in replacement for MySQL 5.5-5.7.

For security reasons, create a database dump of all databases with the following command:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysqldump -u admin --all-databases --routines --triggers > /tmp/all-databases.sql
Stop MariaDB:

# service mariadb stop
Remove additional packages like mariadb-bench:

# rpm -e --nodeps mariadb-bench
For security reasons, copy the database directory in a separate folder:

# cp -v -a /var/lib/mysql/ /var/lib/mysql_backup
Check if the mysql-server package is already installed:

# rpm -q --whatprovides mysql-server

If it is installed and the command above gives output, remove using the following command:

# rpm -e --nodeps `rpm -q --whatprovides mysql-server`
Configure MariaDB repository: open the Setting MariaDB repositories page, select your OS distro, release and a desired MariaDB version. Once done, the configuration that should be added to the /etc/yum.repos.d/MariaDB.repo file will appear.

Here is an example for MariaDB 10.2:

6.1. Open/create the MariaDB.repo file in any text editor. In this example, we are using the vi editor:

# vi /etc/yum.repos.d/MariaDB.repo

6.2. Add the content below to the file:

CONFIG_TEXT: [mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.2/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

6.3. Save the changes and close the file.
Start an upgrade of MariaDB:

# yum install MariaDB-client MariaDB-server
Once the upgrade is finished, start MariaDB:

# systemctl restart mariadb

OR

# systemctl restart mysql
Upgrade MySQL databases:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
Restart mysql service:

# systemctl restart mariadb

OR

# systemctl restart mysql
Execute this command to update the package version inside Plesk:

# plesk sbin packagemng -sdf

Note: After an upgrade, there may appear 'mysql' init script. It should be removed to avoid conflicts with MariaDB service. The same commands can be used to fix already existing conflict:

# systemctl stop mysql; killall mysqld # to stop the incorrect service if it is started
# rm /etc/init.d/mysql && systemctl daemon-reload # to remove the incorrect service script and reload systemctl configuration
# systemctl start mariadb # to start MariaDB if not started
# systemctl enable mariadb # to make sure that MariaDB will start after the server reboot automatically

Plesk on CentOS 6 / RHEL 6

For security reasons, create a database dump of all databases with the following command:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysqldump -u admin --all-databases --routines --triggers > /tmp/all-databases.sql

If the command fails with "Cannot load from mysql.proc. The table is probably corrupted", apply the solution from this KB article.
Stop MySQL server:

# service mysqld stop
For security reasons, create a backup of all existing databases:

# cp -a /var/lib/mysql /var/lib/mysql_backup
Disable Atomic repository, if it is enabled:

# vi /etc/yum.repos.d/atomic.repo
enabled = 0
Check for MySQL repo files left from previous installation.

# ls -l /etc/yum.repos.d/mysql*

If any found, remove them:

# rm -rf /etc/yum.repos.d/mysql-community-source.repo
Install the MySQL-community repository:

# yum install https://dev.mysql.com/get/mysql80-community-release-el6-1.noarch.rpm
Configure MySQL repository:

7.1. Open the mysql-community.repo file in a text editor. In this example, we are using the vi editor:

# vi /etc/yum.repos.d/mysql-community.repo

7.2. Select a MySQL version. In this example, we are upgrading MySQL to 5.7:

Warning: Disable MySQL 8.0 repository and exclude mysql-connector-odbc-8 version, as these releases are not supported by Plesk yet. If it is not disabled, yum will install the latest version which will cause major issues.

CONFIG_TEXT: [mysql56-community]
enabled=0
...
[mysql57-community]
enabled=1
...
[mysql80-community]
enabled=0
...
[mysql-connectors-community]
exclude=mysql-connector-odbc-8*
...

7.3. Save the changes and close the file.
Install MySQL packages:

# yum update mysql

If update of mysql package ends with Nothing to do message, make sure that mysql* packages are not added to excludes in yum.conf file and remove it if it is in the list:

# cat /etc/yum.conf | grep exclude
exclude=php-common php-cli php mysql* httpd* mod_ssl*
Type y if this message appears:

CONFIG_TEXT: warning: rpmts_HdrFromFdno: Header V3 DSA/SHA1 Signature, key ID 5072e1f5: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
Importing GPG key 0x5072E1F5:
Userid : MySQL Release Engineering <mysql-build@oss.oracle.com>
Package: mysql57-community-release-el6-7.noarch (@/mysql57-community-release-el6-7.noarch)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
Is this ok [y/N]:
Start MySQL server:

# service mysqld start

If the service does not start, check the following article: MySQL fails to start: mysql.user table is damaged.
Upgrade MySQL databases:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
Restart mysql service:

# service mysqld restart
Execute the following commands to update package version inside Plesk:

# plesk bin service_node --update local
# plesk sbin packagemng -sdf

Plesk on CloudLinux

Create a backup of all databases with the following command:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysqldump -u admin --all-databases --routines --triggers > /tmp/all-databases.sql
Stop the MySQL service:

# service mysqld stop
Copy a databases directory in a separate folder like this (for backup purposes also):

# cp -v -a /var/lib/mysql/ /var/lib/mysql_backup
Start the MySQL service:

# service mysqld start
Ensure that [mysqlclient] repository is enabled in
/etc/yum.repos.d/cl-mysql.repo and the below command displays similar output:

# yum repolist enabled | grep mysqlclient
Repository extras is listed more than once in the configuration
mysqclient/7/x86_64 mysqlclient 7
Select MySQL/MariaDB version to install:

Note: The following command does not work if governor-mysql package is not installed. In such case, install it:
# yum install governor-mysql

# /usr/share/lve/dbgovernor/mysqlgovernor.py --mysql-version=XXXXX

Note: Where 'XXXXX' has to be substituted with one of the following:
mariadb100 for MariaDB v10.0
mariadb101 for MariaDB v10.1
mariadb102 for MariaDB v10.2
mysql55 for MySQL v5.5
mysql56 for MySQL v5.6
mysql57 for MySQL v5.7
Install selected previously MariaDB engine:

# /usr/share/lve/dbgovernor/mysqlgovernor.py --install

Warning: CloudLinux does not recommend to downgrade from MySQL v5.6, MariaDB 10.x
Restart MySQL:

# service mysql restart
Upgrade MySQL databases:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
Restart MySQL:

# service mysql restart
Execute the following commands to update package version inside Plesk:

# plesk bin service_node --update local
# plesk sbin packagemng -sdf

Plesk on Debian 8 & 9

Debian 8 & 9 are basically shipped with MariaDB. MariaDB 10.x version is a drop-in replacement for MySQL 5.5/5.6/5.7

Backup all existing databases using the KB article How to backup/restore a Plesk database dump and follow instructions on MariaDB site to update it:

https://mariadb.com/kb/en/mariadb/installing-mariadb-deb-files/

Example for MariaDB 10.2

Install MariaDB:

Stop the MariaDB service:

# service mariadb stop

# curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=mariadb-10.2

# apt install mariadb-server-10.2

If the installation fails with unmet dependencies:

CONFIG_TEXT: dpkg: mariadb-server-10.1: dependency problems, but removing anyway as you requested:
plesk-mysql-server depends on virtual-mysql-server | mysql-server; however:
Package virtual-mysql-server is not installed.
Package mariadb-server-10.1 which provides virtual-mysql-server is to be removed.
Package mariadb-server-10.2 which provides virtual-mysql-server is not installed.
Package mysql-server is not installed.
<...>
The following packages have unmet dependencies:
mariadb-server-10.2 : Depends: mariadb-client-10.2 (>= 10.2.19+maria~stretch) but it is not going to be installed
Depends: mariadb-server-core-10.2 (>= 10.2.19+maria~stretch) but it is not going to be installed

Run the command below to correct them:

# apt --fix-broken install

If the command above fails with the following error:

CONFIG_TEXT: [...]
Preparing to unpack .../mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb ...
47146
There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
47146
There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!
dpkg: error processing archive /var/cache/apt/archives/mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
insserv: warning: script 'apf' missing LSB tags and overrides
Errors were encountered while processing:
/var/cache/apt/archives/mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
[...]

Check this article: Plesk Update failed: There is a MySQL server running, but we failed in our attempts to stop it.

Check MySQL version:

# mysql -V
mysql Ver 15.1 Distrib 10.2.19-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

Start the MariaDB service:

# service mariadb start

Note: It may be already started

Upgrade MySQL databases:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

Restart mysql service:

# service mariadb restart

Execute the following commands to update package version inside Plesk:

# plesk bin service_node --update local
# plesk sbin packagemng -sdf

Plesk on Ubuntu 18.04

Ubuntu 18.04 is shipped with MariaDB 10.1. MariaDB 10.x version is a drop-in replacement for MySQL 5.5-5.7. In order to upgrade MariaDB 10.1 to MariaDB 10.2, follow this steps:

Create a backup of all databases with the following command:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysqldump -u admin --all-databases --routines --triggers > /tmp/all-databases.sql
Stop the MariaDB service:

# service mariadb stop
Install repositories from downloads.mariadb.org, for example qq:

Warning: Check the file "/etc/apt/sources.list" and the files inside directory "/etc/apt/sources.list.d/" and disable (comment with # at the beginning of the line) all MySQL repositories (e.g. MySQL 8 repository) to avoid installation of wrong MySQL versions by mistake.

# apt-get install software-properties-common
# apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8
# add-apt-repository 'deb [arch=amd64,arm64,ppc64el] http://mirror.truenetwork.ru/mariadb/repo/10.2/ubuntu bionic main'
Create a backup of all MySQL data:

# cp -v -a /var/lib/mysql/ /var/lib/mysql_backup
Start an upgrade with the following command. Leave all fields empty when asked for a root user password:

# apt-get install mariadb-server
Start the MariaDB service:

# service mariadb start
Upgrade MySQL databases:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
Restart mysql service:

# service mariadb restart
Execute the following commands to update package version inside Plesk:

# plesk bin service_node --update local
# plesk sbin packagemng -sdf

More information available in MySQL documentation at http://dev.mysql.com/.

Comments

140 comments

Aptum Frontline June 21, 2018 21:17

Can you please make sure that the step "mysql_upgrade" is added after upgrading / starting MySQL on the CentOS 7 instructions?

This checks and fixes any system tables

Thank You

1

Comment actions Permalink
Ivan Postnikov June 25, 2018 11:54

Hello @Cogeco Peer 1 Frontline,

I have reviewed the article, "mysql_upgrade" is already added to be executed after upgrading Database server and starting it.

0

Comment actions Permalink
Signor Rossi July 06, 2018 03:38

Upgraded to MariaDB 10.3 on Plesk 17.8.11 on CentOS 7.5 successfully.

1

Comment actions Permalink
Ivan Postnikov July 06, 2018 21:12

Hello @Ivan, glad to hear that the instruction has helped. However, MariaDB 10.2 and 10.3 are not yet officially supported by Plesk.

0

Comment actions Permalink
Learning Curve September 05, 2018 03:04

We followed the instructions provided on here and upgraded MariaDB 10.1 to MariaDB 10.2 on Ubuntu 18.04.1 running Plesk 17.8.11 #19 where MariaDB 10.2 is now officially supported. It worked first time, perfectly, with no issues.

1

Comment actions Permalink
Alexandr Tumanov September 05, 2018 09:43

@Learning Curve, great!

0

Comment actions Permalink
Bruno Schrotter September 13, 2018 18:17 (Edited September 13, 2018 18:24)

Hello Ivan!

I have Plesk Onyx Version 17.8.11 Update #19 on a CentOS Linux 7.5.1804 (Core) with a MySQL (Maria DB I belief) ver.5.5.60. on a dedicated server.

I have a script that requires MySQL ver. 5.6, and error flags with [No MySQL available] when I tried to install it just to see.

The script developer tells me to move to a server with Cpanel, and that is out of the question, as I have used Plesk since version 7 or 8 I believe. I cannot get a refund either, as this is not a script failure, and I'm not going to write off $800 either, and there's no other script with what I need anyway.

I have currently 2 servers with Plesk licenses, and I can experiment with one not so important.
However, my time is on a tremendous squeeze, so I would like to start out with something that works without trying to experiment with version after version.

Should I try to install the latest MariaDB 10.3, or is it possible to install a MySQL 5.6 as required, and a better option. I would appreciate your opinion. Thank you kindly!

0

Comment actions Permalink
Kevin Hudson September 28, 2018 01:14

I am running the latest version of Plesk Onyx for Linux 17.8.11 with CentOS 7.5.1804 and I want to Upgrade the MySQL Server from 5.5 to 5.7.

For software specific reasons, I do not want to Upgrade to MariaDB 10.X. Does anyone know if the instructions above for CentOS 6 will work for CentOS 7.5?

0

Comment actions Permalink
Alexandr Redikultsev October 03, 2018 12:18

Hi @Bruno Schrotter!

As MariaDB is a replacement for MySQL, upgrade it to MariaDB 10.1 (that is equal to MySQL 5.6). Just follow the instructions for CentOS 7, it should work as expected.

1

Comment actions Permalink
Alexandr Redikultsev October 03, 2018 12:50 (Edited October 03, 2018 12:50)

Hi @Kevin Hudson!

Instructions for CentOS 6 will not work as CentOS 6 has MySQL by default.

What you need to do in order to achieve your goal is to replace MariaDB with MySQL 5.5 and then upgrade MySQL 5.5 to MySQL 5.7. Replacement might have some issues with compatibility.

I was not able to find the repo for MySQL 5.5 for CentOS 7, however if you find one, something like this should do the trick for you:

1. Stop MariaDB:

# service mariadb stop

2. Remove it:

# rpm -e --nodeps mariadb-server

3. Add your custom repo with mysql 5.5.

4. Install packages from this repo:

# yum install mysql-server mysql-community-server

5. Then, start the service, run mysql_upgrade:

# service mysqld start
# mysql_upgrade -uadmin -p`cat /etc/psa/.psa.shadow`

6. Refresh server components:

# plesk sbin packagemng -sdf

Note that you might want to install packages manually on step 4 in case you will not be able to find the repo on step 3.

Please, keep in mind that this instructions were not tested and I suggest to create a snapshot of the server as well as the backup of MySQL databases before doing so.

1

Comment actions Permalink
Bruno Schrotter October 03, 2018 16:29

Thanks @Alexandr Redikultsev!
I very much appreciate your kind response and suggestion.

0

Comment actions Permalink
Alexandr Redikultsev October 04, 2018 09:10

You are welcome, @Bruno Schrotter!

0

Comment actions Permalink
Markus October 04, 2018 21:55

Thank You very much Plesk Support Team ! ! ! It worked easy and successful like in the tutorial. Three days ago I reinitialized my 1und1 dedicated server with new Ubuntu 18.04.1 with Plesk 17.8.11 and MariaDB 10.1.36.

NOW MariaDB 10.2.18 - PLESK is awesome 'n' great - Greets

1

Comment actions Permalink
Alisa Kasyanova October 05, 2018 06:27

@Markus Wernecke

Good to know that the article helped! Enjoy your Plesk :)

1

Comment actions Permalink
Patrick Meppe January 02, 2019 16:37
Hello there.

Nice article, I upgraded my MySQL server from 5.5 to 5.7 on Ubuntu 14.04 successfully.

When restarting my server I ran through the following warning: MySQL 5.7 No directory, logging in with HOME=/

My solution (for the time being) is/was to change home directory of mysql
```
# service mysql stop
# usermod -d /var/lib/mysql/ mysql
# service mysql start
```
0

Comment actions Permalink
Jeremy A Gruver January 09, 2019 07:03

This fixed my issues on the latest Plesk 17.8 --- was migrating from Ubuntu 18. Used CloudLinux, it caused a lot of issues. So don't do CloudLinux first -- YOU WILL run into issues... MIGRATE YOUR ACCOUNTS FIRST, then add your extensions like CloudLinux and Litespeed.

0

Comment actions Permalink
Ivan Postnikov January 09, 2019 09:09

Hello @Jeremy,

Thank you for sharing your user experience.

For further issues feel free to contact Plesk Technical Support.

0

Comment actions Permalink
Domenico January 18, 2019 13:49 (Edited January 18, 2019 17:06)

hi, I tried to update the MySQL version by following the guide but the operation stopped at point 8.

MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

and I receive the error:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)
FATAL ERROR: Upgrade failed

thanks

0

Comment actions Permalink
Alexandr Redikultsev January 20, 2019 12:59

Hi @Domenico,

The command should be working well in case there is no other issue involved here. Try checking this in the following manner:

1. Check whether or not you can access MySQL with any of the following commands:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin psa

OR

# plesk db

OR

# mysql psa -uadmin -p`cat /etc/psa/.psa.shadow`

2. I also would recommend checking whether or not you have /root/.my.cnf file and removing it if any.

0

Comment actions Permalink
Domenico January 20, 2019 17:17

thanks for the reply
now I'm stuck at point 10,

if I ask the status of the mariadb comes out like this:

# systemctl status mariadb
? mariadb.service - MariaDB 10.1.37 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
+-migrated-from-my.cnf-settings.conf
Active: active (running) since Sun 2019-01-20 18:12:20 CET; 42s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 14024 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 13985 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 13982 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 13997 (mysqld)
Status: "Taking your SQL requests now..."
Tasks: 26
Memory: 128.3M
CGroup: /system.slice/mariadb.service
+-13997 /usr/sbin/mysqld

Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] InnoDB: Highest supported file format is Barracuda.
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] InnoDB: 128 rollback segment(s) are active.
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] InnoDB: Waiting for purge to start
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] InnoDB: Percona XtraDB (http://www.percona.com) ... 1616887
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] Plugin 'FEEDBACK' is disabled.
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140303289808640 [Note] InnoDB: Dumping buffer pool(s) not yet started
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] Server socket created on IP: '::'.
Jan 20 18:12:20 server88 mysqld[13997]: 2019-01-20 18:12:20 140304080845056 [Note] /usr/sbin/mysqld: ready for connections.
Jan 20 18:12:20 server88 mysqld[13997]: Version: '10.1.37-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
Jan 20 18:12:20 server88 systemd[1]: Started MariaDB 10.1.37 database server.
Hint: Some lines were ellipsized, use -l to show in full.

but when I launch point 10 it comes out like this:

# plesk sbin packagemng -sdf
-bash: plesk: command not found

Naturally I can not access plesk

in /root/.my.cnf I do not have this file

0

Comment actions Permalink
Alisa Kasyanova January 22, 2019 07:49

@Domenico

Check if any Plesk-related packages were removed during the upgrade of MariaDB (in /var/log/yum.log they should be marked as "erased").
If there were, run the autoinstaller and reinstall them:

# wget https://autoinstall.plesk.com/plesk-installer
# chmod +x plesk-installer
# ./plesk-installer

1

Comment actions Permalink
Domenico January 22, 2019 08:23

@Alisa,

thanks for your kind reply, I tried several times to reinstall plesk, in yum.log I see different Erased: plesk ... I made the commands you indicated, part of the installation but crashes with this error:

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

Trying to start service mysql... active
done
Trying to establish test connection... ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)

failed

ERROR while trying to establish test connection
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log), fix and try again

***** problem report *****
ERROR while trying to establish test connection
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log), fix and try again
sh: /etc/init.d/psa: No such file or directory

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.

0

Comment actions Permalink
Ivan Postnikov January 23, 2019 16:34

Hello @Domenico,

From the provided logs I see that Plesk is not able to establish a connection with MariaDB.

Initial troubleshooting steps are the same as provided by @Alexander:

1. Check whether or not you can access MySQL with any of the following commands:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin psa

OR

# plesk db

OR

# mysql psa -uadmin -p`cat /etc/psa/.psa.shadow`

2. I also would recommend checking whether or not you have /root/.my.cnf file and removing it if any.

As the issue is rather complicated and there is Plesk downtime, I would suggest submitting a request for Plesk Support.

1

Comment actions Permalink
Domenico January 23, 2019 17:02

hello Ivan, thanks for the reply

if you activate the commands indicated by you, this happens:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin psa
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)
# plesk db
-bash: plesk: command not found
# mysql psa -uadmin -p`cat /etc/psa/.psa.shadow`
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)

in root/ I do not have the file /.my.cnf
I see a file named .mysql_history

I tried to make a request to the support, but it tells me that my license was sold by a retailer and I can not go on, my dealer does not help me because I did not buy this

0

Comment actions Permalink
Domenico January 23, 2019 17:04

now the server is compromised and I'm giving up, in 10 days my subscription expires and I will let him die

0

Comment actions Permalink
Artyom Baranov January 24, 2019 06:24

@Domenico,

Hello,

In such case, it is still possible to get support from Plesk directly. Please check the article How to get support directly from Plesk?

Plesk support subscription will allow you to submit a request if you decide to continue with MySQL upgrade.

0

Comment actions Permalink
Markus February 04, 2019 23:12 (Edited February 05, 2019 01:40)

Hi,

two little things. First, the repo/mirror "mirror.host.ag" in capital city of Bulgaria, Sofia, provided in the tutorial is not accessable since last week. I had to choose another one, because I got the following error [HUB] Plesk Update Manager (PUM) fails: pum is called with arguments.

Second is a question. Is it possible to upgrade from 10.2 to 10.3 or do you recommend to wait a while? Because on the mirrors site shows MariaDB 10.3 release for Ubuntu 18.04 LTS as "stable".

Lots of greets

0

Comment actions Permalink
Kuzma Ivanov February 06, 2019 10:17

Hey there Markus,

1. Looks like not only in Bulgaria the repo http://mirror.host.ag/ is unavailable. We've already replaced it with a different one - http://mirror.truenetwork.ru.
Thanks for bringing this to our attention.

2. MariaDB 10.3 is not yet supported by Plesk. Support for this version will be added in the upcoming major release. It is now reflected in the article as well.

0

Comment actions Permalink
Alejandro Stendelis March 22, 2019 02:43

Hi I get this error, how I can fix it??

CentOS 6.8

mysql Ver 14.14 Distrib 5.5.30, for Linux (x86_64) using readline 5.1

[root@casadimaco ~]# yum update mysql
Loaded plugins: fastestmirror
Setting up Update Process
Loading mirror speeds from cached hostfile
* base: mirror.fileplanet.com
* extras: mirrors.oit.uci.edu
* updates: mirrors.usc.edu
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.5.30-1.el6.remi will be obsoleted
--> Processing Dependency: mysql(x86-64) = 5.5.30-1.el6.remi for package: mysql-bench-5.5.30-1.el6.r emi.x86_64
--> Processing Dependency: mysql(x86-64) = 5.5.30-1.el6.remi for package: mysql-server-5.5.30-1.el6. remi.x86_64
--> Processing Dependency: mysql(x86-64) = 5.5.30-1.el6.remi for package: mysql-devel-5.5.30-1.el6.r emi.x86_64
---> Package mysql-community-client.x86_64 0:5.7.25-1.el6 will be obsoleting
--> Processing Dependency: mysql-community-libs(x86-64) >= 5.7.9 for package: mysql-community-client -5.7.25-1.el6.x86_64
--> Running transaction check
---> Package mysql-bench.x86_64 0:5.5.30-1.el6.remi will be obsoleted
---> Package mysql-community-devel.x86_64 0:5.7.25-1.el6 will be obsoleting
---> Package mysql-community-libs.x86_64 0:5.7.25-1.el6 will be obsoleting
--> Processing Dependency: mysql-community-common(x86-64) >= 5.7.9 for package: mysql-community-libs -5.7.25-1.el6.x86_64
---> Package mysql-community-server.x86_64 0:5.7.25-1.el6 will be obsoleting
--> Processing Dependency: libnuma.so.1(libnuma_1.2)(64bit) for package: mysql-community-server-5.7. 25-1.el6.x86_64
--> Processing Dependency: libnuma.so.1(libnuma_1.1)(64bit) for package: mysql-community-server-5.7. 25-1.el6.x86_64
--> Processing Dependency: libnuma.so.1()(64bit) for package: mysql-community-server-5.7.25-1.el6.x8 6_64
---> Package mysql-devel.x86_64 0:5.5.30-1.el6.remi will be obsoleted
---> Package mysql-libs.x86_64 0:5.5.30-1.el6.remi will be obsoleted
--> Processing Dependency: libmysqlclient.so.18()(64bit) for package: php-mysql-5.4.13-1.el6.remi.x8 6_64
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4 .13-1.el6.remi.x86_64
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: php-mysql-5.4 .13-1.el6.remi.x86_64
---> Package mysql-server.x86_64 0:5.5.30-1.el6.remi will be obsoleted
--> Running transaction check
---> Package mysql-community-common.x86_64 0:5.7.25-1.el6 will be installed
---> Package mysql-libs.x86_64 0:5.5.30-1.el6.remi will be obsoleted
--> Processing Dependency: libmysqlclient.so.18()(64bit) for package: php-mysql-5.4.13-1.el6.remi.x8 6_64
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4 .13-1.el6.remi.x86_64
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: php-mysql-5.4 .13-1.el6.remi.x86_64
---> Package numactl.x86_64 0:2.0.9-2.el6 will be installed
--> Finished Dependency Resolution
Error: Package: php-mysql-5.4.13-1.el6.remi.x86_64 (installed)
Requires: libmysqlclient.so.18()(64bit)
Removing: mysql-libs-5.5.30-1.el6.remi.x86_64 (installed)
libmysqlclient.so.18()(64bit)
Obsoleted By: mysql-community-libs-5.7.25-1.el6.x86_64 (mysql57-community)
Not found
Available: mysql-libs-5.5.28-3.el6.remi.x86_64 (mt_dv_extras)
libmysqlclient.so.18()(64bit)
Available: mysql-libs-5.5.29-1.el6.remi.x86_64 (mt_dv_extras)
libmysqlclient.so.18()(64bit)
Available: mysql-libs-5.1.73-8.el6_8.i686 (base)
Not found
Error: Package: php-mysql-5.4.13-1.el6.remi.x86_64 (installed)
Requires: libmysqlclient.so.18(libmysqlclient_18)(64bit)
Removing: mysql-libs-5.5.30-1.el6.remi.x86_64 (installed)
libmysqlclient.so.18(libmysqlclient_18)(64bit)
Obsoleted By: mysql-community-libs-5.7.25-1.el6.x86_64 (mysql57-community)
Not found
Available: mysql-libs-5.5.28-3.el6.remi.x86_64 (mt_dv_extras)
libmysqlclient.so.18(libmysqlclient_18)(64bit)
Available: mysql-libs-5.5.29-1.el6.remi.x86_64 (mt_dv_extras)
libmysqlclient.so.18(libmysqlclient_18)(64bit)
Available: mysql-libs-5.1.73-8.el6_8.i686 (base)
Not found
Error: Package: php-mysql-5.4.13-1.el6.remi.x86_64 (installed)
Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Removing: mysql-libs-5.5.30-1.el6.remi.x86_64 (installed)
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Obsoleted By: mysql-community-libs-5.7.25-1.el6.x86_64 (mysql57-community)
Not found
Available: mysql-libs-5.5.28-3.el6.remi.x86_64 (mt_dv_extras)
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Available: mysql-libs-5.5.29-1.el6.remi.x86_64 (mt_dv_extras)
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Available: mysql-libs-5.1.73-8.el6_8.i686 (base)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

0

Comment actions Permalink
Vladimir Chernikov March 27, 2019 16:25

Hello @Alejandro Stendelis,

Try to clean up the list of the mirrors.

1. Install yum utils:
# yum install yum-utils

2. Run the following command:
# yum clean all

If the issue still persists, please submit the ticket and we investigate the issue:
How to submit a request to Plesk support?

0

Comment actions Permalink