MariaDB MariaDB 10.4.9, 10.3.19 and 10.2.28, 10.1.42 and 5.5.66 Now Available

eva2000 · Nov 6, 2019

The MariaDB Foundation is pleased to announce the availability of MariaDB 10.4.9, MariaDB 10.3.19, MariaDB 10.2.28, MariaDB 10.1.42 and MariaDB 5.5.66, the latest stable releases in their respective series. See the release notes and changelogs for details. Download MariaDB 10.4.9 Release Notes Changelog What is MariaDB 10.9? Download MariaDB 10.3.19 Release Notes Changelog What is […]

The post MariaDB 10.4.9, 10.3.19 and 10.2.28, 10.1.42 and 5.5.66 Now Available appeared first on MariaDB.org.

Continue reading...

eva2000 · Nov 6, 2019

hmm probably hold off of yum updates for now. cPanel users reporting crashes with this update Mariadb 10.1.42 Crashes in cPanel v84.0.6 | Web Hosting Talk

might be cPanel specific though

We are currently receiving an influx of tickets regarding MariaDB failing to start with InnoDB Failed Assertion errors. We’ve identified this as an upstream issue with MariaDB (Case ID MDEV-20987) affecting the following versions:

10.1.42
10.2.28
10.3.19
10.4.9

The only known workaround is to downgrade the MariaDB package. Please reference Known Issues Status Page for more.
Click to expand...

Though there is MariaDB Jira bug tracker [MDEV-20987] SIGABRT Failing assertion: table->can_be_evicted in storage/innobase/dict/dict0dict.cc - Jira

After the recent MariaDB update, we've had 11 reports and counting of MariaDB failing to start. This appears related to the FTS changes recently made, perhaps MDEV-19073 ?
Click to expand...

Also experiencing the same issue on 14 servers after MariaDB updates today. As per cPanel's comments, running a yum downgrade of the main mariadb-server package allows MariaDB to start and function normally.
Click to expand...

2019-11-06 10:22:27 2ab722c16c40 InnoDB: Assertion failure in thread 46966050483264 in file dict0dict.cc line 1493
InnoDB: Failing assertion: table->can_be_evicted
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to System Dashboard - Jira
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: MySQL :: MySQL 5.6 Reference Manual :: 14.21.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
191106 10:22:27 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Click to expand...

pamamolf · Nov 6, 2019

Code:
yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel
Does that downgrade at Centminmod to the previous MariaDB version?

eva2000 · Nov 6, 2019

Yes that will downgrade to previous minor version. Strange though, I updated a few servers for one of my paying Centmin Mod using clients and they're on MariaDB 10.1.42 with no problems

pushing 2,300+ mysql queries/sec without any issue.
Code (Text):
mysqladmin ver
mysqladmin  Ver 9.1 Distrib 10.1.42-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Server version          10.1.42-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /home/database/mysql/mysql.sock
Uptime:                 5 hours 48 min 18 sec
Threads: 332  Questions: 48118307  Slow queries: 1157  Opens: 1323  Flush tables: 1  Open tables: 1260  Queries per second avg: 2302.531

eva2000 · Nov 6, 2019

From MariaDB Jira bug tracker update with marked fixed in next version = 10.1.43, 10.2.29, 10.3.20, 10.4.10

This is a regression that was caused by the fix of MDEV-20621. MySQL 5.6 (and MariaDB 10.0) introduced eviction of tables from the InnoDB data dictionary cache. Tables that are connected to FOREIGN KEY constraints or FULLTEXT INDEX are exempt of the eviction. With the problematic change, a table that would already be exempt from eviction due to FOREIGN KEY would cause the problem if there also was a FULLTEXT INDEX defined on it.
Click to expand...

pamamolf · Nov 6, 2019

They removed the problematic rpm version

Index of /10.3/centos7-amd64/rpms/

Soon we may have the fixed one

diy · Nov 8, 2019

Great news, thanks guys!

rdan · Nov 9, 2019

Servers updated fine.

Elasticsearch 7.4.2

MariaDB 10.3.20

sepulchre · Nov 9, 2019

I am on 10.1.41 version of MariaDB.
Can I just make an upgrade to the 10.4.x branch?
What are the benefits running XF?

rdan · Nov 9, 2019

To be safe use 10.3.x only.

eva2000 · Nov 9, 2019

sepulchre said: ↑

I am on 10.1.41 version of MariaDB.
Can I just make an upgrade to the 10.4.x branch?
What are the benefits running XF?
Click to expand...

read MariaDB - Interesting look at what's new in MariaDB 10.4 and sticky thread at MariaDB - MariaDB 10.1 upgrades to MariaDB 10.2, 10.3 and 10.4.

sepulchre · Nov 10, 2019

Upgrade made to 10.3.20 within 5 minutes.
No problems so far, all seems fine.

Thanks.

sepulchre · Jan 2, 2020

Hi,

I am currently on the 10.3.20 version, as stated above. I upgraded from the 10.1.x branch.
Now, since I am on the 10.3.20 branch, how can I update to the latest branch 10.3.21?
I don't see an option to do so.

--------------------------------------------------------
MariaDB MySQL Upgrade & Management Sub-Menu
--------------------------------------------------------
0). Regenerate New MySQL Root User Password (local server)
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
7). MariaDB 10.2.x to MariaDB 10.3.x YUM upgrade
8). MariaDB 10.3.x to MariaDB 10.4.x YUM upgrade
9). Back to Main menu
--------------------------------------------------------
Enter option [ 0 - 9 ]

eva2000 · Nov 7, 2020

pamamolf said: ↑
Code:
yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel
Does that downgrade at Centminmod to the previous MariaDB version?
Click to expand...
FYI, you may want to match galera versions with their MariaDB counterparts too
Code (Text):
yum downgrade MariaDB-client MariaDB-common MariaDB-compat MariaDB-devel MariaDB-server MariaDB-shared galera

Log in / Register

Forums

Get the most out of your Centmin Mod LEMP stack

MariaDB MariaDB 10.4.9, 10.3.19 and 10.2.28, 10.1.42 and 5.5.66 Now Available

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

diy Member

rdan Well-Known Member

sepulchre Member

rdan Well-Known Member

eva2000 Administrator Staff Member

sepulchre Member

sepulchre Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Get the most out of your Centmin Mod LEMP stack

MariaDB MariaDB 10.4.9, 10.3.19 and 10.2.28, 10.1.42 and 5.5.66 Now Available

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

diy Member

rdan Well-Known Member

sepulchre Member

rdan Well-Known Member

eva2000 Administrator Staff Member

sepulchre Member

sepulchre Member

eva2000 Administrator Staff Member

.