MariaDB 10.1.22

Erulezz

Verified User
Joined
Sep 14, 2015
Messages
905
Location
🇳🇱
https://mariadb.com/kb/en/mariadb/mariadb-10122-release-notes/

Notable Changes

Updating from MariaDB 10.1.21 to MariaDB 10.1.22 is highly recommended due to two high-priority regression fixes. See below for links to the relevant MDEVs.

XtraDB updated to 5.6.35-80.0
TokuDB updated to 5.6.35-80.0
PCRE updated to 8.40
MDEV-12160: ed25519 authentication plugin
MDEV-11842: Fix a 10.1.21 regression with failed INSERT, BEFORE INSERT triggers, and columns with no default value
MDEV-12075: Fix a 10.1.21 regression in the InnoDB data file extension code
MDEV-11027: better InnoDB crash recovery progress reporting
MDEV-11520: improvements to how InnoDB data files are extended
Improvements to InnoDB startup/shutdown to make it more robust
MDEV-11233: fix for FULLTEXT index crash
MDEV-9734: systemd compatible bintar files now available
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.1 for Fedora 23, CentOS 5, RHEL 5, and openSUSE 13
OpenSUSE 42 repositories have been added in this release
Fixes for the following security vulnerabilities:
CVE-2017-3313
CVE-2017-3302
 
Last edited:
I did get a warning when installing;

Updating / installing...
1:MariaDB-common-10.1.22-1.el7.cent################################# [ 8%]
2:MariaDB-client-10.1.22-1.el7.cent################################# [ 17%]
3:MariaDB-server-10.1.22-1.el7.centwarning: /usr/lib/systemd/system/mariadb.service saved as /usr/lib/systemd/system/mariadb.service.rpmsave
################################# [ 25%]
libsemanage.map_file: Unable to open /usr/share/mysql/policy/selinux/mariadb.pp
(No such file or directory).
libsemanage.semanage_direct_install_file: Unable to read file /usr/share/mysql/policy/selinux/mariadb.pp
(No such file or directory).
/usr/sbin/semodule: Failed on /usr/share/mysql/policy/selinux/mariadb.pp!
4:MariaDB-devel-10.1.22-1.el7.cento################################# [ 33%]
5:MariaDB-shared-10.1.22-1.el7.cent################################# [ 42%]
6:MariaDB-compat-10.1.22-1.el7.cent################################# [ 50%]

And this symbolic link error is still there;

Cleaning up / removing...
7:MariaDB-devel-10.1.21-1.el7.cento################################# [ 58%]
8:MariaDB-server-10.1.21-1.el7.cent################################# [ 67%]
9:MariaDB-client-10.1.21-1.el7.cent################################# [ 75%]
10:MariaDB-compat-10.1.21-1.el7.cent################################# [ 83%]
11:MariaDB-shared-10.1.21-1.el7.cent################################# [ 92%]
12:MariaDB-common-10.1.21-1.el7.cent################################# [100%]
Failed to execute operation: Too many levels of symbolic links

However everything is cleaned and 10.1.22 is running stable.
 
Regarding "Failed to execute operation: Too many levels of symbolic links", I don't think we need to worry about that, I don't think it causes any trouble after reading this: https://lists.opensuse.org/opensuse-bugs/2016-04/msg00113.html

Regarding libsemanage, I have no idea, other then that on my servers I have always deactivated selinux. I guess you should not worry about it if you have selinux deactivated. But I don't know.
 
Thanks for your news!
I am also using mariadb 10.1 for our forum but didn't see any improvements for it.
 
It don't read my my.cnf file. That's why i came to this problem.

I want to go back with DirectAdmin Custombuild plugin from MariaDB to MySQL, but this is not possible. The plugin see it as a downgrade and that is not possible.

My problem: I can't tune my MariaDB after auto updates/upgrades. Also rebuild is not possible because of "Failed to execute operation: Too many levels of symbolic links". Auto update/upgrade of MariaDB has broken my MariaDB installation.

I have a big webshop at my VPS now, where i want to tune the import of a lot of products. But tuning is impossible.

PS. I think i have to buy a new VPS and move all the websites to the new VPS.
 
Last edited:
Back
Top