Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3.15
-
None
Description
I am getting regular signal 11 errors when interacting with INFORMATION_SCHEMA in 10.3.15. Have now crashed using homebrew install on my Mac, docker contianer on my mac, and Centos repo install on AWS (to rule out hardware issue). Once I crashed simply when I issuesd "use information_schema" via mysql command line. More often I crash doing simple selects against the column table.
Most recent crash on AWS Centos repo install simply involved starting the mariadb service via systemctl, starting mysql command line and then issuing.
mysql -uroot
|
Welcome to the MariaDB monitor. Commands end with ; or \g.
|
Your MariaDB connection id is 8
|
Server version: 10.3.15-MariaDB MariaDB Server
|
|
|
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
|
|
|
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
|
|
|
MariaDB [(none)]> use information_schema
|
Reading table information for completion of table and column names
|
You can turn off this feature to get a quicker startup with -A
|
|
|
Database changed
|
MariaDB [information_schema]> select column_name from columns;
|
ERROR 2006 (HY000): MySQL server has gone away
|
No connection. Trying to reconnect...
|
Connection id: 8
|
Current database: information_schema
|
|
|
ERROR 2006 (HY000): MySQL server has gone away
|
No connection. Trying to reconnect...
|
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
|
ERROR: Can't connect to the server
|
|
|
unknown [information_schema]>
|
Log output via journalctl is attached and includes at least a couple signal 11s.
Running on m5.xlarge (4 core 16 GB memory).
Let me know what other info you would like. Crash has been easy for me to reproduce (3 environments out of 3 so far).
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-