Article ID: 125586, created on May 22, 2015, last review on Oct 1, 2016

  • Applies to:
  • Plesk Automation 11.5


How to upgrade MySQL database engine to version 5.5 on Linux service node?


There are two possible options:

  1. Since update 18 Plesk Automation supports new role "MySQL 5.5 database server", so you can add new service node with MySQL 5.5.
  2. It is possible to upgrade existing Database Server Service Node using the steps bellow. However it is strongly recomended to deploy new service node with MySQL 5.5 role.

2.1. Create DB backups on the management node.

2.2. Go to the service node where MySQL is planned to be upgraded and backup existing MySQL databases. It is recommended to take full server backup (or take a snapshot if a virtual environment is used).

2.3. Download and setup the repositories the packages are about to be downloaded from:

    # wget
    # wget
    # rpm -Uvh epel-release-6-8.noarch.rpm
    # rpm -Uvh remi-release-6.rpm

2.4. Install MySQL:

    # yum --enablerepo=remi update mysql-server

2.5. Make sure the versions are correct:

    # rpm -qa | grep mysql

2.6. Check the databases structure:

    # mysql_upgrade

2.7. Reread the packages installed on the service node. Go to PPA> Infrastructure> Service Nodes, select the service node where MySQL has been upgraded, then click Refresh under User-installed packages section.

2.8. As PHP version is upgraded from version 5.3 to 5.4 by dependencies, it should be updated in Customer Control Panel accordingly. Re-read PHP handlers information by using the following command on Plesk Automation Management node:

    # /usr/local/psa/bin/php_handler --reread -service-node

where `` is the communication IP address of the service node where MySQL has been upgraded.

Search Words

database version

adding new Mysql version

Upgrade MysQL

mysql 5.5

Upgrade mysql to 5.5

move mysql to 5.5

how to upgrade mysql

mysql upgrade

upgrade mysql

MySQL 5.5

Mysql 5.6.0

MySQL upgrade to 5.5

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF