Public bug reported:
I'm running a Ubuntu 22.04 under lxd, without memory limits
When I try to run mariadb I see this error:
root@robot:~# journalctl -xeu mariadb.service
Apr 14 23:13:30 robot mariadbd[7926]: Max processes unlimited
unlimited processes
Apr 14 23:13:30 robot mariadbd[7926]: Max open files 32768
32768 files
Apr 14 23:13:30 robot mariadbd[7926]: Max locked memory 65536
65536 bytes
Apr 14 23:13:30 robot mariadbd[7926]: Max address space unlimited
unlimited bytes
Apr 14 23:13:30 robot mariadbd[7926]: Max file locks unlimited
unlimited locks
Apr 14 23:13:30 robot mariadbd[7926]: Max pending signals 63736
63736 signals
Apr 14 23:13:30 robot mariadbd[7926]: Max msgqueue size 819200
819200 bytes
Apr 14 23:13:30 robot mariadbd[7926]: Max nice priority 0
0
Apr 14 23:13:30 robot mariadbd[7926]: Max realtime priority 0
0
Apr 14 23:13:30 robot mariadbd[7926]: Max realtime timeout unlimited
unlimited us
Apr 14 23:13:30 robot mariadbd[7926]: Core pattern: |/usr/share/apport/apport
%p %s %c %d %P %E
Apr 14 23:13:30 robot systemd[1]: mariadb.service: Main process exited,
code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 6.
Apr 14 23:13:30 robot systemd[1]: mariadb.service: Failed with result
'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mariadb.service has entered the 'failed' state with result
'core-dump'.
Apr 14 23:13:30 robot systemd[1]: Failed to start MariaDB 10.6.7 database
server.
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░
░░ The job identifier is 4500 and the job result is failed.
Apr 14 23:13:36 robot systemd[1]: mariadb.service: Scheduled restart job,
restart counter is at 76.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit mariadb.service has been scheduled, as the
result for
░░ the configured Restart= setting for the unit.
Apr 14 23:13:36 robot systemd[1]: Stopped MariaDB 10.6.7 database server.
░░ Subject: A stop job for unit mariadb.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit mariadb.service has finished.
░░
░░ The job identifier is 4548 and the job result is done.
Apr 14 23:13:36 robot systemd[1]: Starting MariaDB 10.6.7 database server...
░░ Subject: A start job for unit mariadb.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mariadb.service has begun execution.
░░
░░ The job identifier is 4548.
Apr 14 23:13:36 robot mariadbd[7970]: 2022-04-14 23:13:36 0 [Note]
/usr/sbin/mariadbd (server 10.6.7-MariaDB-2ubuntu1) starting as process 7970 ...
Apr 14 23:13:36 robot mariadbd[7970]: 2022-04-14 23:13:36 0 [Note] InnoDB: The
first data file './ibdata1' did not exist. A new tablespace will be created!
Apr 14 23:13:36 robot mariadbd[7970]: 2022-04-14 23:13:36 0 [Note] InnoDB:
Compressed tables use zlib 1.2.11
Apr 14 23:13:36 robot mariadbd[7970]: 2022-04-14 23:13:36 0 [Note] InnoDB:
Number of pools: 1
Apr 14 23:13:36 robot mariadbd[7970]: 2022-04-14 23:13:36 0 [Note] InnoDB:
Using crc32 + pclmulqdq instructions
Apr 14 23:13:36 robot mariadbd[7970]: 2022-04-14 23:13:36 0 [Warning] mariadbd:
io_uring_queue_init() failed with ENOMEM: try larger memory locked limit,
ulimit -l, or https://mariadb.com/kb/en/sys>
Apr 14 23:13:36 robot mariadbd[7970]: 220414 23:13:36 [ERROR] mysqld got signal
6 ;
Apr 14 23:13:36 robot mariadbd[7970]: This could be because you hit a bug. It
is also possible that this binary
Apr 14 23:13:36 robot mariadbd[7970]: or one of the libraries it was linked
against is corrupt, improperly built,
Apr 14 23:13:36 robot mariadbd[7970]: or misconfigured. This error can also be
caused by malfunctioning hardware.
Apr 14 23:13:36 robot mariadbd[7970]: To report this bug, see
https://mariadb.com/kb/en/reporting-bugs
Apr 14 23:13:36 robot mariadbd[7970]: We will try our best to scrape up some
info that will hopefully help
Apr 14 23:13:36 robot mariadbd[7970]: diagnose the problem, but since we have
already crashed,
Apr 14 23:13:36 robot mariadbd[7970]: something is definitely wrong and this
may fail.
Apr 14 23:13:36 robot mariadbd[7970]: Server version: 10.6.7-MariaDB-2ubuntu1
Apr 14 23:13:36 robot mariadbd[7970]: key_buffer_size=134217728
Apr 14 23:13:36 robot mariadbd[7970]: read_buffer_size=131072
Apr 14 23:13:36 robot mariadbd[7970]: max_used_connections=0
Apr 14 23:13:36 robot mariadbd[7970]: max_threads=153
Apr 14 23:13:36 robot mariadbd[7970]: thread_count=0
Apr 14 23:13:36 robot mariadbd[7970]: It is possible that mysqld could use up to
Apr 14 23:13:36 robot mariadbd[7970]: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_threads = 467957 K bytes of memory
Apr 14 23:13:36 robot mariadbd[7970]: Hope that's ok; if not, decrease some
variables in the equation.
** Affects: mariadb-10.6 (Ubuntu)
Importance: Undecided
Status: New
--
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
