Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.3.24, 10.4.14, 10.5.5
-
Ubuntu 18.04.4 LTS, Ubuntu 18.04.5 LTS, running on virtual machines (vmware and VirtualBox) and AWS EC2 instances
Description
Hello,
After I installed a new server with MariaDB 10.4 or 10.5, I am facing on ubuntu syslog the "systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV" being reported a lot of times.
Then applications loss the DB connections and some transactions are broken. I tried to install a new server, MariaDB, and restore a existing mysql dump file, however the same error happened.
My system: - AWS EC2 running ubuntu 18.04 instances; - MariaDB 10.4.14 / 10.5 (error on both versions); - Client applications (nodejs using mysql or mariadb dependency);
My findings so far is that only on MariaDB 10.4.13 (using a not-upgraded developer server and another one using AWS RDS MariaDB) the error does not happen.
All other tentatives, I tried existing and new servers with MariaDB 10.4.14 and 10.5.x, the erratic behavior was the same (service crash and restart with status=11/SEGV).
I am attaching my syslog and coredump files.
PS: I also recorded the error on community KB:
https://mariadb.com/kb/en/mariadb-104-105-crashing-and-restarting-intermittently-status11segv/
Best regards,
Attachments
Issue Links
- relates to
-
MDEV-17239 change default max_recursive_iterations = 4G -> 1k
- Closed