*** This bug is a duplicate of bug 1970634 ***
https://bugs.launchpad.net/bugs/1970634
** This bug has been marked a duplicate of bug 1970634
FTBFS: mariadb fails to start due to low MEMLOCK limit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
See https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634
as its the same problem.
While my 10.6.8-MariaDB-1:10.6 test above what built in an ubuntu-22.04
container, it quite possibly used different compile options than what
produces the packages. As the regions of code of the
Checked a rebased https://github.com/MariaDB/server/pull/2036
(openssl-3.0 backport on 10.6 latest from yesterday) in ubuntu-22.04
container and it doesn't assert. The ENOMEM error handling path is the
same as ENOSYS. I will get to the 'uprading' typo though probably not
before the next release
On the Ubuntu container host the fresh jammy install and the container
upgraded to Jammy behave the same. Probably the kernel versions on the
two container hosts make the difference. Manjaro is clearly ahead of
Ubuntu 20.04.
--
You received this bug notification because you are a member of
Had exactly the same problem, but only with a container host running
Ubuntu 21.10. No problem with the container running on a Manjaro host.
LXC runs with version 5.0 on both hosts. LXC container in both cases
running Ubuntu 22.04.
I could enable mariadb to start in the container by setting
lxc
This is the apport-cli file
** Attachment added: "apport-cli mariadb-server"
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+attachment/5581076/+files/apport.mariadb-server.ooapdhtt.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: jammy ubuntu
** Tags removed: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969160
Title:
mariadb [ERROR] mysqld got signal 6
To manage notifications about this bug go to:
