MariaDB Updates

[BillyS]

I know that @Erulezz also mentioned this, but MariaDB released new versions a couple of weeks ago.

MariaDB Community Server Release Notes

mariadb.com

 

[Erulezz]

@smtalk @fln @DirectAdmin Support

MariaDB 10.9.1, 10.8.3, 10.7.4, 10.6.8, 10.5.16, 10.4.25, 10.3.35 and 10.2.44 now available - MariaDB.org

The MariaDB Foundation is pleased to announce the availability of MariaDB 10.9.1, the first Release Candidate (RC) in the MariaDB 10.9 series, MariaDB 10.8.3, the first Generally Available (GA) release in the MariaDB 10.8 series, MariaDB 10.7.4, the second Generally Available release in the...

mariadb.org

Any ETA on adding these? Pretty big updates for all versions with performance updates.. and this:

Security​

• Fixes for the following security vulnerabilities:
  • CVE-2021-46669
  • CVE-2022-27376
  • CVE-2022-27377
  • CVE-2022-27378
  • CVE-2022-27379
  • CVE-2022-27380
  • CVE-2022-27381
  • CVE-2022-27382
  • CVE-2022-27383
  • CVE-2022-27384
  • CVE-2022-27386
  • CVE-2022-27387
  • CVE-2022-27444
  • CVE-2022-27445
  • CVE-2022-27446
  • CVE-2022-27447
  • CVE-2022-27448
  • CVE-2022-27449
  • CVE-2022-27451
  • CVE-2022-27452
  • CVE-2022-27455
  • CVE-2022-27456
  • CVE-2022-27457
  • CVE-2022-27458

 

[smtalk]

Updated, thanks.

 

[apogee]

Update don't upgrade to new version, stick on old (only on one server) - CL8:

Executing /usr/local/directadmin/plugins/custombuild/admin/build mysql...
Dumping database a..........
.............
Downloading mysql/centos8-64.txt...
######################################################################## 100.0%
Found /usr/local/directadmin/custombuild/mysql/MariaDB-client-10.5.16-1.el8.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-devel-10.5.16-1.el8.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-server-10.5.16-1.el8.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-shared-10.5.16-1.el8.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-common-10.5.16-1.el8.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-backup-10.5.16-1.el8.x86_64.rpm
Installing dependencies...
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 1:40:23 ago on Mon Jun 6 15:09:03 2022.
Package boost-program-options-1.66.0-10.el8.x86_64 is already installed.
Package perl-Compress-Raw-Bzip2-2.081-1.el8.x86_64 is already installed.
Package perl-Compress-Raw-Zlib-2.081-1.el8.x86_64 is already installed.
Package perl-DBI-1.641-3.module_el8.3.0+2054+fbe55708.x86_64 is already installed.
Package perl-Data-Dumper-2.167-399.el8.x86_64 is already installed.
Package perl-IO-Compress-2.081-1.el8.noarch is already installed.
No match for argument: perl-PlRPC
Package lsof-4.93.2-1.el8.x86_64 is already installed.
Package rsync-3.1.3-12.el8.x86_64 is already installed.
Package pcre2-10.32-2.el8.x86_64 is already installed.
Package socat-1.7.4.1-1.el8.x86_64 is already installed.
Error: Unable to find a match: perl-PlRPC
Installing galera...
Found /usr/local/directadmin/custombuild/mysql/galera-4-26.4.8-1.el8.x86_64.rpm
warning: /usr/local/directadmin/custombuild/mysql/galera-4-26.4.8-1.el8.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
Stopping mysqld ...
Service didn't get stopped, sleeping for 20 secs and re-trying ...
Stopping mysqld ...
Updating MariaDB 10.5.15 to 10.5.16
warning: MariaDB-client-10.5.16-1.el8.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
Created symlink /etc/systemd/system/mysql.service → /etc/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/mysqld.service → /etc/systemd/system/mariadb.service.
Ensuring local-infile is disabled for security reasons in MySQL configuration file...
Giving mysqld a few seconds to start up...
This installation of MariaDB is already upgraded to 10.5.13-MariaDB.
There is no need to run mysql_upgrade again for 10.5.15-MariaDB.
You can use --force if you still want to run mysql_upgrade
CageFS: Executing 'cagefsctl --force-update'...
Copying /usr/bin/msql2mysql to /usr/share/cagefs-skeleton/usr/bin/msql2mysql
Copying /usr/bin/my_print_defaults to /usr/share/cagefs-skeleton/usr/bin/my_print_defaults
Copying /usr/bin/mariadb to /usr/share/cagefs-skeleton/usr/bin/mariadb
Copying /usr/bin/mariadb-access to /usr/share/cagefs-skeleton/usr/bin/mariadb-access
Copying /usr/bin/mariadb-admin to /usr/share/cagefs-skeleton/usr/bin/mariadb-admin
Copying /usr/bin/mariadb-binlog to /usr/share/cagefs-skeleton/usr/bin/mariadb-binlog
Copying /usr/bin/mariadb-check to /usr/share/cagefs-skeleton/usr/bin/mariadb-check
Copying /usr/bin/mariadb-dump to /usr/share/cagefs-skeleton/usr/bin/mariadb-dump
Copying /usr/bin/mariadb-find-rows to /usr/share/cagefs-skeleton/usr/bin/mariadb-find-rows
Copying /usr/bin/mariadb-import to /usr/share/cagefs-skeleton/usr/bin/mariadb-import
Copying /usr/bin/mariadb-show to /usr/share/cagefs-skeleton/usr/bin/mariadb-show
Copying /usr/bin/mariadb-waitpid to /usr/share/cagefs-skeleton/usr/bin/mariadb-waitpid
Updating users ...
Updating statuses of users ...
Restarting MySQL.
Installation completed.
Done

 

[apogee]

removed /var/lib/rpm/.rpm.lock and run again, done

 

[BillyS]

Can someone translate for me what happened? I noticed the update took a long time on my server.

 

[Richard G]

Can someone translate for me what happened?

What exactly do you need translated? And in which language?

 

[BillyS]

error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)

Is this the issue, the upgrade threw this error and they were not able to run the update?

 

[Richard G]

Yes there was an error during update, this error which he posted in the log:

error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)

Removing the /var/lib/rpm/.rpm.lock file remove this error for Apogee so he could do the upgrade without errors.

 

[sparek]

Is this the issue, the upgrade threw this error and they were not able to run the update?

I don't think the issue is related to MariaDB. But is just related to his RPM database being locked. Probably by another process or a process that failed to clean up after itself (perhaps stopped mid install).

I don't think there is an issue with the MariaDB update. This was just specific to this one specific user having their RPM database locked.

 

[Richard G]

Yes I'm also under that impression. I didn't here of any similar issues until now.

 

[apogee]

it occurred only on one server, but on one of the dev servers the update took almost 7 minutes (but without any other error messages)

 

[Erulezz]

Dumping the databases took that long or the upgrade itself? Pretty quick here, around 30-40 seconds to install.

One thing I noticed is that mysql_upgrade isn't run anymore after the upgrade:

Giving mysqld a few seconds to start up...
This installation of MariaDB is already upgraded to 10.6.5-MariaDB.
There is no need to run mysql_upgrade again for 10.6.8-MariaDB.
You can use --force if you still want to run mysql_upgrade
Restarting MySQL.
Installation completed.

A change in CustomBuild? I've had some issues in the past with this so I ran it manually with --force

This installation of MariaDB is already upgraded to 10.6.8-MariaDB.
There is no need to run mysql_upgrade again for 10.6.8-MariaDB.
You can use --force if you still want to run mysql_upgrade

 

[Active8]

One thing I noticed is that mysql_upgrade isn't run anymore after the upgrade:

Same here but the you get message like

This installation of MariaDB is already upgraded to 10.5.13-MariaDB. There is no need to run mysql_upgrade again for 10.5.15-MariaDB.

So this make me confused,although checking sql version shows the latest version, but now I am worried..

 

[Erulezz]

If ./build versions shows the latest version it’s ok.

mysql_upgrade saves the MySQL version number in a file named mysql_upgrade_info in the data directory. This is used to quickly check whether all tables have been checked for this release so that table-checking can be skipped. To ignore this file and perform the check regardless, use the --force option.

To make sure everything is ok and upgrade this file run it manually

mysql_upgrade --force -u root -p

 

[BillyS]

This installation of MariaDB is already upgraded to 10.5.13-MariaDB. There is no need to run mysql_upgrade again for 10.5.15-MariaDB.

I saw this during my upgrade too, which confused me so I did check to make sure the upgrade was successful - which it was.

 

[Richard G]

but now I am worried..

You don't need to be worried, as mysql-upgrade only needs to be run when doing major version upgrades or migrations. So MariaDB 10.4 to 10.5 for example, but not within the 10.4 or 10.5 range.

The current update is a minor version so you don't need to run the command. Which is what the notice also says.
It's safe to do it, but it's not needed.

You can find this info at the Mariadb info page here:

mysql_upgrade

Old name for mariadb-upgrade.

mariadb.com

I wonder why nobody else went on Google and checked this if people are worried.

 

[Zhenyapan]

I am worried..

same about recommended PHP recompile - it's only needed after mysql upgrade between different branches, any update in same branch - don't need to change anything because usually nobody implements any new incompatible features in same branch.