MariaDB 10.1.21 and other releases now available

2017-01-18

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.21, MariaDB 10.0.29, MariaDB Galera Cluster 10.0.29, MariaDB Connector/J 1.5.7, MariaDB Connector/C 2.3.2, and MariaDB Connector/C 3.0.1 Beta. Apart from the Connector/C 3.0.1 Beta these are all stable (GA) releases. See the release notes and changelogs for details.

Download MariaDB 10.1.21

Release Notes Changelog What is MariaDB 10.1?

MariaDB APT and YUM Repository Configuration Generator

Download MariaDB 10.0.29

Release Notes Changelog What is MariaDB 10.0?

MariaDB APT and YUM Repository Configuration Generator

Download MariaDB Galera Cluster 10.0.29

Release Notes Changelog What is MariaDB Galera Cluster?

MariaDB APT and YUM Repository Configuration Generator

Download MariaDB Connector/J 1.5.7

Release Notes Changelog About MariaDB Connector/J

Download MariaDB Connector/C 2.3.2

Release Notes Changelog About MariaDB Connector/C

Download MariaDB Connector/C 3.0.1 Beta

Release Notes Changelog About MariaDB Connector/C

Thanks, and enjoy MariaDB!
MariaDB 10.1.21 now available

Connector/C, Connector/J, MariaDB 10.0, MariaDB 10.1, MariaDB Galera Cluster, MariaDB Galera Cluster 10.0, MariaDB Releases, mysql

Comments

6 responses to “MariaDB 10.1.21 and other releases now available”

2017-01-19

MariaDB 10.1.21 和其他版本已发布 | 客家网络

[…] 发布主页 […]
2017-01-19

MariaDB 10.1.21 和其他版本已发布 | Zen-Cart.Wang

[…] 发布主页 […]
2017-01-19

MariaDB 10.1.21 和其他版本已发布 | News Pod

[…] 发布主页 […]
2017-02-09

Jure

I can’t get this version to start as a service on debian/stretch on DigitalOcean (can start by /usr/sbin/mysqld). I suspect some SELinux incompatibility.

mariadb.service: Failed at step NO_NEW_PRIVILEGES spawning /usr/sbin/mysqld: Invalid argument

Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-02-09 21:26:28 CET; 32min ago
Process: 2184 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=227/NO_NEW_PRIVILEGES)

Setting NoNewPrivileges to true/false has no effect.
1. 2017-02-11
  
  Jure
  
  You can probably disregard my previous comment. Turns out I was using a not very recent kernel – 3.2.0-4 but after upgrade to a more recent version it works ok.
  1. 2017-09-28
    
    Jörg Schubert
    
    NoNewPrivileges is ignored when one of these options is set:
    
    SystemCallFilter=, SystemCallArchitectures=, RestrictAddressFamilies=, RestrictNamespaces=, PrivateDevices=, ProtectKernelTunables=, ProtectKernelModules=, MemoryDenyWriteExecute=, or RestrictRealtime=
    
    In case of debian 9 with very old kernel (xen h3.2.64-domU) I had to disable “PrivateDevices”