# Upgrade MariaDB to 10.11

**URL:** <https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [November 1, 2025, 6:53pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824 "2025-11-01T18:53:08Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![chupi](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@chupi](https://forums.rockylinux.org/u/chupi)\
**Post date:** [November 1, 2025, 6:53pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/1 "2025-11-01T18:53:08Z")

</div>

Hello everyone,

I’m using Rocky Linux 9.6 and I need to update MariaDB to version 10.11, which is necessary for Joomla 6, the latest release of this CMS I use.

Rocky uses MariaDB 10.5 by default, but it has a module for version 10.11. When I enable this module:

$ dnf module enable mariadb:10.11

Webmin now indicates that I can update:

An update to mariadb from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available

My question is whether I can update from Webmin without any problems while keeping the current databases as they are, since I’ve read some tutorials that say several additional steps are required.

Thanks,

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 1, 2025, 7:02pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/2 "2025-11-01T19:02:18Z")

</div>

So if you did:

```auto
dnf module enable mariadb:10.11

```

then your second command should have been:

```auto
dnf update

```

or if mariadb is not already installed:

```auto
dnf install mariadb-server

```

Personally I don’t use Webmin, I’ve been bitted before because if it’s peculiarities and it breaking things. That is why Rocky comes with cockpit. Also it’s better to learn to do things properly than rely on tools that try to be clever like webmin.

---

<div class="post-metadata">

**Author:** ![chupi](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@chupi](https://forums.rockylinux.org/u/chupi)\
**Post date:** [November 1, 2025, 7:26pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/3 "2025-11-01T19:26:08Z")

</div>

Thanks iwalker,

I have MariaDB version 10.5 installed and several production domains, hence my question: would updating to version 10.11 affect the databases?

If I run the update from Webmin, these are the packages that would be updated:

An update to mariadb from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available.

An update to mariadb-backup from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available.

An update to mariadb-common from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available.

An update to mariadb-errmsg from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available.

An update to mariadb-server from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available.

An update to mariadb-server-utils from 10.5.27-1.el9\_5.0.2 to 10.11.10-1.module+el9.6.0+31841+9417776a is available.

However, some say that you first need to remove the previous version of MariaDB and then run, for example, $ mysql\_upgrade --force.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 1, 2025, 7:57pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/4 "2025-11-01T19:57:48Z")

</div>

A quick test:

```auto
root@rocky9:~# rpm -qa | grep -i mariadb-server
mariadb-server-utils-10.5.27-1.el9_5.0.2.x86_64
mariadb-server-10.5.27-1.el9_5.0.2.x86_64

root@rocky9:~# dnf module enable mariadb:10.11
Last metadata expiration check: 0:01:58 ago on Sat 01 Nov 2025 08:52:37 PM CET.
Dependencies resolved.
========================================================================================================================
 Package Architecture Version Repository Size
========================================================================================================================
Enabling module streams:
 mariadb 10.11                                                          

Transaction Summary
========================================================================================================================

Is this ok [y/N]: y
Complete!

root@rocky9:~# dnf update -y
Last metadata expiration check: 0:02:17 ago on Sat 01 Nov 2025 08:52:37 PM CET.
Dependencies resolved.
========================================================================================================================
 Package Architecture Version Repository Size
========================================================================================================================
Upgrading:
 mariadb x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 1.7 M
 mariadb-backup x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 6.8 M
 mariadb-common x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 27 k
 mariadb-errmsg x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 254 k
 mariadb-gssapi-server x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 15 k
 mariadb-server x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 10 M
 mariadb-server-utils x86_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream 261 k

Transaction Summary
========================================================================================================================
Upgrade 7 Packages

Total download size: 19 M
Downloading Packages:
(1/7): mariadb-common-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 141 kB/s | 27 kB 00:00    
(2/7): mariadb-gssapi-server-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 73 kB/s | 15 kB 00:00    
(3/7): mariadb-server-utils-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 2.4 MB/s | 261 kB 00:00    
(4/7): mariadb-errmsg-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 4.5 MB/s | 254 kB 00:00    
(5/7): mariadb-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 5.8 MB/s | 1.7 MB 00:00    
(6/7): mariadb-backup-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 7.0 MB/s | 6.8 MB 00:00    
(7/7): mariadb-server-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64.rpm 7.8 MB/s | 10 MB 00:01    
------------------------------------------------------------------------------------------------------------------------
Total 12 MB/s | 19 MB 00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing : 1/1 
  Upgrading : mariadb-common-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 1/14 
  Upgrading : mariadb-errmsg-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 2/14 
  Upgrading : mariadb-gssapi-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 3/14 
  Upgrading : mariadb-backup-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 4/14 
  Upgrading : mariadb-server-utils-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 5/14 
  Upgrading : mariadb-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 6/14 
  Running scriptlet: mariadb-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 7/14 
  Upgrading : mariadb-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 7/14 
  Running scriptlet: mariadb-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 7/14 
  Running scriptlet: mariadb-server-3:10.5.27-1.el9_5.0.2.x86_64 8/14 
  Cleanup : mariadb-server-3:10.5.27-1.el9_5.0.2.x86_64 8/14 
  Running scriptlet: mariadb-server-3:10.5.27-1.el9_5.0.2.x86_64 8/14 
  Cleanup : mariadb-errmsg-3:10.5.27-1.el9_5.0.2.x86_64 9/14 
  Cleanup : mariadb-3:10.5.27-1.el9_5.0.2.x86_64 10/14 
  Cleanup : mariadb-common-3:10.5.27-1.el9_5.0.2.x86_64 11/14 
  Cleanup : mariadb-backup-3:10.5.27-1.el9_5.0.2.x86_64 12/14 
  Cleanup : mariadb-gssapi-server-3:10.5.27-1.el9_5.0.2.x86_64 13/14 
  Cleanup : mariadb-server-utils-3:10.5.27-1.el9_5.0.2.x86_64 14/14 
  Running scriptlet: mariadb-server-utils-3:10.5.27-1.el9_5.0.2.x86_64 14/14 
  Verifying : mariadb-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 1/14 
  Verifying : mariadb-server-3:10.5.27-1.el9_5.0.2.x86_64 2/14 
  Verifying : mariadb-common-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 3/14 
  Verifying : mariadb-common-3:10.5.27-1.el9_5.0.2.x86_64 4/14 
  Verifying : mariadb-gssapi-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 5/14 
  Verifying : mariadb-gssapi-server-3:10.5.27-1.el9_5.0.2.x86_64 6/14 
  Verifying : mariadb-backup-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 7/14 
  Verifying : mariadb-backup-3:10.5.27-1.el9_5.0.2.x86_64 8/14 
  Verifying : mariadb-server-utils-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 9/14 
  Verifying : mariadb-server-utils-3:10.5.27-1.el9_5.0.2.x86_64 10/14 
  Verifying : mariadb-errmsg-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 11/14 
  Verifying : mariadb-errmsg-3:10.5.27-1.el9_5.0.2.x86_64 12/14 
  Verifying : mariadb-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64 13/14 
  Verifying : mariadb-3:10.5.27-1.el9_5.0.2.x86_64 14/14 

Upgraded:
  mariadb-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                                             
  mariadb-backup-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                                      
  mariadb-common-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                                      
  mariadb-errmsg-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                                      
  mariadb-gssapi-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                               
  mariadb-server-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                                      
  mariadb-server-utils-3:10.11.10-1.module+el9.6.0+31841+9417776a.x86_64                                                

Complete!

root@rocky9:~# systemctl restart mariadb

root@rocky9:~# rpm -qa | grep mariadb-server
mariadb-server-utils-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64
mariadb-server-10.11.10-1.module+el9.6.0+31841+9417776a.x86_64

root@rocky9:~# mysql
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 3
Server version: 10.11.10-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
+--------------------+
3 rows in set (0.001 sec)

```

as you can clearly see, I was on MariaDB 10.5, then I switched modules, and then I did dnf update. Then I restarted MariaDB, and you can clearly see MariaDB running and the default databases.

No, the process should not cause problems for your databases. But obviously, you should make sure you have backups of your system before you do anything that might break something.

Also, forget about webmin and stop using it.

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [November 1, 2025, 11:27pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/5 "2025-11-01T23:27:19Z")

</div>

I normally stop the old service, backup, uninstall using dnf, then enable the stream, then install the new packages, then start the new version. Plus I also run the mysql upgrade tool after checking that it’s going to do what I expect it to do, e.g. fixing system tables where there have been schema changes.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [November 2, 2025, 10:14am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/6 "2025-11-02T10:14:36Z")

</div>

> [@gerry666uk](#):
>
> Plus I also run the mysql upgrade tool after checking that it’s going to do what I expect it to do, e.g. fixing system tables where there have been schema changes.

That is what MariaDB recommends: [mariadb-upgrade | MariaDB Documentation](https://mariadb.com/docs/server/clients-and-utilities/deployment-tools/mariadb-upgrade)

Their overall procedure is:

1. Make backup of data in databases
2. Stop service
3. Remove old packages
4. Install new packages
5. Start service
6. Run `mariadb-upgrade`
7. Restart service

There can be also changed defaults, renames, or removals of options. Example: [Upgrading from MariaDB 10.6 to MariaDB 10.11 | MariaDB Documentation](https://mariadb.com/docs/server/server-management/install-and-upgrade-mariadb/upgrading/mariadb-community-server-upgrade-paths/upgrading-from-mariadb-10-6-to-mariadb-10-11)

Somewhere there was a note that package upgrade might also run the mariadb-upgrade, but that running it multiple times is not an error.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 2, 2025, 10:33am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/7 "2025-11-02T10:33:25Z")

</div>

> [@jlehtone](#):
>
> Somewhere there was a note that package upgrade might also run the mariadb-upgrade, but that running it multiple times is not an error.

This was something I was also under the impression of as well, that deb/rpm package upgrades would take care of it. Although I’ve not checked the pre/post scripts to verify if that is the case or not. So definitely good advice to run the mysql\_pgrade anyway, just in case to be sure. Not something I’ve done personally and never had any issues when I was using MariaDB when I didn’t run it.

---

<div class="post-metadata">

**Author:** ![felfert](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/felfert/32/2259_2.png) [@felfert](https://forums.rockylinux.org/u/felfert)\
**Post date:** [November 2, 2025, 1:06pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/8 "2025-11-02T13:06:48Z")

</div>

> > [@gerry666uk](#):
> >
> > Plus I also run the mysql upgrade tool after checking that it’s going to do what I expect it to do, e.g. fixing system tables where there have been schema changes.

> That is what MariaDB recommends: [mariadb-upgrade | MariaDB Documentation](https://mariadb.com/docs/server/clients-and-utilities/deployment-tools/mariadb-upgrade)
> 
> Their overall procedure is:
> 
> 1. Make backup of data in databases
> 2. Stop service
> 3. Remove old packages
> 4. Install new packages
> 5. Start service
> 6. Run `mariadb-upgrade`
> 7. Restart service

Just 2 remarks:

- Steps 2-5 are handled during `dnf update` by the package pre/post scripts of the rpm package.

- Step 6 needs to run manually. However the mariadb.service runs a script after any startup which checks for an outdated data directory and prints a warning in the journal. That script is located at `/usr/libexec/mariadb-check-upgrade` The warning (if it exists) can be seen by running `journalctl -u mariadb.service`

---

<div class="post-metadata">

**Author:** ![chupi](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@chupi](https://forums.rockylinux.org/u/chupi)\
**Post date:** [November 3, 2025, 9:23am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/9 "2025-11-03T09:23:10Z")

</div>

Thank you all for your answers, they have been very helpful.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [November 3, 2025, 10:20am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/10 "2025-11-03T10:20:53Z")

</div>

> [@iwalker](#):
>
> Not something I’ve done personally and never had any issues when I was using MariaDB when I didn’t run it.

While MariaDB boasts about backward-compatibility, they do also mention:

> If you skip running `mariadb-upgrade`, issues can arise, including these:
> 
> - Errors in the [error log](https://mariadb.com/docs/server/server-management/server-monitoring-logs/error-log) that some system tables don’t have all needed columns.
> - Updates or searches may not find the record they are attempting to update or search for.
> - [CHECKSUM TABLE](https://mariadb.com/docs/server/reference/sql-statements/table-statements/checksum-table) may report the wrong checksum for [MyISAM](https://mariadb.com/docs/server/server-usage/storage-engines/myisam-storage-engine) or [Aria](https://mariadb.com/docs/server/server-usage/storage-engines/aria) tables.
> - The error message “Cannot load from mysql.proc. The table is probably corrupted.”

In other words it probably depends a lot on the content and use of the database, whether _things happen_ or not.

* * *

The script mentioned by @felfert notes:

> Please, mind that as a general rule, to upgrade from one release series to another, go to the next series rather than skipping a series.

“Smaller diffs to merge”, I presume. Red Hat has “stepwise” docs too: [Chapter&nbsp;5.&nbsp;Migration | 3.7 Release Notes | Red Hat Software Collections | 3 | Red Hat Documentation](https://docs.redhat.com/en/documentation/red_hat_software_collections/3/html/3.7_release_notes/chap-migration)

* * *

The overarching point is that “a database” is many things:

- Packages for the binaries, etc. These one can “dnf”
- System tables (schema and data). Initialized on very first service start, but separate from packages from then-on. The ‘mariadb-upgrade’ (or equivalents) may be required
- Schemas of the user databases. Tables, etc
- Data within the user databases

Furthermore, “backup” of database is not file copy of files in /var/lib/… (when service is running).  
Rather, one uses mysql-dump or similar tool to fetch consistent set of data.

---

<div class="post-metadata">

**Author:** ![chupi](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@chupi](https://forums.rockylinux.org/u/chupi)\
**Post date:** [November 3, 2025, 10:59am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/11 "2025-11-03T10:59:10Z")

</div>

Thanks jlehtone, I’m reviewing all the documentation you mentioned before running the update, and of course, I have backups of the databases in .sql format. When I finish the update, I’ll report here the result (successful or not) and the steps I followed.

---

<div class="post-metadata">

**Author:** ![chupi](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@chupi](https://forums.rockylinux.org/u/chupi)\
**Post date:** [November 4, 2025, 11:11am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/12 "2025-11-04T11:11:44Z")

</div>

Hello everyone,

I have successfully upgraded to MariaDB 10.11. These are the steps I followed:

$ mysqldump --all-databases --single-transaction --quick --lock-tables=false \> /home/backup/mariadb\_backup\_$(date +%F).sql

create MariaDB.repo file:

`$ MariaDB 10.11 RedHatEnterpriseLinux repository list - created 2025-11-01 10:04 UTC`  
`$ `  
`[mariadb]`  
`name = MariaDB`  
`$ ``rpm.mariadb.org`` is a dynamic mirror if your preferred mirror goes offline. See ``https://mariadb.org/mirrorbits/`` for details.`  
`$ baseurl = ``https://rpm.mariadb.org/10.11/rhel/$releasever/$basearch`  
`baseurl = ``https://mirror.raiolanetworks.com/mariadb/yum/10.11/rhel/$releasever/$basearch`  
`$ gpgkey = ``https://rpm.mariadb.org/RPM-GPG-KEY-MariaDB`  
`gpgkey = ``https://mirror.raiolanetworks.com/mariadb/yum/RPM-GPG-KEY-MariaDB`  
`gpgcheck = 1`

$ dnf module enable mariadb:10.11

$ systemctl stop mariadb.service

$ dnf remove “MariaDB\*” “mariadb\*”

$ ls /var/lib/MySQL

$ dnf clean all  
$ dnf makecache

$ dnf install mariadb mariadb-server

$ systemctl enable --now MariaDB

$ mariadb-upgrade

$ systemctl restart mariadb.service

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [November 4, 2025, 7:57pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/13 "2025-11-04T19:57:56Z")

</div>

It looks like you installed a non-rocky repo and then did

> [@chupi](#):
>
> dnf module enable mariadb:10.11

which I’m guessing would use the official rocky repo

---

<div class="post-metadata">

**Author:** ![chupi](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@chupi](https://forums.rockylinux.org/u/chupi)\
**Post date:** [November 5, 2025, 9:48am UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/14 "2025-11-05T09:48:28Z")

</div>

Hi gerry666uk,

Both MariaDB version 10.5 and 10.11 are from the Rocky Linux repository, as appstream modules.

$ dnf list MariaDB

Last metadata expiration check: 3:25:05 ago on Sat 01 Nov 2025 08:15:42 AM CET.  
Installed Packages  
mariadb.x86\_64 3:10.5.27-1.el9\_5.0.2 @appstream  
Available Packages  
mariadb.x86\_64 3:10.11.10-1.module+el9.6.0+31841+9417776a appstream

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [November 5, 2025, 11:09pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/16 "2025-11-05T23:09:15Z")

</div>

> [@chupi](#):
>
> Both MariaDB version 10.5 and 10.11 are from the Rocky Linux repository,

Right, so what’s all the stuff about

[https://mirror.raiolanetworks.com/](https://mirror.raiolanetworks.com/)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [January 4, 2026, 11:09pm UTC](https://forums.rockylinux.org/t/upgrade-mariadb-to-10-11/19824/17 "2026-01-04T23:09:30Z")

</div>

Closed on January 4, 2026, 11:09pm UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
