• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Updating mariadb 10.3 to 10.11 on rockylinux?

charmainebell

New Pleskian
Server operating system version
Rocky Linux 8.8 (Green Obsidian)
Plesk version and microupdate number
18.0.54 Update #3
Hey all, i wish to upgrade my current mariadb version 10.3.35 to 10.11 on rocky linux 8.8. what is best possible way to do it?
 
Hi,
I'd strongly recommend performing something like this in a maintenance timeframe if the server is in a production environment.

Actions performed as root.
1. Create dump backup folder:
# mkdir /root/dbBackups
2. Dump databases, just in case(don't proceed if this action failed):
# plesk db -Ne 'show databases' | egrep -vE '(information_schema|performance_schema|mysql)' | xargs -l bash -c 'mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` $0 > /root/dbBackups/$0.sql'
3. Create /etc/yum.repos.d/mariadb.repo with the following contents:
Code:
[mariadb]
name = MariaDB
baseurl = http://mirror.mariadb.org/yum/11.3.1/rhel8-amd64/
module_hotfixes=1
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1
4. Stop mariadb server:
# systemctl stop mariadb
5. Remove it:
# rpm -e --nodeps `rpm -qf /usr/libexec/mysqld`
6. Create repository cache and install new MariaDB from it:
# yum makecache
# yum install mariadb-server
(will be prompted to hit "Y" a number of times)

7. Adjust config's bind_address value:
# sed -i 's/::ffff://' /etc/my.cnf

8. Start MariaDB 10.11:
# systemctl start mariadb

9. Upgrade tables:
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

Done.
 
Last edited:
Hello!

Thank you for the instructions, I keep running into the following errors:

Screenshot 2023-11-11 065129.png

Screenshot 2023-11-11 065216.png

Do you have any idea?

Many thanks in advance and greetings Olaf
 
Hello!

Good point... that corresponds to one of my attempts, even with lower versions I run into the same problem:

[mariadb-main]
name = MariaDB Server
baseurl = https://dlm.mariadb.com/repo/mariadb-server/10.11.5/yum/rhel/8/x86_64
gpgkey = file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
gpgcheck = 1
enabled = 1
module_hotfixes = 1

[mariadb-maxscale]
# To use the latest stable release of MaxScale, use "latest" as the version
# To use the latest beta (or stable if no current beta) release of MaxScale, use "beta" as the version
name = MariaDB MaxScale
baseurl = https://dlm.mariadb.com/repo/maxscale/latest/yum/rhel/8/x86_64
gpgkey = file:///etc/pki/rpm-gpg/MariaDB-MaxScale-GPG-KEY
gpgcheck = 1
enabled = 1

[mariadb-tools]
name = MariaDB Tools
baseurl = Tools/rhel/8/x86_64/ - MariaDB
gpgkey = file:///etc/pki/rpm-gpg/MariaDB-Enterprise-GPG-KEY
gpgcheck = 1
enabled = 1

Best regards
 
Back
Top