How to install MySQL Governor

IMPORTANT: Please make full database backup (including system tables) before you will do        upgrade of MySQL or switch to MariaDB. This action will prevent data losing in case if something goes wrong.

MySQL Governor is compatible only with MySQL 5.x, 8.0; MariaDB & Percona Server 5.6.

To install MySQL Governor on your server install governor-mysql package at first:

# yum remove db-governor db-governor-mysql  # you can ignore errors if you don’t have those packages installed
# yum install governor-mysql

Then configure MySQL Governor properly.
The installation is currently supported only on cPanel, Plesk, DirectAdmin, ISPmanager, InterWorx, as well as on servers without control panel.
If you are installing CloudLinux on a server running MySQL already, set your current MySQL version before calling installation script:

# /usr/share/lve/dbgovernor/ –mysql-version=mysqlXX
# /usr/share/lve/dbgovernor/ –install

Please make sure to specify your current MySQL version instead of XX as follows:
•55 — MySQL v5.5
•56 — MySQL v5.6
•57 — MySQL v5.7
•80 — MySQL v8.0 [requires MySQL Governor 1.2-37+;
database packages are available in Beta only, so, please use –install-beta flag instead of –install]

If you are installing CloudLinux on a server running MariaDB already, do instead:

# /usr/share/lve/dbgovernor/ –mysql-version=mariadbXX
# /usr/share/lve/dbgovernor/ –install

Please make sure to specify your current MariaDB version instead of XX as follows:
•55 — MariaDB v5.5
•100 — MariaDB v10.0
•101 — MariaDB v10.1
•102 — MariaDB v10.2
•103 — MariaDB v10.3 [requires MySQL Governor 1.2-36+; for cPanel – MySQL Governor 1.2-41+]

Installation for Percona Server 5.6 [requires MySQL Governor 1.1-22+ or 1.2-21+]:

# /usr/share/lve/dbgovernor/ –mysql-version=percona56
# /usr/share/lve/dbgovernor/ –install

Please note that MySQL/MariaDB/Percona will be updated from CloudLinux repositories.

If you are installing MySQL Governor on a server without MySQL at all, you have an opportunity to choose desired MySQL version to be installed with MySQL Governor installation script. Use –mysql-version flag before calling the installation script:

# /usr/share/lve/dbgovernor/ –mysql-version=MYSQL_VERSION
# /usr/share/lve/dbgovernor/ –install

MYSQL_VERSION could be chosen from the list of versions currently supported by MySQL Governor:
mysql51            MySQL v5.1
mysql55            MySQL v5.5
mysql56            MySQL v5.6
mysql57            MySQL v5.7
mysql80            MySQL v8.0 [requires MySQL Governor 1.2-37+; database packages are available in Beta only, so use –install-beta flag instead of –install]
mariadb55        MariaDB v5.5
mariadb100      MariaDB v10.0
mariadb101      MariaDB v10.1
mariadb102      MariaDB v 10.2
mariadb103      MariaDB v 10.3 [requires MySQL Governor 1.2-36+; for cPanel – MySQL Governor 1.2-41+]
percona56        Percona Server v 5.6

Generally, stable and beta channels contain different version of MySQL packages – beta contains newer version than stable or the same one. If you would like to install beta packages, use –install-beta flag instead of –install when calling installation script:

# /usr/share/lve/dbgovernor/ –install-beta

Starting with MySQL Governor version 1.2 when installing MySQL/MariaDB MySQL Governor asks for a confirmation of a database version to be installed. To avoid such behavior for the automatic installations, please use –yes flag.

For example:

# /usr/share/lve/dbgovernor/ –install –yes

Please note that restore of previous packages in case of failed installation would also be confirmed with –yes flag.

WARNING! Use –yes flag on your own risk, because it        confirms installation in any case – even in case if there are troubles during installation (for example, network problems causing incomplete download of packages), everything would be confirmed.

Removing MySQL Governor

To remove MySQL Governor:

# /usr/share/lve/dbgovernor/ –delete

The script will install original MySQL server, and remove MySQL Governor.

By anup

Leave a Reply

Your email address will not be published. Required fields are marked *