[MDEV-14532] apt upgrade fails on TokuDB Created: 2017-11-29  Updated: 2017-11-29  Resolved: 2017-11-29

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Platform Debian
Affects Version/s: 10.2.11
Fix Version/s: 10.2.11

Type: Bug Priority: Critical
Reporter: Nicolas Payart Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: apt, debian
Environment:

Debian Strech

Issue Links:
Relates
relates to MDEV-14524 TokuDB is unable to be built on Linux Closed

 Description   

I was running a MariaDB server installed via APT repositories (from mariadb.org) with the following packages :

  • mariadb-server-10.2 (10.2.10+maria~stretch)
  • mariadb-plugin-tokudb (10.2.10+maria~stretch)

After running an apt-get upgrade, mariadb-server was upgraded to 10.2.11+maria~stretch but mariadb-plugin-tokudb was not...

Now, TokuDB tables are unusable.
TokuDB Storage Engine can not be loaded anymore:

MariaDB [(none)]> INSTALL SONAME 'ha_tokudb';
 
ERROR 1126 (HY000): Can't open shared library 'ha_tokudb.so' (errno: 8, API version for STORAGE ENGINE plugin TokuDB not supported by this version of the server)



 Comments   
Comment by Elena Stepanova [ 2017-11-29 ]

nico, Yes, we are already aware, sorry about that. TokuDB 10.2.11 package is coming soon, expectedly later today.

Comment by Nicolas Payart [ 2017-11-29 ]

Thank you Elena.

For thoses who are experiencing the same issue and want to downgrade MariaDB to its previous minor version using apt, you can follow the following steps on Debian (Stretch in this example) :

  1. Add "mariadb-10.2.10" apt source: 

    echo "deb http://fr.mirror.babylon.network/mariadb//mariadb-10.2.10/repo/debian stretch main" > /etc/apt/sources.list.d/mariadb-10.2.10.list

  2. Update apt: 

    apt-get update

  3. Then install version-specific of all you mariadb packages: 

    apt-get install mariadb-server-10.2=10.2.10+maria~stretch mariadb-server-core-10.2=10.2.10+maria~stretch

Comment by Elena Stepanova [ 2017-11-29 ]

The TokuDB package is now in place (particularly in the repo that you are apparently using). Sorry again for the trouble.

Generated at Thu Feb 08 08:14:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.