How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.x on Linux?

Follow

Comments

241 comments

  • Avatar
    Ivan Postnikov

    Hello Kingsley Felix

    Thank you for the feedback.

    In that case, feel free to do it on your side, following steps from this article, as confirmed by other Pleskians, steps for 10.3 are identical.

    0
    Comment actions Permalink
  • Avatar
    Domenico

    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
  • Avatar
    murat (Edited )

    i have ubuntu 18.04.3, Plesk Obsidian 18.0.20 update 2 and mariadb default 10.1

    I applied this article in order.

    after;

    root@sonbahar:~# apt install mariadb-server
    ...
    Job for mariadb.service failed because the control process exited with error code.
    See "systemctl status mariadb.service" and "journalctl -xe" for details.
    invoke-rc.d: initscript mysql, action "start" failed.
    ● mariadb.service - MariaDB 10.2.29 database server
    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/mariadb.service.d
    └─migrated-from-my.cnf-settings.conf
    Active: failed (Result: exit-code) since Sat 2019-11-16 14:58:00 CET; 10ms ago
    Docs: man:mysqld(8)
    ...

    dpkg: error processing package mariadb-server (--configure):
    dependency problems - leaving unconfigured
    Processing triggers for libc-bin (2.27-3ubuntu1) ...
    No apport report written because the error message indicates its a followup error from a previous failure.
    Processing triggers for systemd (237-3ubuntu10.31) ...
    Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
    Processing triggers for ureadahead (0.100.0-21) ...
    Errors were encountered while processing:
    mariadb-server-10.2
    mariadb-server
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    root@sonbahar:~#

     

    PLEASE HELP ME.

    REGARDS

    0
    Comment actions Permalink
  • Avatar
    zainee123

    @Robert. Thanks a lot. This is really a helpful information.

    Regards

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    @Steve Yates

    I was able to check what you mentioned after upgrading to MariaDB 10.2.1. After running "yum updates" (to get to 10.2.25) the file /etc/init.d/mysql was recreated but it did not affect the service after reboot. After I rebooted, mariadb was running and mysql was not.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Necro

    It's recommended to stay with the configuration, predefined by Plesk.

    Also, here're general recommendations for securing Plesk installation: https://support.plesk.com/hc/en-us/articles/115000626925

    0
    Comment actions Permalink
  • Avatar
    Markus (Edited )

    Hi amazing Plesk support,

    in the past all upgrades were successful. This time it seems also, but in the end of installation MariaDB 10.5.5 to 10.3.24 on Ubuntu 18.04.5 and Plesk Obsidian 18.0.30 #1 I got the info that the installation failed. I went on for the last three steps by restarting and updating package version in Plesk. Then I looked in Plesk and the old version 10.3.x was shown. I performed the usual step clicking on localhost and simply clicking on OK on the next side.

    Then the new 10.5.5 version of MariaDB was shown and all websites/databases are working.

    But the fatal error already makes me unsure. Is everything okay now, or not.

    Greets and thanks for the tutorial.


    root@server:~# service mariadb start
    root@server:~# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
    Phase 1/7: Checking and upgrading mysql database
    Processing databases
    mysql
    mysql.column_stats OK
    mysql.columns_priv OK
    mysql.db OK
    mysql.event OK
    mysql.func OK
    mysql.global_priv OK
    mysql.gtid_slave_pos OK
    mysql.help_category OK
    mysql.help_keyword OK
    mysql.help_relation OK
    mysql.help_topic OK
    mysql.index_stats OK
    mysql.innodb_index_stats OK
    mysql.innodb_table_stats OK
    mysql.plugin OK
    mysql.proc OK
    mysql.procs_priv OK
    mysql.proxies_priv OK
    mysql.roles_mapping OK
    mysql.servers OK
    mysql.table_stats OK
    mysql.tables_priv OK
    mysql.time_zone OK
    mysql.time_zone_leap_second OK
    mysql.time_zone_name OK
    mysql.time_zone_transition OK
    mysql.time_zone_transition_type OK
    mysql.transaction_registry OK
    Phase 2/7: Installing used storage engines... Skipped
    Phase 3/7: Fixing views
    mysql.user
    Error : The user specified as a definer ('mariadb.sys'@'localhost') does not exist
    error : Corrupt
    Phase 4/7: Running 'mysql_fix_privilege_tables'
    ERROR 1449 (HY000) at line 7: The user specified as a definer ('mariadb.sys'@'localhost') does not exist
    ERROR 1449 (HY000) at line 16: The user specified as a definer ('mariadb.sys'@'localhost') does not exist
    ERROR 1449 (HY000) at line 59: The user specified as a definer ('mariadb.sys'@'localhost') does not exist
    ERROR 1449 (HY000) at line 68: The user specified as a definer ('mariadb.sys'@'localhost') does not exist
    ERROR 1449 (HY000) at line 86: The user specified as a definer ('mariadb.sys'@'localhost') does not exist
    FATAL ERROR: Upgrade failed
    root@server:~# service mariadb restart
    root@server:~# plesk bin service_node --update local
    The service node 'local' was successfully updated.
    root@server:~# plesk sbin packagemng -sdf
    root@server:~#

    root@server:~# aptitude upgrade
    The following packages will be upgraded:
    libmariadb3 mysql-common
    2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 153 kB of archives. After unpacking 3,072 B will be used.
    Do you want to continue? [Y/n/?] Y
    Get: 1 http://mirror.truenetwork.ru/mariadb/repo/10.5/ubuntu bionic/main amd64 libmariadb3 amd64 1:10.5.5+maria~bionic [149 kB]
    Get: 2 http://mirror.truenetwork.ru/mariadb/repo/10.5/ubuntu bionic/main ppc64el mysql-common all 1:10.5.5+maria~bionic [3,264 B]
    Fetched 153 kB in 1s (267 kB/s)
    (Reading database ... 220626 files and directories currently installed.)
    Preparing to unpack .../libmariadb3_1%3a10.5.5+maria~bionic_amd64.deb ...
    Unpacking libmariadb3:amd64 (1:10.5.5+maria~bionic) over (1:10.3.24+maria~bionic) ...
    Preparing to unpack .../mysql-common_1%3a10.5.5+maria~bionic_all.deb ...
    Unpacking mysql-common (1:10.5.5+maria~bionic) over (1:10.3.24+maria~bionic) ...
    Setting up libmariadb3:amd64 (1:10.5.5+maria~bionic) ...
    Setting up mysql-common (1:10.5.5+maria~bionic) ...
    Processing triggers for mariadb-server-10.5 (1:10.5.5+maria~bionic) ...
    Processing triggers for libc-bin (2.27-3ubuntu1.2) ...

    Current status: 0 (-2) upgradable.
    root@server:~#

    root@server:~# service mariadb status
    ● (<green) mariadb.service - MariaDB 10.5.5 database server
    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/mariadb.service.d
    └─migrated-from-my.cnf-settings.conf, override.conf
    Active: active (running) since Tue 2020-09-22 22:49:35 CEST; 50min ago
    Docs: man:mariadbd(8)
    https://mariadb.com/kb/en/library/systemd/
    Main PID: 22381 (mariadbd)
    Status: "Taking your SQL requests now..."
    Tasks: 22 (limit: 4915)
    CGroup: /system.slice/mariadb.service
    └─22381 /usr/sbin/mariadbd

    Sep 22 22:49:33 server.example.com systemd[1]: Starting MariaDB 10.5.5 database server...
    Sep 22 22:49:33 server.example.com mariadbd[22381]: 2020-09-22 22:49:33 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.5-MariaDB-1:10.5.5+maria~bion
    Sep 22 22:49:35 server.example.com systemd[1]: Started MariaDB 10.5.5 database server.
    Sep 22 22:49:35 server.example.com /etc/mysql/debian-start[22410]: Upgrading MySQL tables if necessary.
    Sep 22 22:49:35 server.example.com systemd-journald[529]: Suppressed 2385 messages from mariadb.service
    Sep 22 22:49:35 server.example.com /etc/mysql/debian-start[22415]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
    Sep 22 22:49:35 server.example.com /etc/mysql/debian-start[22415]: Looking for 'mysql' as: /usr/bin/mysql
    Sep 22 22:49:35 server.example.com /etc/mysql/debian-start[22415]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
    Sep 22 22:49:35 server.example.com /etc/mysql/debian-start[22415]: This installation of MariaDB is already upgraded to 10.5.5-MariaDB, use --f
    Sep 22 22:49:35 server.example.com /etc/mysql/debian-start[22423]: Checking for insecure root accounts.
    lines 1-23/23 (END)

    0
    Comment actions Permalink
  • Avatar
    Nerque

    I guess some of the steps are related to the change from mysql to mariadb, right?

    If we consider that we are changing from mariadb 5.5 to mariadb 10.3, in Centos 7.7, could the summary of the steps be like I show below?

    ----------------------

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

    service mariadb stop

    rpm -qa | grep mariadb

     ==> rpm -e --nodeps <other-mariadb-package>

    cp -v -a /var/lib/mysql/ /var/lib/mysql_backup

    rpm -q --whatprovides mariadb-server

    rpm -e --nodeps `rpm -q --whatprovides mariadb-server`

     

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

    [mariadb]

    name = MariaDB

    baseurl = http://yum.mariadb.org/10.3/centos7-amd64

    gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB

    gpgcheck=1

     

    yum install MariaDB-server MariaDB-client

    systemctl restart mariadb

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

    systemctl restart mariadb

    plesk sbin packagemng -sdf

    --------------------------------------

     

    My maridb related packages are:

    plesk-libmariadbclient-3.0-3.0.9-1centos.7.190417.1743.x86_64
    mariadb-libs-5.5.64-1.el7.x86_64
    sw-mariadb-client-1.0.0-centos7.17031417.x86_64
    mariadb-server-5.5.64-1.el7.x86_64
    plesk-libmariadbclient-1.0-1.0.0-1centos.7.190329.1026.x86_64
    mariadb-5.5.64-1.el7.x86_64

     

    So I guess I don't need to uninstall any of them individually, right? I guess with the command "rpm -e --nodeps `rpm -q --whatprovides mariadb-server`" they will be uninstalled

     

    If we follow all these steps, what should we do if something fails and we need to restore the previous version?

     

    0
    Comment actions Permalink
  • Avatar
    A T (Edited )

    Hello all,
    I'm sharing my upgrade path and notes (for anyone that finds it usefull),
    
upgraded CentOS 7.9.2009 x86_64 Plesk 18.0.32.2 MariaDB 5.5.68-1 to MariaDB 10.5.8-1

    As we all should research, backup backup and snap'n'backup :] and read all the comments.

    After this I made a bash script step by step mainly to avoid typos, see below and !!! use at your own rist !!!

     

    
Requirements:
    
- create the repo file for the new MariaDB version in /etc/yum.repos.d/MariaDB.repo.disabled

    Steps I executed before running the script.

    - !!! Plesk Full backup, local and off-site # !!! 

    - !!! Full (VPS) server backup !!!

    - SMTP Server (postfix), stop service
 ( in Plesk > Tools & Settings > Server Management > Services Management )
    - !!! VPS Snapshot !!!

    - Suspend sites ( in Plesk > Domains > [tag: Select ALL] > [Change Status .. Suspend]
    I tried to upgrade as recommended by Redhat 5.5 > 10.0, it failed, (the repo) could not download so I set it to 10.5 (read below)

    Post upgrade notes:
    Restart SMTP Server (postfix)
    Check # systemctl (For me wdcollect.service failed becouse database connection) manualy restared it.
    There is an error in the /var/log/message from wdcollect, think its hardcoded in the (base64-whatever encoded file)
    "PHP Warning: date(): We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/local/psa/admin/bin/modules/watchdog/wdcollect on line 194"
     

    As it seemed that the update was succesfull, database started website were running.

    A lot of other services where unable to connect in the background to the /var/lib/mysql/mysql.sock

    I've restored the connections, services are running but there are still some damaged attributes in the plesk database.

    I've removed the script for now.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Alexander! Usually, it is not required. 

    0
    Comment actions Permalink
  • Avatar
    Vitaly Zhidkov

    @Artur, in case you need some specific version of MariaDB, you can specify it in repository configuration file in baseurl. For 10.0.27 for CentOS 7 it will be http://yum.mariadb.org/10.0.27/centos7-amd64

    0
    Comment actions Permalink
  • Avatar
    Anzhelika Khapaknysh

    @murat,

    Such issues required investigation on the server.

    Please contact our Support Team for assistance.

    0
    Comment actions Permalink
  • Avatar
    Yulia Plokhotnikova

    Hi @Vinod Vyas,

    You need to find the command for a package manager that depends on your server OS. You may search in the internet for the proper command applicable for your OS as it is not managed by Plesk. For example, there are yum and rpm package managers used on Centos, CloudLinux or Red Hat OS and one of available commands would be the following:

    # rpm -qa | grep mariadb

    0
    Comment actions Permalink
  • Avatar
    Jan Bludau

    Hello @Dinara Aspembitova,

    Cool, very fast :-)

    0
    Comment actions Permalink
  • Avatar
    Vitaly Zhidkov

    @Definedhostinguk this can be only a workaround, not a fix. Check the /var/log/mysqld.log for error messages and search for articles in our Help Center

    0
    Comment actions Permalink
  • Avatar
    Markus (Edited )

    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
  • Avatar
    Jan Bludau (Edited )

    Update  Plesk Onyx 17.8.11 Update Nr. 54 to Mariadb 10.4 from 10.3

    1. rpm -q --whatprovides mysql-server
    2. If it is installed and the command above gives output, remove using the following command:

      rpm -e --nodeps `rpm -q --whatprovides mysql-server`

    3. 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:

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

      6.3. Save the changes and close the file.

     

     --> new between the next step in the guide

    # yum -y update

    # yum install MariaDB-client MariaDB-server

    if you receive a conflict with "galera-25.3.26-1" because you had installed mariadb 10.3 

    # rpm -e galera-25.3.26-1.rhel7.el7.centos.x86_64 ... 

    # yum install MariaDB-client MariaDB-server

    --> Now follow the normal guide... 

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

    ....

    # service mariadb restart

    0
    Comment actions Permalink
  • Avatar
    Anzhelika Khapaknysh (Edited )

    Hi @Hopjanj,

    Since MariaDB 10.2 default-tmp-storage-engine (in MySQL called internal_tmp_disk_storage_engine) was changed from MyISAM to InnoDB, which has certain limitations.

    In general, you may ignore the above warning.

    However, to avoid any potential issues with others (not Plesk) databases:

    1. Login server via SSH;
    2. Change  default-tmp-storage-engine back to MyISAM in [mysqld] section of /etc/my.cnf using text editor:

      grep default-tmp-storage-engine /etc/my.cnf
      default-tmp-storage-engine=MyISAM

    3. Restart MariaDB:

      service mariadb restart

     

    0
    Comment actions Permalink
  • Avatar
    Christopher-James Sheppard

    is there a possibility to roll back to the previous MariaDB version if any part of the install fails? Im on CentOS 7, MariaDB 5.5.6 and am a little hesitant to go ahead as we have 10+ Wordpress installs on the server

    0
    Comment actions Permalink
  • Avatar
    WeHoDo

    @Ivan,

     

    Thank you for your quick reply.
    I will have a look.

    0
    Comment actions Permalink
  • Avatar
    Gilberto Greppi

    HI,

    I have installed Obsidian and now some client has problem to import Database (utf8_unicode_520_ci). Your raccomended instruction ist to upgrade MariaDB.Questions:

    - can I use with Obsidian and install from Red Hat Softwer Collection the MariaDB10.3?

    - can I migrate  MariaDB 5.5.64 direct to MariaDB 10.3? On RedHat Manual they raccomand to migrate to Version 10 at first and than to 10.3    https://access.redhat.com/documentation/en-us/red_hat_software_collections/3/html/3.3_release_notes/chap-migration

    - can I use your instrution for Cento OS to migrate to MariaDB 10.3

    Thanks in advice

     

    0
    Comment actions Permalink
  • Avatar
    Rashid Qureshi

    I have followed this Article. 

    Everything went fine but the Mysql version still shows to be 5.5?

     

    What did I do wrong?

    0
    Comment actions Permalink
  • Avatar
    Miguel Ángel (Edited )

    Hi!! :)

    After upgrade mariaDB (5.5.65 >> 10.2.34) doesn't start with mysqld_safe option :(

    Any ideas?

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Artur Beqiraj

    @Vitaly Zhidkov 

    i have specific it but dont work so does not successfully complete the installation

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Louis-Philippe Frenette

    Thank you for sharing the workaround.
    It may be useful to another Pleskians.

    0
    Comment actions Permalink
  • Avatar
    Artyom Baranov

    @Peter Jablonski,

    Direct upgrade of MySQL 5.1 to MySQL 5.6/5.7 will damage tables (There is the warning message at the top of this article).

    It's strongly recommended to upgrade to MySQL 5.5 at first.

    0
    Comment actions Permalink
  • Avatar
    Thomas Friedrich

    With Ubuntu 14.04 I had to restart mysql before step 7 worked.

    0
    Comment actions Permalink
  • Avatar
    Kuzma Ivanov

    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
  • Avatar
    francesco

    What about this error? upgrading on debian 9 from mariadb 10.1 to 10.2

    Any clue how to fix it and continue upgrade?

    Removing mariadb-server-10.1 (10.1.47-0+deb9u1) ...
    (Reading database ... 97403 files and directories currently installed.)
    Preparing to unpack .../mariadb-server-10.2_10.2.36+maria~stretch_amd64.deb ...
    /var/lib/mysql: found previous version 10.1
    Unpacking mariadb-server-10.2 (10.2.36+maria~stretch) ...
    dpkg: error processing archive /var/cache/apt/archives/mariadb-server-10.2_10.2.36+maria~stretch_amd64.deb (--unpack):
    trying to overwrite '/usr/bin/mysql_install_db', which is also in package mariadb-server-core-10.1 10.1.47-0+deb9u1
    dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
    Errors were encountered while processing:
    /var/cache/apt/archives/mariadb-server-10.2_10.2.36+maria~stretch_amd64.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    0
    Comment actions Permalink
  • Avatar
    Vinod Vyas

    I am upgrading MariaDB 5.5 to v10.3

    What is the command to FIND if any additional packages like mariadb-bench are installed.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request