[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
*** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969160 Title: mariadb [ERROR] mysqld got signal 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
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 assertions haven't changed from 10.6.7, 10.6.8 is unlikely to be a magic fix. For the moment setting innodb_use_native_aio=0 will avoid the problem ref: https://mariadb.com/kb/en/innodb-system- variables/#innodb_use_native_aio -- 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: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
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 sometime in the next week: root@cd8baf7b8407:/source/builddir# sql/mariadbd --bootstrap --datadir=/tmp/ 2022-04-26 22:15:13 0 [Note] sql/mariadbd (server 10.6.8-MariaDB-1:10.6.8+maria~jammy) starting as process 9561 ... 2022-04-26 22:15:13 0 [Note] InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be created! 2022-04-26 22:15:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-04-26 22:15:13 0 [Note] InnoDB: Number of pools: 1 2022-04-26 22:15:13 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-04-26 22:15:13 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) 2022-04-26 22:15:13 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: try uprading the kernel 2022-04-26 22:15:13 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF 2022-04-26 22:15:13 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2022-04-26 22:15:13 0 [Note] InnoDB: Completed initialization of buffer pool 2022-04-26 22:15:13 0 [Note] InnoDB: Setting file './ibdata1' size to 12 MB. Physically writing the file full; Please wait ... 2022-04-26 22:15:13 0 [Note] InnoDB: File './ibdata1' size is now 12 MB. 2022-04-26 22:15:13 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 100663296 bytes 2022-04-26 22:15:13 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2022-04-26 22:15:13 0 [Note] InnoDB: New log file created, LSN=10329 2022-04-26 22:15:13 0 [Note] InnoDB: Doublewrite buffer not found: creating new 2022-04-26 22:15:13 0 [Note] InnoDB: Doublewrite buffer created 2022-04-26 22:15:13 0 [Note] InnoDB: 128 rollback segments are active. 2022-04-26 22:15:13 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-04-26 22:15:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-04-26 22:15:13 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-04-26 22:15:13 0 [Note] InnoDB: 10.6.8 started; log sequence number 0; transaction id 3 2022-04-26 22:15:13 0 [Note] Plugin 'FEEDBACK' is disabled. And kernel version - 5.18.0-0.rc2.23.fc37.x86_64 (general insanity or was testing kernel bugs, possibly both) -- 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: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
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 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: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
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 config set limits.kernel.memlock=1048576 On the container "ulimit -l" now shows 1024 (without setting the parameter the value was 64 which seems to be a default). Setting limits.kernel.memlock to multiples of 65536, the minimum factor enabling mariadb to start was 4 (ulimit -l showing 256). -- 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: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
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, 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: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969160] Re: mariadb [ERROR] mysqld got signal 6
** 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: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1969160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
